Fixes to build it on openSUSE/Packman.#67
Conversation
jobermayr
commented
May 9, 2016
- Support different BINDIR, INCLUDEDIR and LIBDIR on install
- Take right python dir on x86_64 arch
- Fix build against Boost >= 1.58
- Make it possible to build libIfcGeom shared to reduce size of dependent binaries
- Fix INSTALL_RPATH
- Fix some more compiler warnings
| if (NOT APPLE) | ||
| set(LIB_RT "rt") | ||
| endif() | ||
| set(OPENCASCADE_LIBRARIES ${OPENCASCADE_LIBRARIES} ${OPENCASCADE_LIBRARIES} ${OPENCASCADE_LIBRARIES} ${CMAKE_THREAD_LIBS_INIT} ${LIB_RT} dl) |
There was a problem hiding this comment.
Hi Johannes, many thanks for your pr. Can you elaborate on this particular change? IIRC duplicating the libraries was necessary (at least on some versions of gcc) to make sure static libraries where properly searched for all (possibly cyclic) dependencies.
There was a problem hiding this comment.
You are right. Amended commit reverts it.
- Support different BINDIR, INCLUDEDIR and LIBDIR on install - Take right python dir on x86_64 arch - Fix build against Boost >= 1.58 - Make it possible to build libIfcGeom shared to reduce size of dependent binaries - Fix INSTALL_RPATH - Fix some more compiler warnings
|
Got a chance to run it on Windows, your macro seems to choke on my Windows paths seemingly thinking the path separators are escape characters: I am a bit puzzled how to fix this elegantly. Even if I try to add a Another option would be to skip this altogether on Windows, as I don't think anything like an rpath equivalent exists there anyway. On the other hand it would be nice if the macro deals with special characters better. Thoughts? |
|
Please set: Remember CMake doesn't support |
|
@Stinkfist0 do you have any thoughts on this? How does the build script currently process slashes? |
|
@aothms I think I have not paid any special attention to slashes in the scripts. I've assumed CMake automatically converts those for the env vars used for specifying the dependencies' locations, but actually now that looking in CMakeCache.txt it would appear that there are both slashes mixed. |
|
Is there anything I have to fix or do you accept CMake rules regarding (back)slashes in future? |
|
I will merge it as is and do a quick PS: Do you have an official reference on cmake's position on backslashes? |
|
Thanks. Was hoping for an actual documentation reference, but that might be difficult. The |