MantisBT - CMake
View Issue Details
IDProjectCategoryView StatusDate SubmittedLast Update
0013303CMakeCMakepublic2012-06-14 11:092016-06-10 14:31
Reportertree 
Assigned ToKitware Robot 
PrioritynormalSeverityminorReproducibilityalways
StatusclosedResolutionmoved 
PlatformApple MacOSOS XOS Version10.4.10
Product VersionCMake 2.8.8 
Target VersionFixed in Version 
Summary0013303: Strange issues when using "target_link_libraries" to link stlport and boost on XCode 4
DescriptionI orgnize stlport libraries in two directories like:
stlport/Debug/libstlportstlg.5.2.1.dylib (represented as A)
stlport/Release/libstlport.5.2.dylib (represented as B)

and then use command
target_link_libraries(taget debug ${A})
target_link_libraries(taget optimized ${B})

After generating XCode project, I found in "Building Settings/Other Linker Flags", both the two libraries exist under both "Debug" and "RelWithDebInfo".

In happens to boost either. But for other libraries it works as expected.
Steps To Reproduce
Additional Information
TagsNo tags attached.
Relationships
Attached Files
Issue History
Date ModifiedUsernameFieldChange
2012-06-14 11:09treeNew Issue
2012-06-14 17:01Brad KingNote Added: 0029698
2012-08-11 21:42David ColeStatusnew => backlog
2012-08-11 21:42David ColeNote Added: 0030441
2016-06-10 14:28Kitware RobotNote Added: 0042065
2016-06-10 14:28Kitware RobotStatusbacklog => resolved
2016-06-10 14:28Kitware RobotResolutionopen => moved
2016-06-10 14:28Kitware RobotAssigned To => Kitware Robot
2016-06-10 14:31Kitware RobotStatusresolved => closed

Notes
(0029698)
Brad King   
2012-06-14 17:01   
I cannot reproduce this:
$ cmake --version
cmake version 2.8.8

$ find ../Issue13303 -type f
../Issue13303/CMakeLists.txt
../Issue13303/foo.c
../Issue13303/stlport/Debug/libstlportstlg.5.2.1.dylib
../Issue13303/stlport/Release/libstlport.5.2.dylib

$ cat ../Issue13303/CMakeLists.txt
cmake_minimum_required(VERSION 2.8)
project(FOO C)

add_executable(foo foo.c)
target_link_libraries(foo debug ${FOO_SOURCE_DIR}/stlport/Debug/libstlportstlg.5.2.1.dylib)
target_link_libraries(foo optimized ${FOO_SOURCE_DIR}/stlport/Release/libstlport.5.2.dylib)

$ cmake ../Issue13303 -GXcode

$ grep OTHER_LDFLAGS FOO.xcodeproj/project.pbxproj
 OTHER_LDFLAGS = "  -Wl,-search_paths_first -Wl,-headerpad_max_install_names \".../Issue13303/stlport/Debug/libstlportstlg.5.2.1.dylib\"";
 
OTHER_LDFLAGS = "  -Wl,-search_paths_first -Wl,-headerpad_max_install_names \".../Issue13303/stlport/Release/libstlport.5.2.dylib\"";
 
OTHER_LDFLAGS = "  -Wl,-search_paths_first -Wl,-headerpad_max_install_names \".../Issue13303/stlport/Release/libstlport.5.2.dylib\"";
 
OTHER_LDFLAGS = "  -Wl,-search_paths_first -Wl,-headerpad_max_install_names \".../Issue13303/stlport/Release/libstlport.5.2.dylib\"";


Please provide a minimal source tarball that reproduces the problem.
(0030441)
David Cole   
2012-08-11 21:42   
Sending old, never assigned issues to the backlog.

(The age of the bug, plus the fact that it's never been assigned to anyone means that nobody is actively working on it...)

If an issue you care about is sent to the backlog when you feel it should have been addressed in a different manner, please bring it up on the CMake mailing list for discussion. Sign up for the mailing list here, if you're not already on it: http://www.cmake.org/mailman/listinfo/cmake [^]

It's easy to re-activate a bug here if you can find a CMake developer who has the bandwidth to take it on, and ferry a fix through to our 'next' branch for dashboard testing.
(0042065)
Kitware Robot   
2016-06-10 14:28   
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.