View Single Post
Old 06-30-2020, 12:06 PM   #786
Westrabua
Human being with feelings
 
Join Date: Aug 2008
Location: Germany
Posts: 76
Default

@osxmidi: Thanks for giving support!


Quote:
Originally Posted by pax-eterna View Post
Okay, finally got it sorted - the instructions were a little off...firstly it showed cmake .. when the correct command (in eOS) was cmake . and further the make dir build is redundant as the cmakr command worked in the linvstmanager folder directly without the need to mkdir build.
The actual build instructions should work on all distributions the same. It's only about installing the right dependencies (as osxmidi pointed out above), whose names can differ between distributions.

And here's a quick rundown of that 'cmake ..' command.
The double dot '..' means "one directory up from the current one".
A single dot '.' means "the current directory".
This applies to any distribution you might be running in general, so it doesn't hurt to know about it.

You are right about that one can run cmake in the base directory without that 'build' directory just fine.
The reason why one would prefer to create a 'build' directory and then run 'cmake ..' (which basically says "cmake, please run and look one directory above for your 'CMakeLists.txt' file"), is that by doing so, all the files created during the build process itself are then stored within that 'build' directory, away from the actual source files.

So it's not so much about it wouldn't "work" without that build directory, but more about it keeps your source files etc. clean of any temporary build files.
Without using the 'build' directory (like you've done yourself), you simply end up with all files in the same base folder mixed together. That's about it.
__________________
Graphical manager application for LinVst: https://github.com/Goli4thus/linvstmanager

A.k.a Goli4thus (on github). Donate
Westrabua is offline   Reply With Quote