Changes between Version 1 and Version 2 of WikiStart/Toolchain/CMakeMacros


Ignore:
Timestamp:
04/19/11 10:31:57 (9 years ago)
Author:
sylvain.joyeux
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • WikiStart/Toolchain/CMakeMacros

    v1 v2  
    11||'''Subject'''||'''UseOrocos-RTT.cmake'''||'''Rock.cmake'''|| 
    22||Dependency tracking||use dependencies from manifest.xml by translating into pkg-config, orocos_use_package||dependencies are listed in the rock_executable or rock_library macro. Handles three types of dependencies: CMake (find_package), pkg-config and internal (dependencies between two targets in the same cmake package)|| 
    3 ||pkg-config||Autogenerated with all library targets produced in the package||Hand-made, with the help of some CMake variables (i.e. the default template produces the same result than the UseOrocos-RTT.cmake, but can be customized)|| 
    4 ||Qt integration||None||Special support (QT_HEADERS or something like that)|| 
     3||pkg-config file||Autogenerated with all library targets produced in the package||Hand-made, with the help of some CMake variables (i.e. the default template produces the same result than the UseOrocos-RTT.cmake, but can be customized). Variables available on a per-target basis (not global basis)|| 
     4||Qt integration||None||Special support|| 
    55 
    66= Open Questions = 
    77 * autoproj allows packages to be defined in subdirectories (e.g. slam/envire). How does orocos_use_package handles that ? 
     8 * what about dependencies that are not libraries (no pkg-config file) ? 
    89 * Qt integration (very important for us)