Join GitHub today
GitHub is home to over 50 million developers working together to host and review code, manage projects, and build software together.Sign up
Clean build system and installation #213
In trac we have a milestone
In order to solve the contained tickets, I rewrote the build system from scratch
Every build configuration, that was possible before, should be possible with the cmake version, too. I tried to keep most of the work-flows intact. For NEST installation details, please see INSTALL.
The trac tickets that should be solved by this PR:
Partly or not solved trac issues from this milestone:
The GitHub Issues affected by this:
creates targets: * make package # creates a binary package * make package_source # creates a packages from the source also adding custom target `make dist` which calls `make package_source` for script compatibility also let doc be generated in Source as `doc/Makefile.am` suggests create new rcsinfo.sli before...
I improved compilation on BG/Q with the last commits. Please see
@heplesser I saw the deprecation flag, but ignored it as it keeps the code cleaner. This email clarifies the deprecation flag. Maybe I should go through the code and see, where which dependancy is actually used.
@tammoippen I tried to build
On first try, I did not specify which compiler to use when running
Couldn't CMake pick up the compiler information from
With the compiler flag in place, compilation went well, but CMake chose
With that in place, everything works (OSX 10.10, g++-5 from Homebrew).
@heplesser Commit 3ca304d should solve the compiler selection:
I cannot reproduce this. Sometimes the build directory is confused from previous failed runs. Try to
@tammoippen The compiler is now detected properly. I have also understood the problem with the prefix. The relevant code is
Note that unless
I would suggest that we just drop the check and unconditionally use the value in