I'm merging the ocl-debian branch to trunk/ocl in order to prepare the
ocl-1.4.0 release. For all component developers: note that some CMake macros
have been added such that each ocl component library gets a -
For example, liborocos-taskcontext.so becomes
liborocos-taskcontext-gnulinux.so . This allows to install multiple targets
in /usr/lib, which is required for Debian packaging.
This has mainly influence on the TARGET_LINK_LIBRARIES macro, which should no
longer be used. Instead use COMPONENT_ADD_DEPS, with the same arguments.
If you need to use TARGET_LINK_LIBRARIES anyway, use it with
the -${OROCOS_TARGET} appendix:
TARGET_LINK_LIBRARIES( orocos-robot-${TARGET} myroblib )
Peter
OCL Debian merge / linking libraries
On Monday 19 November 2007 17:23:41 Peter Soetens wrote:
[...]
> This has mainly influence on the TARGET_LINK_LIBRARIES macro, which should
> no longer be used. Instead use COMPONENT_ADD_DEPS, with the same arguments.
>
> If you need to use TARGET_LINK_LIBRARIES anyway, use it with
> the -${OROCOS_TARGET} appendix:
>
> TARGET_LINK_LIBRARIES( orocos-robot-${TARGET} myroblib )
Actually, you can use the macros
COMPONENT_ADD_LIBS: for linking components with external libraries and
PROGRAM_ADD_DEPS: for linking programs (tests,...) with orocos components.
i.e.
COMPONENT_ADD_LIBS ==> link with component external library
[PROGRAM|COMPONENT]_ADD_DEPS ==> link X with orocos-ocl component.
These CMake macros are only meant for use within OCL.
Peter