> Sorry, I don't really understand your question. What generated file names, > and > what external sources ?
I mean with an external source here a directory which is not directly managed and controlled by the build system. I see installation directories as a well-known example for the use case when you occasionally compare the run time behaviour of an installed library to a freshly built one. The build system encapsulates file name conventions (and file formats) for the software generation. I would like to reuse such knowledge so that I can also refer to libraries from other sources in a generic way. > Or, since you are it seems mixing C and C++, you have a problem with symbol > naming. Thanks for your hint. I'm sorry that I overlooked an other preprocessor symbol which is relevant here. My evolving CMake scripts show better results now. Regards, Markus -- Powered by www.kitware.com Please keep messages on-topic and check the CMake FAQ at: http://www.cmake.org/Wiki/CMake_FAQ Kitware offers various services to support the CMake community. For more information on each offering, please visit: CMake Support: http://cmake.org/cmake/help/support.html CMake Consulting: http://cmake.org/cmake/help/consulting.html CMake Training Courses: http://cmake.org/cmake/help/training.html Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Follow this link to subscribe/unsubscribe: http://www.cmake.org/mailman/listinfo/cmake
