Upon further reflection the abs paths for every lib is absolutely not
defensible.
1) Pass only the short lib name to target_link_libraries
2) Add absolute path to future target_link_directories if you must
Then it's one (1) long path on the command line string and not N long paths
fore each lib
I seriously can't believe in 2017 I am actually having this conversation.
Did I miss something here or does Kitware really mean to have package
maintainers spec
target_link_libraries(
targ
INTERFACE
C:\projects\lib1\install\lib\lib1
C:\projects\lib1\install\lib\lib2
C:\projects\lib1\install\lib\lib3
)
and not
target_link_libraries(
targ
INTERFACE
lib1
lib2
lib3
)
target_link_directories( targ INTERFACE C:\projects\lib1\install\lib )
Does Kitware understand the length problem on command line tools and get
the difference I am trying to convey here? As far as cmd line would go
"one of these is not like the other", but would have same effect. If
implemented for projs like ITK maybe I could build is a place other than C:\
--
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
