-
Notifications
You must be signed in to change notification settings - Fork 448
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Fix installation on Linux/Mac machines #101
Conversation
Signed-off-by: Bogdan Vaneev <[email protected]>
Signed-off-by: Bogdan Vaneev <[email protected]>
Signed-off-by: Bogdan Vaneev <[email protected]>
Signed-off-by: Bogdan Vaneev <[email protected]>
This is not true. When you generate the cmake project, then this file will be generated from cmake. I have to check first how your changes affect the VS-Windows build. |
I compiled your PR with MSVC, it fails because of this reason:
Can you restore the old behavior, so that by default, when not custom install directory was provided, it will be installed in the build directory? |
I am working an a fix for this! |
See PR #103 : I merged this PR, and restored some good behavior which was over written. |
cmake .. -DCMAKE_DEBUG_POSTFIX=hello
)detail/base/version.h
: if you install this project and do not include it via generatedrttr-config.cmake
, then this file is not generated and compilation failsGNUInstallDirs
package for install paths on OSX and Linux. Now you can writecmake -DCMAKE_INSTALL_PREFIX=/usr/local ${src} make install
/usr/local/lib
, binaries in/usr/local/bin
, cmake in/usr/local/share/rttr/cmake
/usr/local/lib
, binaries in/usr/local/bin
, etc. To write in these directories you need root permissions. In CMake, during install, it installedOWNER_READ
permissions on headers, it resulted in permission error for other users - they were unable to read headers.libstdc++
withlibc++
Now
master
can be built and installed in the system without any problems.