ocl 2.3.1 : Install in include/orocos/ocl instead of orocos/include/ocl

Hi,

I'm testing orocos 2.3.1 on MSVC and linux for my apps. I found that
orocos-ocl is installing under "include/orocos/ocl" instead of include/ocl
as before. The problem is the same for libraries of ocl.

Is it wanted?

I was using :

include_directories(${OROCOS-RTT_INCLUDE_DIRS})

in my cmake file, and after I can add :

#include <ocl/Taskbrowser.hpp>.

Is I'm suppose to use another CMake variable for the include directory?

May you help me?

ocl 2.3.1 : Install in include/orocos/ocl instead of orocos/incl

On Friday 01 April 2011 17:54:58 Simon Pelletier-Thibault wrote:
> Hi,
>
> I'm testing orocos 2.3.1 on MSVC and linux for my apps. I found that
> orocos-ocl is installing under "include/orocos/ocl" instead of include/ocl
> as before. The problem is the same for libraries of ocl.
>
> Is it wanted?
>
> I was using :
>
> include_directories(${OROCOS-RTT_INCLUDE_DIRS})
>
> in my cmake file, and after I can add :
>
> #include <ocl/Taskbrowser.hpp>.
>
> Is I'm suppose to use another CMake variable for the include directory?
>
> May you help me?

I see only two options:
- add include/orocos to the OROCOS-RTT_INCLUDE_DIRS
- add a new cmake variable OROCOS_INCLUDE_DIRS that contains include/orocos

I think it's best to go for the first option, which best supports the present
use of these macros. So I pushed the addition of .../include/orocos to OROCOS-
RTT_INCLUDE_DIRS to the toolchain-2.3 branch.

Peter

ocl 2.3.1 : Install in include/orocos/ocl instead of orocos/incl

2011/4/1 Simon Pelletier-Thibault <simon [dot] pelletiert [..] ...>

> Hi,
>
> I'm testing orocos 2.3.1 on MSVC and linux for my apps. I found that
> orocos-ocl is installing under "include/orocos/ocl" instead of include/ocl
> as before. The problem is the same for libraries of ocl.
>
> Is it wanted?
>
> I was using :
>
> include_directories(${OROCOS-RTT_INCLUDE_DIRS})
>
> in my cmake file, and after I can add :
>
> #include <ocl/Taskbrowser.hpp>.
>
> Is I'm suppose to use another CMake variable for the include directory?
>
> May you help me?
>
>
The "orocos" folder is wanted, but should not change any of your C code (I
mean you are not supposed to do #include "orocos/ocl/....h"). How are you
adding Orocos to your CMakes ? There is "find_package" stuff that do
everything for you.

> --
> Orocos-Users mailing list
> Orocos-Users [..] ...
> http://lists.mech.kuleuven.be/mailman/listinfo/orocos-users
>
>

Ruben Smits's picture

Hi,there seems still to an

On Thursday 21 April 2011 11:32:23 joerg [..] ... wrote:
> Hi,
>
> there seems still to an issue with the include path for OCL!!!
>
> When I try to compile the hello-7-deployment from the rtt-exercises I get an
> error for "#include <ocl/Component.hpp>" saying the the file could not be
> found.

The use of <ocl/Component.hpp> is deprecated, you should use
<rtt/Component.hpp> from now on. The header is not OCL specific so it has been
moved to RTT to get rid of the unneeded dependency on OCL for component
implementations

-- Ruben

> However the Hello-1.. and Hello-2.. are working fine.
> I placed for a test the line 'orocos_use_package(ocl-taskbrowser)' in the
> CMakeLits.txt of Hello-7-deployment, just before 'orocos_component(hello
> Hello.cpp)' and than I could compile the example.
>
> I think this is not the intended way of doing this . . .
>
> Is there a separate "CMake-Statement" to include the OCL stuff or should it
> just be done by 'find_package(Orocos-RTT REQUIRED \${RTT_HINTS})' and
> 'include(${OROCOS-RTT_USE_FILE_PATH}/UseOROCOS-RTT.cmake)' ????
>
> Ciao
> Joerg
>
> Computer are like air conditioner, they stop working properly when opening
> windows

