Hello, I use the ExternalProject_Add command to manage third-party libraries. In the same time, I need to overcome some compatibility problems between GCC 4 and GCC 5 (strings are not defined in the same way in the STL). The solution I use is the one given here: http://stackoverflow.com/questions/33500337/how-to-handle-dual-abi-in-gcc-5 It allows me to force to use the libstdc++.so given by the GCC repository given to the cmake command.
The problem is that trick does not work with the ExternalProject_Add command because configuration steps of third-party libraries are autonomous. Do you know how to solve the problem? For example, if I use the ExternalProject_Add command to manage a third-library whose configuration also depends on a cmake script, how could I tell this script to use the compilers and the libstdc++.so I provided to my own cmake script? Best, Cédric
-- 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://public.kitware.com/mailman/listinfo/cmake
