Re: Orocos integration in buildroot

2013/2/1 Willy Lambert <[email protected]>:
> [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 ?
> 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.


I think I'm done for review. Before sending this to Buildroot dev
list, I would like to publish my work here to have some comments.
There are very few file (mainly makefile wrappers and kernel type
configuration menus)
Here is my github clone :
https://github.com/wixiw/buildroot

The only things to checks are 3 directories  :
package/orocos-log4cpp
package/orocos-rtt
package/orocos-ocl

The Config.in is the file that describe the menu that will be used by
buildroot users to select Orocos, so I need a reviews on this to check
if my comments are good, and if option selection are ok.
The *.mk are the makefile wrappers that will do the build. There is
little thing to review as it is mainly Buildroot stuff.

It's currently freezed on the 2.5 version, but of course, there is
nothing blocking this except that it is the working version on my
robot so I prefer setting up all this before updating to more recent
one. I'll post this to Buildroot in a week, let me know if you are
willing more time to review or just don't care.
-- 
Orocos-Dev mailing list
[email protected]
http://lists.mech.kuleuven.be/mailman/listinfo/orocos-dev