RTT/OCL code freeze

I have updated the version numbers to 2.2.0 on gitorious. I'll now start
preparing the release, update some docs etc. Note the message in the other
thread where I moved the carray.hpp header from internal to types. Since there
is a backwards compatibility header, there shouldn't be an issue here for
existing users.

I'm still waiting a fix from Markus on the OCL's getComponentTypes function. I
might revert the earlier patch if I ain't getting anything.

I've been working on two cheat-sheets: a general 'Orocos' one and an RTT
specific one. You can find them on their temporary location here:

http://people.mech.kuleuven.be/~psoetens/orocos/orocos_cheat_sheet.pdf
http://people.mech.kuleuven.be/~psoetens/orocos/rtt_cheat_sheet.pdf

The sources are in orocos-toolchain/rtt/doc . It's by no-one reviewed yet so
your input is welcome.

Peter

RTT/OCL code freeze

On Mon, Dec 06, 2010 at 05:48:47PM +0100, Peter Soetens wrote:

> I'm still waiting a fix from Markus on the OCL's getComponentTypes function. I
> might revert the earlier patch if I ain't getting anything.

Here it is (next mail)

Compiles but I can't really test because for some reason the
ocltypekit does not get loaded:

Deployer [S]> .types
Available data types: ConnPolicy FlowStatus PropertyBag SendHandle
SendStatus TaskContext array bool char double float int rt_string
string uint void
Deployer [S]> getComponentTypes ()
= (unknown_t)

Deployer [S]>

No bools, strings, etc. Any idea?

Markus

RTT/OCL code freeze

On Tuesday 07 December 2010 08:52:49 Markus Klotzbuecher wrote:
> On Mon, Dec 06, 2010 at 05:48:47PM +0100, Peter Soetens wrote:
> > I'm still waiting a fix from Markus on the OCL's getComponentTypes
> > function. I might revert the earlier patch if I ain't getting anything.
>
> Here it is (next mail)
>
> Compiles but I can't really test because for some reason the
> ocltypekit does not get loaded:
>
> Deployer [S]> .types
> Available data types: ConnPolicy FlowStatus PropertyBag SendHandle
> SendStatus TaskContext array bool char double float int rt_string
> string uint void
> Deployer [S]> getComponentTypes ()
> = (unknown_t)
>
> Deployer [S]>
>
> No bools, strings, etc. Any idea?

They were not in (the types subdir of) your component path.

If you type at the TB: path("/path/to/ocl-install/lib/orocos") does it find
them?

RTT looks for types in RTT's install path. OCL looks for types in OCL's
install path, so even if OCL and RTT are in different places, it should work.

Peter

RTT/OCL code freeze

On Tue, Dec 07, 2010 at 10:23:31AM +0100, Peter Soetens wrote:
> On Tuesday 07 December 2010 08:52:49 Markus Klotzbuecher wrote:
> > On Mon, Dec 06, 2010 at 05:48:47PM +0100, Peter Soetens wrote:
> > > I'm still waiting a fix from Markus on the OCL's getComponentTypes
> > > function. I might revert the earlier patch if I ain't getting anything.
> >
> > Here it is (next mail)
> >
> > Compiles but I can't really test because for some reason the
> > ocltypekit does not get loaded:
> >
> > Deployer [S]> .types
> > Available data types: ConnPolicy FlowStatus PropertyBag SendHandle
> > SendStatus TaskContext array bool char double float int rt_string
> > string uint void
> > Deployer [S]> getComponentTypes ()
> > = (unknown_t)
> >
> > Deployer [S]>
> >
> > No bools, strings, etc. Any idea?
>
> They were not in (the types subdir of) your component path.
>
> If you type at the TB: path("/path/to/ocl-install/lib/orocos") does it find
> them?

No. But when I do:

path("/home/mk/tmp/ocl/ocl-v2.1.1-163-g3d33162/lib/orocos/orocos-ocl")

it does. Somehow the install "lib" dir looks odd:

