Thx now for summing up the tasks. Here comes a status update:
As far as I can see I have implemented most of it up until make dist. Just the paths are probably not correct. Since I don't exactly know to much about Linux, I simply asked those guys
Our build system supports copyable installations, which means everything gets into one folder with different subfolders (bin, lib, lib/static, data, config, log, lib/modules). This is very useful for "installing" on systems where you don't have the rights to install as usual. And it is extremely useful for Windows since you can simply move things around without worrying.
But the default installation for Linux is of course with hard coded paths. Here are the currently used paths (extract from InstallConfig.cmake from the resource2 branch):
Code: Select all
SET(RUNTIME_INSTALL_DIRECTORY ${CMAKE_INSTALL_PREFIX}/bin)
SET(LIBRARY_INSTALL_DIRECTORY ${CMAKE_INSTALL_PREFIX}/lib/orxonox)
SET(ARCHIVE_INSTALL_DIRECTORY ${CMAKE_INSTALL_PREFIX}/lib/orxonox/static)
SET(DOC_INSTALL_DIRECTORY ${CMAKE_INSTALL_PREFIX}/share/doc/orxonox)
SET(DATA_INSTALL_DIRECTORY ${CMAKE_INSTALL_PREFIX}/share/orxonox)
${CMAKE_INSTALL_PREFIX} is a CMake Cache variable so you can easily configure it. The default points to "/usr/local".
Is that remotely correct? The config and log folders go to ~/.orxonox, but at runtime.
And orxonox still runs smoothly if you use the executable from any other directory (as long as the binary path is in the PATH variable). It was quite a pain, but I found code for all three platforms to perform this.
make, make install and make clean should work properly.
However I haven't yet had a look at CPack to generate the packages. It seems to offer quite a lot, but with sparse documentation.
If I can find the time I shall have a look at it.