Hi,there seems still to an

Hi,

there seems still to an issue with the include path for OCL!!!

When I try to compile the hello-7-deployment from the rtt-exercises I get an error for "#include <ocl/Component.hpp>" saying the the file could not be found.

However the Hello-1.. and Hello-2.. are working fine. I placed for a test the line 'orocos_use_package(ocl-taskbrowser)' in the CMakeLits.txt of Hello-7-deployment, just before 'orocos_component(hello Hello.cpp)' and than I could compile the example.

I think this is not the intended way of doing this . . .

Is there a separate "CMake-Statement" to include the OCL stuff or should it just be done by 'find_package(Orocos-RTT REQUIRED \${RTT_HINTS})' and 'include(${OROCOS-RTT_USE_FILE_PATH}/UseOROCOS-RTT.cmake)' ????

Ciao Joerg

Computer are like air conditioner, they stop working properly when opening windows

Hi,there seems still to an

On Thursday 21 April 2011 11:32:23 joerg [..] ... wrote:
> Hi,
>
> there seems still to an issue with the include path for OCL!!!
>
> When I try to compile the hello-7-deployment from the rtt-exercises I get
> an error for "#include <ocl/Component.hpp>" saying the the file could not
> be found.

The manifest.xml lists ocl as a dependency, so it should find this header.

>
> However the Hello-1.. and Hello-2.. are working fine.
> I placed for a test the line 'orocos_use_package(ocl-taskbrowser)' in the
> CMakeLits.txt of Hello-7-deployment, just before 'orocos_component(hello
> Hello.cpp)' and than I could compile the example.
>
> I think this is not the intended way of doing this . . .
>
> Is there a separate "CMake-Statement" to include the OCL stuff or should it
> just be done by 'find_package(Orocos-RTT REQUIRED \${RTT_HINTS})' and
> 'include(${OROCOS-RTT_USE_FILE_PATH}/UseOROCOS-RTT.cmake)' ????

Normally, you list your dependencies in the manifest.xml file. The useorocos
macros will then lookup the .pc file for that dependency and add the include
paths automatically. If you don't want to use the manifest, you can have the
same behavior by writing orocos_use_package( ocl ).

Are you working in a ROS_ROOT environment ? How did you build/install OCL ?

Peter

Re: Hi,there seems still to an

peter wrote:
On Thursday 21 April 2011 11:32:23 joerg [..] ... wrote: > Hi, > > there seems still to an issue with the include path for OCL!!! > > When I try to compile the hello-7-deployment from the rtt-exercises I get > an error for "#include <ocl/Component.hpp>" saying the the file could not > be found.

The manifest.xml lists ocl as a dependency, so it should find this header.

I did not remove anything, but also did not check for manifest.xml

peter wrote:
> > However the Hello-1.. and Hello-2.. are working fine. > I placed for a test the line 'orocos_use_package(ocl-taskbrowser)' in the > CMakeLits.txt of Hello-7-deployment, just before 'orocos_component(hello > Hello.cpp)' and than I could compile the example. > > I think this is not the intended way of doing this . . . > > Is there a separate "CMake-Statement" to include the OCL stuff or should it > just be done by 'find_package(Orocos-RTT REQUIRED \${RTT_HINTS})' and > 'include(${OROCOS-RTT_USE_FILE_PATH}/UseOROCOS-RTT.cmake)' ????

Normally, you list your dependencies in the manifest.xml file. The useorocos macros will then lookup the .pc file for that dependency and add the include paths automatically. If you don't want to use the manifest, you can have the same behavior by writing orocos_use_package( ocl ).

Are you working in a ROS_ROOT environment ? How did you build/install OCL ?

Peter

I don't use the ROS_ROOT environment, I just boostapped the toolchain and worked through the rtt_exercises . . . .

I used right now Kubuntu 10.10 with Eclipse and got it running pretty easy . .

However I did build the rtt and ocl on windows too and that was not so straight forward any more. There I had to face the "orocos/ocl" path problem too and ended up by just making a copy of "include/orocos/ocl" to "include/ocl" . . .. . . not nice but worked for the start . . ..

 
Joerg

Computer are like air conditioner, they stop working properly when opening windows