barcaroller wrote:
"Eric Noulard" wrote:
What is the final reason that makes you want to avoid the "monstrosities"?
I do not want the __FILE__ macro to reveal the structure of the project.
Also, I'm trying to keep the log file entries short.
I guess I can wrap __FILE__ with another macro that extracts relative
pathnames, but I was hoping to just use cmake's CMAKE_USE_RELATIVE_PATHS
since it is available.
I see, sorry.... It is really hard to make everything work with
relative paths, and you don't get that much out of it, except lots of
maintenance issues and corner cases that do not work... Sounds like
doing it from the C/C++ code would be the best way for you to go.
-Bill
_______________________________________________
Powered by www.kitware.com
Visit other Kitware open-source projects at
http://www.kitware.com/opensource/opensource.html
Please keep messages on-topic and check the CMake FAQ at:
http://www.cmake.org/Wiki/CMake_FAQ
Follow this link to subscribe/unsubscribe:
http://www.cmake.org/mailman/listinfo/cmake
