cmake; make install; liblib

[rburkholder]

A few comments:

• for cmake, in your getting started guide, it is typical to "mkdir build && cd build" then perform the cmake ..... within the build directory -- never mind on this, I see that the '-B build' does the same thing
• once built, do you have a 'sudo make install' of some sort so that include directory is placed into /usr/local/include/ and the libs are placed in /usr/local/lib?
• the built static files in build/ have a liblib prefix -- shouldn't they be just simply prefixed with a single 'lib'?
• and it is these .a files I'd like to see in /usr/local/lib so I can link them across some projects

[borisbat]

There is cmake install. I've tested them on win64 and mac, I'm assuming its going to work fine on linux.
I got no preferences on how the project libraries are named - typical integration so far was building daScript with the project which required it. I would certainly appreciate any help with organizing this for the better workflow.

[rburkholder]

Thank you for the update. As more background:

• in your installation notes, you have a step for make daScript which seems to skip all the test stuff and just build the libraries. Which is desirable. However, if I followed that with sudo make install, it proceeds to reprocess a bunch of test stuff and do other things I don't think it needs to. So I killed that and simply referenced your final libs where they were. But it would be nice to see them in /usr/local/lib at some point.
  • it would be nice if there was an explicit make install to handle the simple installation of the libs and headers, without all the test stuff being run. perhaps a separate make test or something.
• I think you have some CMakeLists.txt projects which have a 'lib' prefix on them. In your note in my other issue, you mention a primary target of windows & mac. So I kinda understand what happened. On linux, a quirk of the build process is to automatically prefix build libraries with a lib. And during the link process to automatically apply that to any included library lists. This would be the reason for the 'liblib' prefix probably.
  • my solution to this sort of thing for my own projects is/was to put libraries into a lib/ source sub-directory, and remove the lib prefix from the project name. It isn't as pretty from a windows platform perspective, but it conforms to the linux platform -- my suggestion for what it is worth.

[borisbat]

CMake has options of conditional compilation per platform. Mainly IF(WIN32), IF(APPLE) etc. So I suspect project files can be modified to do different things on linux. I'm not sure when I'll be able to get to it (I will eventually), but I will gladly accept linux PR's :)