PMA-10-048 ~/tmp/ocl/ocl-v2.1.1-163-g3d33162 $ tree lib/
lib/
??? liborocos-deployment-gnulinux.so
??? liborocos-taskbrowser-gnulinux.so
??? orocos
?   ??? liborocos-helloworld-gnulinux.so
?   ??? liborocos-lua-gnulinux.so
?   ??? liborocos-ocl-common-gnulinux.so
?   ??? liborocos-reporting-gnulinux.so
?   ??? liborocos-timer-gnulinux.so
?   ??? orocos-ocl
?   ??? plugins
?   ?   ??? libos-gnulinux.so
?   ?   ??? libprint-gnulinux.so
?   ?   ??? librttlua-plugin-gnulinux.so
?   ??? types
?   ??? libocl-gnulinux.so
??? pkgconfig
??? orocos-ocl-gnulinux.pc

5 directories, 12 files

Why is there a orocos-ocl directory inside lib/orocos ?

> RTT looks for types in RTT's install path. OCL looks for types in OCL's
> install path, so even if OCL and RTT are in different places, it should work.

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

RTT/OCL code freeze

On Tuesday 07 December 2010 10:57:40 Markus Klotzbuecher wrote:
> On Tue, Dec 07, 2010 at 10:23:31AM +0100, Peter Soetens wrote:
> > On Tuesday 07 December 2010 08:52:49 Markus Klotzbuecher wrote:
> > > On Mon, Dec 06, 2010 at 05:48:47PM +0100, Peter Soetens wrote:
> > > > I'm still waiting a fix from Markus on the OCL's getComponentTypes
> > > > function. I might revert the earlier patch if I ain't getting
> > > > anything.
> > >
> > > Here it is (next mail)
> > >
> > > Compiles but I can't really test because for some reason the
> > > ocltypekit does not get loaded:
> > >
> > > Deployer [S]> .types
> > > Available data types: ConnPolicy FlowStatus PropertyBag SendHandle
> > > SendStatus TaskContext array bool char double float int rt_string
> > > string uint void
> > > Deployer [S]> getComponentTypes ()
> > >
> > > = (unknown_t)
> > >
> > > Deployer [S]>
> > >
> > > No bools, strings, etc. Any idea?
> >
> > They were not in (the types subdir of) your component path.
> >
> > If you type at the TB: path("/path/to/ocl-install/lib/orocos") does it
> > find them?
>
> No. But when I do:
>
> path("/home/mk/tmp/ocl/ocl-v2.1.1-163-g3d33162/lib/orocos/orocos-ocl")
>
> it does. Somehow the install "lib" dir looks odd:
>
> PMA-10-048 ~/tmp/ocl/ocl-v2.1.1-163-g3d33162 $ tree lib/
> lib/
> ??? liborocos-deployment-gnulinux.so
> ??? liborocos-taskbrowser-gnulinux.so
> ??? orocos
> ? ??? liborocos-helloworld-gnulinux.so
> ? ??? liborocos-lua-gnulinux.so
> ? ??? liborocos-ocl-common-gnulinux.so
> ? ??? liborocos-reporting-gnulinux.so
> ? ??? liborocos-timer-gnulinux.so
> ? ??? orocos-ocl
> ? ??? plugins
> ? ? ??? libos-gnulinux.so
> ? ? ??? libprint-gnulinux.so
> ? ? ??? librttlua-plugin-gnulinux.so
> ? ??? types
> ? ??? libocl-gnulinux.so
> ??? pkgconfig
> ??? orocos-ocl-gnulinux.pc
>
> 5 directories, 12 files
>
> Why is there a orocos-ocl directory inside lib/orocos ?

The UseOrocos.cmake macros install plugins and typekits in the
'lib/orocos/projectname/plugins' directory. OCL has as project name 'orocos-
ocl'. We treat OCL as a special case and want to install it in lib/orocos...

This was correctly done for the components, but not for the typekits and
plugins.

ROS-builds don't suffer from this because they don't install them.

I'm on it.

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

RTT/OCL code freeze

