Hello.
The OCL installation have changed in 2.1.1. The libs go in lib/orocos/orocos-ocl.
I don't see how should i deploy my components ? For example i have a package Foo with components (like OCL and reporter, timer, ...), typekit, and transport. Should i make a lib/orocos/foo directory ? Where should go types ? In lib/orocos/types or lib/orocos/foo/types (so i export RTT_COMPONENTS_PATH to lib/orocos/foo) ?
Thank you for your help.
Paul.
About the lib/orocos/ organisation.
On Wednesday 17 November 2010 10:28:30 paul [dot] chavent [..] ... wrote:
> Hello.
>
> The OCL installation have changed in 2.1.1. The libs go in
> lib/orocos/orocos-ocl.
Are you sure about this ? This looks like the behaviour of the 'master'
branch, and not the toolchain-2.1 branch.
How did you download the release ? Using the bootstrap or the tar files ?
Peter
About the lib/orocos/
Oops, it was with the master branch. Sorry.
About the lib/orocos/ organisation.
Oops, it was with the master branch. Sorry.
About the lib/orocos/
On Wednesday 17 November 2010 13:08:24 paul [dot] chavent [..] ... wrote:
> Oops, it was with the master branch. Sorry.
I pushed the fix for master to gitorious. All should be back to 'normal'.
Peter
About the lib/orocos/ organisation.
On Wednesday 17 November 2010 10:28:30 paul [dot] chavent [..] ... wrote:
> Hello.
>
> The OCL installation have changed in 2.1.1. The libs go in
> lib/orocos/orocos-ocl.
The components, you mean. That's not good. We have to fix that asap, and
install OCL back in lib/orocos.
>
> I don't see how should i deploy my components ? For example i have a
> package Foo with components (like OCL and reporter, timer, ...), typekit,
> and transport. Should i make a lib/orocos/foo directory ? Where should go
> types ? In lib/orocos/types or lib/orocos/foo/types (so i export
> RTT_COMPONENTS_PATH to lib/orocos/foo) ?
For any other project than OCL, you would indeed install in lib/orocos/foo and
the types in lib/orocos/foo/types. With a simple import("foo") (in
TaskBrowser, or equivalent element in XML) you would load all its components
and types.
Peter
About the lib/orocos/ organisation.
On Wednesday 17 November 2010 10:45:10 Peter Soetens wrote:
> On Wednesday 17 November 2010 10:28:30 paul [dot] chavent [..] ... wrote:
> > Hello.
> >
> > The OCL installation have changed in 2.1.1. The libs go in
> > lib/orocos/orocos-ocl.
>
> The components, you mean. That's not good. We have to fix that asap, and
> install OCL back in lib/orocos.
>
> > I don't see how should i deploy my components ? For example i have a
> > package Foo with components (like OCL and reporter, timer, ...), typekit,
> > and transport. Should i make a lib/orocos/foo directory ? Where should go
> > types ? In lib/orocos/types or lib/orocos/foo/types (so i export
> > RTT_COMPONENTS_PATH to lib/orocos/foo) ?
>
> For any other project than OCL, you would indeed install in lib/orocos/foo
> and the types in lib/orocos/foo/types. With a simple import("foo") (in
> TaskBrowser, or equivalent element in XML) you would load all its
> components and types.
Does the import("foo") already work with ros packages?
Ruben
About the lib/orocos/ organisation.
On Wednesday 17 November 2010 14:26:50 Ruben Smits wrote:
> On Wednesday 17 November 2010 10:45:10 Peter Soetens wrote:
> > On Wednesday 17 November 2010 10:28:30 paul [dot] chavent [..] ... wrote:
> > > Hello.
> > >
> > > The OCL installation have changed in 2.1.1. The libs go in
> > > lib/orocos/orocos-ocl.
> >
> > The components, you mean. That's not good. We have to fix that asap, and
> > install OCL back in lib/orocos.
> >
> > > I don't see how should i deploy my components ? For example i have a
> > > package Foo with components (like OCL and reporter, timer, ...),
> > > typekit, and transport. Should i make a lib/orocos/foo directory ?
> > > Where should go types ? In lib/orocos/types or lib/orocos/foo/types
> > > (so i export RTT_COMPONENTS_PATH to lib/orocos/foo) ?
> >
> > For any other project than OCL, you would indeed install in
> > lib/orocos/foo and the types in lib/orocos/foo/types. With a simple
> > import("foo") (in TaskBrowser, or equivalent element in XML) you would
> > load all its components and types.
>
> Does the import("foo") already work with ros packages?
Yes. It's only on OCL's master.
Peter
About the lib/orocos/ organisation.
On Nov 17, 2010, at 04:45 , Peter Soetens wrote:
> On Wednesday 17 November 2010 10:28:30 paul [dot] chavent [..] ... wrote:
>> Hello.
>>
>> The OCL installation have changed in 2.1.1. The libs go in
>> lib/orocos/orocos-ocl.
>
> The components, you mean. That's not good. We have to fix that asap, and
> install OCL back in lib/orocos.
>
>>
>> I don't see how should i deploy my components ? For example i have a
>> package Foo with components (like OCL and reporter, timer, ...), typekit,
>> and transport. Should i make a lib/orocos/foo directory ? Where should go
>> types ? In lib/orocos/types or lib/orocos/foo/types (so i export
>> RTT_COMPONENTS_PATH to lib/orocos/foo) ?
>
> For any other project than OCL, you would indeed install in lib/orocos/foo and
> the types in lib/orocos/foo/types. With a simple import("foo") (in
> TaskBrowser, or equivalent element in XML) you would load all its components
> and types.
Then does OCL have a special-case installation, that normal users should not base their own application's on?
S
About the lib/orocos/ organisation.
On Wednesday 17 November 2010 13:31:18 S Roderick wrote:
> On Nov 17, 2010, at 04:45 , Peter Soetens wrote:
> > On Wednesday 17 November 2010 10:28:30 paul [dot] chavent [..] ... wrote:
> >> Hello.
> >>
> >> The OCL installation have changed in 2.1.1. The libs go in
> >> lib/orocos/orocos-ocl.
> >
> > The components, you mean. That's not good. We have to fix that asap, and
> > install OCL back in lib/orocos.
> >
> >> I don't see how should i deploy my components ? For example i have a
> >> package Foo with components (like OCL and reporter, timer, ...),
> >> typekit, and transport. Should i make a lib/orocos/foo directory ?
> >> Where should go types ? In lib/orocos/types or lib/orocos/foo/types (so
> >> i export RTT_COMPONENTS_PATH to lib/orocos/foo) ?
> >
> > For any other project than OCL, you would indeed install in
> > lib/orocos/foo and the types in lib/orocos/foo/types. With a simple
> > import("foo") (in TaskBrowser, or equivalent element in XML) you would
> > load all its components and types.
>
> Then does OCL have a special-case installation, that normal users should
> not base their own application's on? S
Yes.
Normal users just use the orocos_component() macro from UseOrocos.cmake. That
macro by default installs a component in lib/orocos/${PROJECT_NAME}. If you
want to override it, use:
orocos_component( mycomponent source.cpp INSTALL lib/orocos/....)
OCL is special case, in that all OCL components are to be loaded by default,
therefore they are installed in lib/orocos.
Peter
About the lib/orocos/ organisation.
On Nov 17, 2010, at 08:17 , Peter Soetens wrote:
> On Wednesday 17 November 2010 13:31:18 S Roderick wrote:
>> On Nov 17, 2010, at 04:45 , Peter Soetens wrote:
>>> On Wednesday 17 November 2010 10:28:30 paul [dot] chavent [..] ... wrote:
>>>> Hello.
>>>>
>>>> The OCL installation have changed in 2.1.1. The libs go in
>>>> lib/orocos/orocos-ocl.
>>>
>>> The components, you mean. That's not good. We have to fix that asap, and
>>> install OCL back in lib/orocos.
>>>
>>>> I don't see how should i deploy my components ? For example i have a
>>>> package Foo with components (like OCL and reporter, timer, ...),
>>>> typekit, and transport. Should i make a lib/orocos/foo directory ?
>>>> Where should go types ? In lib/orocos/types or lib/orocos/foo/types (so
>>>> i export RTT_COMPONENTS_PATH to lib/orocos/foo) ?
>>>
>>> For any other project than OCL, you would indeed install in
>>> lib/orocos/foo and the types in lib/orocos/foo/types. With a simple
>>> import("foo") (in TaskBrowser, or equivalent element in XML) you would
>>> load all its components and types.
>>
>> Then does OCL have a special-case installation, that normal users should
>> not base their own application's on? S
>
> Yes.
>
> Normal users just use the orocos_component() macro from UseOrocos.cmake. That
> macro by default installs a component in lib/orocos/${PROJECT_NAME}. If you
> want to override it, use:
> orocos_component( mycomponent source.cpp INSTALL lib/orocos/....)
>
> OCL is special case, in that all OCL components are to be loaded by default,
> therefore they are installed in lib/orocos.
Is that policy what all users want? Why isn't OCL just like any other library built on top of RTT?
S
About the lib/orocos/ organisation.
On Wednesday 17 November 2010 14:22:45 Stephen Roderick wrote:
> On Nov 17, 2010, at 08:17 , Peter Soetens wrote:
> > On Wednesday 17 November 2010 13:31:18 S Roderick wrote:
> >> On Nov 17, 2010, at 04:45 , Peter Soetens wrote:
> >>> On Wednesday 17 November 2010 10:28:30 paul [dot] chavent [..] ... wrote:
> >>>> Hello.
> >>>>
> >>>> The OCL installation have changed in 2.1.1. The libs go in
> >>>> lib/orocos/orocos-ocl.
> >>>
> >>> The components, you mean. That's not good. We have to fix that asap,
> >>> and install OCL back in lib/orocos.
> >>>
> >>>> I don't see how should i deploy my components ? For example i have a
> >>>> package Foo with components (like OCL and reporter, timer, ...),
> >>>> typekit, and transport. Should i make a lib/orocos/foo directory ?
> >>>> Where should go types ? In lib/orocos/types or lib/orocos/foo/types
> >>>> (so i export RTT_COMPONENTS_PATH to lib/orocos/foo) ?
> >>>
> >>> For any other project than OCL, you would indeed install in
> >>> lib/orocos/foo and the types in lib/orocos/foo/types. With a simple
> >>> import("foo") (in TaskBrowser, or equivalent element in XML) you would
> >>> load all its components and types.
> >>
> >> Then does OCL have a special-case installation, that normal users should
> >> not base their own application's on? S
> >
> > Yes.
> >
> > Normal users just use the orocos_component() macro from UseOrocos.cmake.
> > That macro by default installs a component in
> > lib/orocos/${PROJECT_NAME}. If you want to override it, use:
> > orocos_component( mycomponent source.cpp INSTALL lib/orocos/....)
> >
> > OCL is special case, in that all OCL components are to be loaded by
> > default, therefore they are installed in lib/orocos.
>
> Is that policy what all users want? Why isn't OCL just like any other
> library built on top of RTT? S
That's my vision too. But for backwards compatibility and also to make it a
little bit easier on newcommers, I wanted to leave it like it was. OCL is a
bit different than the others, since it contains only infrastructural
components and not something application specific. YMMV.
Pete
About the lib/orocos/ organisation.
Hello.
The OCL installation have changed in 2.1.1. The libs go in lib/orocos/orocos-ocl.
I don't see how should i deploy my components ? For example i have a package Foo with components (like OCL and reporter, timer, ...), typekit, and transport. Should i make a lib/orocos/foo directory ? Where should go types ? In lib/orocos/types or lib/orocos/foo/types (so i export RTT_COMPONENTS_PATH to lib/orocos/foo) ?
Thank you for your help.
Paul.