Gonzalo,
Could you please elaborate, where should I check it? Will CMake indeed generate
-L/usr/local/lib argument for the linker if it sees something in
LD_LIBRARY_PATH?
Do you have any insight why other flags (-arch, -isysroot) get generated in one
environment, but not the other?
WBR Oleg Zhylin [email protected]
On Sunday, August 23, 2015 8:10 PM, Oleg Zhylin <[email protected]> wrote:
I have a CMake C++ dylib project that builds correctly in one MacOS X
environment but fails in another. Environments are on the same machine, but
under different users. I'm seeking help how to do I troubleshoot where the
failure in the second one comes from.What I managed to figure out is that in
failing configuration CMake adds the following flags in link.txt (the commands
used to link the executable)-arch x86_64
-isysroot
/Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX10.9.sdk
-mmacosx-version-min=10.6
-L/usr/local/lib
The last one causes havoc as it makes ld pick up dependencies from
/usr/local/lib instead of link directories I configured in CMake.I would
appreciate any insight what triggers generating the flags above and what is the
best way to squelch them, especially -L/usr/local/lib? WBR Oleg Zhylin
[email protected]
--
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