On Tuesday 07 December 2010 11:29:59 Peter Soetens wrote:
> On Tuesday 07 December 2010 10:57:40 Markus Klotzbuecher wrote:
> > On Tue, Dec 07, 2010 at 10:23:31AM +0100, Peter Soetens wrote:
> > > On Tuesday 07 December 2010 08:52:49 Markus Klotzbuecher wrote:
> > > > On Mon, Dec 06, 2010 at 05:48:47PM +0100, Peter Soetens wrote:
> > > > > I'm still waiting a fix from Markus on the OCL's getComponentTypes
> > > > > function. I might revert the earlier patch if I ain't getting
> > > > > anything.
> > > >
> > > > Here it is (next mail)
> > > >
> > > > Compiles but I can't really test because for some reason the
> > > > ocltypekit does not get loaded:
> > > >
> > > > Deployer [S]> .types
> > > > Available data types: ConnPolicy FlowStatus PropertyBag SendHandle
> > > > SendStatus TaskContext array bool char double float int rt_string
> > > > string uint void
> > > > Deployer [S]> getComponentTypes ()
> > > >
> > > > = (unknown_t)
> > > >
> > > > Deployer [S]>
> > > >
> > > > No bools, strings, etc. Any idea?
> > >
> > > They were not in (the types subdir of) your component path.
> > >
> > > If you type at the TB: path("/path/to/ocl-install/lib/orocos") does it
> > > find them?
> >
> > No. But when I do:
> > path("/home/mk/tmp/ocl/ocl-v2.1.1-163-g3d33162/lib/orocos/orocos-ocl")
> >
> > it does. Somehow the install "lib" dir looks odd:
> >
> > PMA-10-048 ~/tmp/ocl/ocl-v2.1.1-163-g3d33162 $ tree lib/
> > lib/
> > ??? liborocos-deployment-gnulinux.so
> > ??? liborocos-taskbrowser-gnulinux.so
> > ??? orocos
> > ? ??? liborocos-helloworld-gnulinux.so
> > ? ??? liborocos-lua-gnulinux.so
> > ? ??? liborocos-ocl-common-gnulinux.so
> > ? ??? liborocos-reporting-gnulinux.so
> > ? ??? liborocos-timer-gnulinux.so
> > ? ??? orocos-ocl
> > ? ??? plugins
> > ? ? ??? libos-gnulinux.so
> > ? ? ??? libprint-gnulinux.so
> > ? ? ??? librttlua-plugin-gnulinux.so
> > ? ??? types
> > ? ??? libocl-gnulinux.so
> > ??? pkgconfig
> >
> > ??? orocos-ocl-gnulinux.pc
> >
> > 5 directories, 12 files
> >
> > Why is there a orocos-ocl directory inside lib/orocos ?
>
> The UseOrocos.cmake macros install plugins and typekits in the
> 'lib/orocos/projectname/plugins' directory. OCL has as project name
> 'orocos- ocl'. We treat OCL as a special case and want to install it in
> lib/orocos...
>
> This was correctly done for the components, but not for the typekits and
> plugins.
>
> ROS-builds don't suffer from this because they don't install them.
>
> I'm on it.

I have pushed my master branches to gitorious. Both RTT and OCL were updated.

Every orocos_ macro now has an optional INSTALL argument that can override the
default. See the patch for OCL (and lua) for your reference.

Peter

[PATCH] change getComponentTypes to return string vector

---
deployment/DeploymentComponent.cpp | 6 +++---
deployment/DeploymentComponent.hpp | 2 +-
2 files changed, 4 insertions(+), 4 deletions(-)

diff --git a/deployment/DeploymentComponent.cpp b/deployment/DeploymentComponent.cpp
index 8fe87b0..29c6092 100644
--- a/deployment/DeploymentComponent.cpp
+++ b/deployment/DeploymentComponent.cpp
@@ -1335,12 +1335,12 @@ namespace OCL
cout << " (none)"<<endl;
}

- std::string DeploymentComponent::getComponentTypes() const
+ std::vector<std::string> DeploymentComponent::getComponentTypes() const
{
- std::string s;
+ std::vector<std::string> s;
OCL::FactoryMap::iterator it;
for(it = OCL::ComponentFactories::Instance().begin(); it != OCL::ComponentFactories::Instance().end(); ++it)
- s+=it->first + ';';
+ s.push_back(it->first);

return s;
}
diff --git a/deployment/DeploymentComponent.hpp b/deployment/DeploymentComponent.hpp
index 04cd1d7..82cc24f 100644
--- a/deployment/DeploymentComponent.hpp
+++ b/deployment/DeploymentComponent.hpp
@@ -356,7 +356,7 @@ namespace OCL
* can create in a comma separated list.
* @see loadComponent()
*/
- std::string getComponentTypes() const;
+ std::vector<std::string> getComponentTypes() const;

