Re: Orocos integration in buildroot

i, Feb 1, 2013 at 1:47 PM, Willy Lambert <[email protected]> wrote:
> [snip]
>
> I managed to build rtt and ocl. I still have one issue : my ROS_ROOT
> is defined because I have my standard developpment toolchain there in
> a ROS build system. But when I build with Buildroot, I have my
> CMAKE_INSTALL_PREFIX that is "forced" by this (in rtt/CmakeLists.txt)
> :
>
> # We force it in case of ROS builds because the UseOrocos.cmake
> scripts will always look
> # in this path, also during an autoproj/bootstrap build.
> IF(ROS_ROOT)
>   SET(CMAKE_INSTALL_PREFIX
>     ${PROJECT_SOURCE_DIR}/../install CACHE PATH "Orocos install prefix
> for ROS builds" FORCE
>     )
> [snip] ...
>
>   endif()
> ENDIF(ROS_ROOT)
>
>
> In the best world, I would like to set something in CMake cache to ask
> it not to take ROS_ROOT into account, are you interested in such a
> feature ?

We currently use the flag IS_ROS_PACKAGE which is only true if
ROS_ROOT is set and the current directory is in the ROS_PACKAGE_PATH.

However, this flag is 'calculated' in the UseOrocos.cmake file, which
is not used by RTT itself. OCL and all others do use it. So it's only
an issue for RTT, so there you could force ROS out with a cmake flag.

> In the worst world, I have to unset ROS_ROOT locally before building
> with Buildroot. The problem is that I don't really have a way to
> automate this, so if someone use buildroot with ros it will fail.

That would break importing ROS packages in 2.6, since in 2.6, RTT has
the component loading code and depends on the ROS_ROOT variable to see
if roslib/rospack is available.

Peter
-- 
Orocos-Dev mailing list
[email protected]
http://lists.mech.kuleuven.be/mailman/listinfo/orocos-dev