How to export a debug and release library?
I have package A in workspace1, and i build the package using:
catkin_make -DCMAKE_BUILD_TYPE=Debug
When I try to compile package B in workspace2 using:
catkin_make -DCMAKE_BUILD_TYPE=Debug
Build fails with message:
CMake Error at /path/AConfig.cmake:141 (message):
Project 'B' tried to find library 'target_inside_A''. The library is
neither a target nor built/installed properly. Did you compile project
'A'? Did you find_package() it before the subdirectory containing
its code is included?
same issue when building with catkin_make_isolated a workspace with both packages inside (catkin_make compilation runs clean).
I don't know if this behaviour is by catkin design or if it's a bug, or if it's all my fault.
I'm using ROS indigo on debian, compiled by source.
I've also tested in ROS groovy on ubuntu 12.10.
I don't suppose it would be possible for you to post your code even, if it is anonymized, or a minimal example which reproduces this? Unfortunately, I can't imagine what the issue is or what to recommend without the contents of your CMakeLists.txt for each.
I'm so sorry, I missed to tell that you should set a debug postfix to see the issue.
i was missing the point because the library is huge, and I've only worked on the catkinization.
here is a minimal example of the setup:
https://www.dropbox.com/sh/igs20bc3v0...
ps: i don't know how to upload files, so i've used dropbox... if there is a better way to share the workspace tell me...
I can compile your example with ROS Indigo perfectly fine - also when setting the build type to "Debug". Since groovy has been EOLed I don't maintain a VM to test with it anymore.
Have you tried catkin_make_isolated -DCMAKE_BUILD_TYPE=Debug? Please consider to run it on a clean workspace to avoid side effects (it seemes that if the release libraries exists, the linker uses them instead of Debug version). With catkin_make it works perfectly, the problem is the isolation...