MantisBT - CMake
View Issue Details
IDProjectCategoryView StatusDate SubmittedLast Update
0015713CMakeCMakepublic2015-08-26 18:282016-06-10 14:31
Reporterovz 
Assigned ToKitware Robot 
PrioritynormalSeveritymajorReproducibilityalways
StatusclosedResolutionmoved 
PlatformOSXOSOS Version
Product VersionCMake 3.2.3 
Target VersionFixed in Version 
Summary0015713: CMake generates “-L/usr/local/lib” on Mac OSX
DescriptionCould you please help me with the question I asked on the mailing list. http://public.kitware.com/pipermail/cmake/2015-August/061413.html. [^] The question is also pasted into Steps to Reproduce for convenience.

I'm still at loss what triggers CMake to generate -L/usr/local/lib linker flag.
Steps To ReproduceI 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?
Additional Information
TagsNo tags attached.
Relationships
Attached Files
Issue History
Date ModifiedUsernameFieldChange
2015-08-26 18:28ovzNew Issue
2016-06-10 14:29Kitware RobotNote Added: 0042828
2016-06-10 14:29Kitware RobotStatusnew => resolved
2016-06-10 14:29Kitware RobotResolutionopen => moved
2016-06-10 14:29Kitware RobotAssigned To => Kitware Robot
2016-06-10 14:31Kitware RobotStatusresolved => closed

Notes
(0042828)
Kitware Robot   
2016-06-10 14:29   
Resolving issue as `moved`.

This issue tracker is no longer used. Further discussion of this issue may take place in the current CMake Issues page linked in the banner at the top of this page.