/**
* (Re-)set the activity of a component with a periodic activity.

Ruben Smits's picture

RTT/OCL code freeze

On Monday 06 December 2010 17:48:47 Peter Soetens wrote:
> I have updated the version numbers to 2.2.0 on gitorious. I'll now start
> preparing the release, update some docs etc. Note the message in the other
> thread where I moved the carray.hpp header from internal to types. Since
> there is a backwards compatibility header, there shouldn't be an issue
> here for existing users.
>
> I'm still waiting a fix from Markus on the OCL's getComponentTypes
> function. I might revert the earlier patch if I ain't getting anything.
>
> I've been working on two cheat-sheets: a general 'Orocos' one and an RTT
> specific one. You can find them on their temporary location here:
>
> http://people.mech.kuleuven.be/~psoetens/orocos/orocos_cheat_sheet.pdf
> http://people.mech.kuleuven.be/~psoetens/orocos/rtt_cheat_sheet.pdf
>
> The sources are in orocos-toolchain/rtt/doc . It's by no-one reviewed yet
> so your input is welcome.

These sheets are really helpfull!!!, some comment on the Development workflow,
in the build block, is the make install mandatory?

Is there a reason why the component figure in the orocos and rtt cheat sheet is
different?

Is there an orogen and autoproj cheat sheet available too?

Ruben

RTT/OCL code freeze

On Monday 06 December 2010 20:37:43 Ruben Smits wrote:
> On Monday 06 December 2010 17:48:47 Peter Soetens wrote:
> > I have updated the version numbers to 2.2.0 on gitorious. I'll now start
> > preparing the release, update some docs etc. Note the message in the
> > other thread where I moved the carray.hpp header from internal to types.
> > Since there is a backwards compatibility header, there shouldn't be an
> > issue here for existing users.
> >
> > I'm still waiting a fix from Markus on the OCL's getComponentTypes
> > function. I might revert the earlier patch if I ain't getting anything.
> >
> > I've been working on two cheat-sheets: a general 'Orocos' one and an RTT
> > specific one. You can find them on their temporary location here:
> >
> > http://people.mech.kuleuven.be/~psoetens/orocos/orocos_cheat_sheet.pdf
> > http://people.mech.kuleuven.be/~psoetens/orocos/rtt_cheat_sheet.pdf
> >
> > The sources are in orocos-toolchain/rtt/doc . It's by no-one reviewed yet
> > so your input is welcome.
>
> These sheets are really helpfull!!!, some comment on the Development
> workflow, in the build block, is the make install mandatory?

In principle it is, except when you're in a ros package tree. I was thinking
of having one especially for ROS+Orocos, which wouldn't have the 'make
install' part, but just a make or rosmake. If someone could help with that...

>
> Is there a reason why the component figure in the orocos and rtt cheat
> sheet is different?

I had more space left in the Orocos sheet :-)

>
> Is there an orogen and autoproj cheat sheet available too?

Orogen's has been posted by Sylvain before.

Peter

RTT/OCL code freeze

Cheat sheet will be for sure very usefull.
I have some difficulties to see the "Deployment script" section on the
rigth, some pictures cover the text

2010/12/6 Peter Soetens <peter [..] ...>

> I have updated the version numbers to 2.2.0 on gitorious. I'll now start
> preparing the release, update some docs etc. Note the message in the other
> thread where I moved the carray.hpp header from internal to types. Since
> there
> is a backwards compatibility header, there shouldn't be an issue here for
> existing users.
>
> I'm still waiting a fix from Markus on the OCL's getComponentTypes
> function. I
> might revert the earlier patch if I ain't getting anything.
>
> I've been working on two cheat-sheets: a general 'Orocos' one and an RTT
> specific one. You can find them on their temporary location here:
>
> http://people.mech.kuleuven.be/~psoetens/orocos/orocos_cheat_sheet.pdf<h...
> http://people.mech.kuleuven.be/~psoetens/orocos/rtt_cheat_sheet.pdf<http...
>
> The sources are in orocos-toolchain/rtt/doc . It's by no-one reviewed yet
> so
> your input is welcome.
>
> Peter
> --
> Orocos-Dev mailing list
> Orocos-Dev [..] ...
> http://lists.mech.kuleuven.be/mailman/listinfo/orocos-dev
>

RTT/OCL code freeze

On Monday 06 December 2010 18:18:38 Willy Lambert wrote:
> Cheat sheet will be for sure very usefull.
> I have some difficulties to see the "Deployment script" section on the
> rigth, some pictures cover the text

There seems to be an issue with the PDF exporter of inkscape. I'll see if I
can fix it.

Peter