RTT Lua status

Submitted by markus.klotzbuecher on Tue, 2011-05-10 06:32

Orocos-users

Dear All,

It has been fairly quiet from my side on the topic of rttlua,
nevertheless a lot of enhacements, fixes and syntactial improvements
have been flowing in:

- '.new' constructors are gone, create RTT types with
rtt.Variable('string') (btw: same with rFSM!)

- the confusing syntax (TaskContext:call('start')) for invoking
operations has gone, now just call tc:start() or
deployer:loadComponent("lua", "OCL::LuaComponent")

- fixed the type overriding issue

- No basic datasources are returned from port:read, property:get
etc., but instead automatically converted to Lua types. This solves
equality issue which causes equal RTT and Lua types not to be
equal.

- add rttlib.info() which prints available types, typekits,
components, etc.

- made all Component hooks optional.

- ...

Dokumentationwise, I have started moving everything in a "Cookbook
format" to the wiki (which some of you have discovered already):

http://www.orocos.org/wiki/orocos/toolchain/LuaCookbook

Next I will convert the existing API docs to the luadoc format which
generates much nicer html.

All in all we are getting closer to 1.0! The only larger item
remaining will be to add and test the hard-real time patches (TLSF
support, alloc tracing hooks etc.)

Thanks to everyone trying this and providing feedback!

Best regards
Markus

Re: RTT Lua status

Submitted by gstruyf on Fri, 2011-05-20 21:08.

markus.klotzbuecher wrote:

Dear All,

It has been fairly quiet from my side on the topic of rttlua, nevertheless a lot of enhacements, fixes and syntactial improvements have been flowing in:

 - '.new' constructors are gone, create RTT types with
   rtt.Variable('string') (btw: same with rFSM!)

 - the confusing syntax (TaskContext:call('start')) for invoking
   operations has gone, now just call tc:start() or
   deployer:loadComponent("lua", "OCL::LuaComponent")

 - fixed the type overriding issue

 - No basic datasources are returned from port:read, property:get
   etc., but instead automatically converted to Lua types. This solves
   equality issue which causes equal RTT and Lua types not to be
   equal.

 - add rttlib.info() which prints available types, typekits,
   components, etc.

 - made all Component hooks optional.

 - ...

Dokumentationwise, I have started moving everything in a "Cookbook format" to the wiki (which some of you have discovered already):

http://www.orocos.org/wiki/orocos/toolchain/LuaCookbook

Next I will convert the existing API docs to the luadoc format which generates much nicer html.

All in all we are getting closer to 1.0! The only larger item remaining will be to add and test the hard-real time patches (TLSF support, alloc tracing hooks etc.)

Thanks to everyone trying this and providing feedback!

Best regards Markus

I'm following your 'cookbook' on http://www.orocos.org/wiki/orocos/toolchain/orocostoolchainluacookbook but it seems that these latest updates haven't been included on the orocos_toolchain_ros repository I pulled from http://git.mech.kuleuven.be/robotics/orocos_toolchain_ros.git I'm currently on the diamondback branch, ocl v2.3.2.

in order to not work with outdated code, is it possible to merge git://gitorious.org/~markusk/orocos-toolchain/ocl-mk.git with my current install? and my main problem, how do I do this? (I'm not a great git expert..)

Or do I just have to wait untill the next orocos_toolchain_ros release?

thanks, Gunther

RTT Lua status

Submitted by markus.klotzbuecher on Sat, 2011-05-21 20:00.

Dear Gunther,

On Fri, May 20, 2011 at 11:08:39PM +0200, gunther [dot] struyf [..] ... wrote:
>
> [/quote]
> I'm following your 'cookbook' on http://www.orocos.org/wiki/orocos/toolchain/orocostoolchainluacookbook
> but it seems that these latest updates haven't been included on the orocos_toolchain_ros repository I pulled from http://git.mech.kuleuven.be/robotics/orocos_toolchain_ros.git
> I'm currently on the diamondback branch, ocl v2.3.2.

Right!

> in order to not work with outdated code, is it possible to merge
> git://gitorious.org/~markusk/orocos-toolchain/ocl-mk.git with my
> current install? and my main problem, how do I do this? (I'm not a
> great git expert..)

Yes, you could track that branch, but as I'm currently pushing all
fixes directly to OCL/master you can just switch both OCL and RTT to
master and recompile. Something like the following should work:

$ roscd rtt
$ git checkout master
$ git pull
$ roscd ocl
$ git checkout master
$ git pull
$ rosmake

> Or do I just have to wait untill the next orocos_toolchain_ros
> release?

That's an option too, if you have that time.

Best regards
Markus

RTT Lua status

Submitted by gstruyf on Sun, 2011-05-22 15:12.

Op 21/05/2011 21:57, Markus Klotzbuecher schreef:
> Dear Gunther,
>
> On Fri, May 20, 2011 at 11:08:39PM +0200, gunther [dot] struyf [..] ... wrote:
>> [/quote]
>> I'm following your 'cookbook' on http://www.orocos.org/wiki/orocos/toolchain/orocostoolchainluacookbook
>> but it seems that these latest updates haven't been included on the orocos_toolchain_ros repository I pulled from http://git.mech.kuleuven.be/robotics/orocos_toolchain_ros.git
>> I'm currently on the diamondback branch, ocl v2.3.2.
> Right!
>
>> in order to not work with outdated code, is it possible to merge
>> git://gitorious.org/~markusk/orocos-toolchain/ocl-mk.git with my
>> current install? and my main problem, how do I do this? (I'm not a
>> great git expert..)
> Yes, you could track that branch, but as I'm currently pushing all
> fixes directly to OCL/master you can just switch both OCL and RTT to
> master and recompile. Something like the following should work:
>
> $ roscd rtt
> $ git checkout master
> $ git pull
> $ roscd ocl
> $ git checkout master
> $ git pull
> $ rosmake
after a make clean and rosmake, this worked just fine for me. All new rttlua-stuff is available!
a small remark however: I now have two rttlua-gnulinux files:

[rosrun] You have chosen a non-unique executable, please pick one of the following:
1) /home/s0178923/orocos_toolchain_ros_db/ocl/bin/rttlua-gnulinux
2) /home/s0178923/orocos_toolchain_ros_db/ocl/install/bin/rttlua-gnulinux

but besides that, no problems

>
>> Or do I just have to wait untill the next orocos_toolchain_ros
>> release?
> That's an option too, if you have that time.
actually I hadn't :p

> Best regards
> Markus
so thanks a lot for your help!

RTT Lua status

Submitted by gstruyf on Tue, 2011-05-24 08:28.

Op 22/05/2011 17:10, Gunther Struyf schreef:
> Op 21/05/2011 21:57, Markus Klotzbuecher schreef:
>> Dear Gunther,
>>
>> On Fri, May 20, 2011 at 11:08:39PM +0200, gunther [dot] struyf [..] ... wrote:
>>> [/quote]
>>> I'm following your 'cookbook' on http://www.orocos.org/wiki/orocos/toolchain/orocostoolchainluacookbook
>>> but it seems that these latest updates haven't been included on the orocos_toolchain_ros repository I pulled from http://git.mech.kuleuven.be/robotics/orocos_toolchain_ros.git
>>> I'm currently on the diamondback branch, ocl v2.3.2.
>> Right!
>>
>>> in order to not work with outdated code, is it possible to merge
>>> git://gitorious.org/~markusk/orocos-toolchain/ocl-mk.git with my
>>> current install? and my main problem, how do I do this? (I'm not a
>>> great git expert..)
>> Yes, you could track that branch, but as I'm currently pushing all
>> fixes directly to OCL/master you can just switch both OCL and RTT to
>> master and recompile. Something like the following should work:
>>
>> $ roscd rtt
>> $ git checkout master
>> $ git pull
>> $ roscd ocl
>> $ git checkout master
>> $ git pull
>> $ rosmake
> after a make clean and rosmake, this worked just fine for me. All new rttlua-stuff is available!
> a small remark however: I now have two rttlua-gnulinux files:
>
> [rosrun] You have chosen a non-unique executable, please pick one of the following:
> 1) /home/s0178923/orocos_toolchain_ros_db/ocl/bin/rttlua-gnulinux
> 2) /home/s0178923/orocos_toolchain_ros_db/ocl/install/bin/rttlua-gnulinux
>
> but besides that, no problems
ignore that last remark, I forgot to recompile rtt_ros_integration, when doing so, a bunch of errors in rtt_ros_integration_std_msgs popped up (see attached log file), all with the same structure:

/home/s0178923/orocos_toolchain_ros_db/rtt_ros_integration/src/ros_msg_transporter.hpp: In instantiation of ‘ros_integration::RosMsgTransporter<std_msgs::UInt32_ /home/s0178923/orocos_toolchain_ros_db/rtt_ros_integration_std_msgs/src/orocos/types/ros_std_msgs_transport.cpp:48: instantiated from here
/home/s0178923/orocos_toolchain_ros_db/rtt_ros_integration/src/ros_msg_transporter.hpp:222: error: conflicting return type specified for ‘RTT::base::ChannelElementBase* ros_integration::RosMsgTransporter<T>::createStream(RTT::base::PortInterface*, const RTT::ConnPolicy&, bool) const [with T = std_msgs::UInt32_<std::allocator /home/s0178923/orocos_toolchain_ros_db/rtt/install/include/rtt/types/TypeTransporter.hpp:81: error: overriding ‘virtual boost::intrusive_ptr<RTT::base::ChannelElementBase> RTT::types::TypeTransporter::createStream(RTT::base::PortInterface*, const RTT::ConnPolicy&, bool) const’

is there a fix for this or should I head back to v2.3.2 ?

Thanks,
Gunther

RTT Lua status

Submitted by Ruben Smits on Tue, 2011-05-24 08:36.

On Sunday 22 May 2011 17:50:30 Gunther Struyf wrote:
> Op 22/05/2011 17:10, Gunther Struyf schreef:
> > Op 21/05/2011 21:57, Markus Klotzbuecher schreef:
> >> Dear Gunther,
> >>
> >> On Fri, May 20, 2011 at 11:08:39PM +0200,
gunther [dot] struyf [..] ... wrote:
> >>> [/quote]
> >>> I'm following your 'cookbook' on
> >>> http://www.orocos.org/wiki/orocos/toolchain/orocostoolchainluacookb
> >>> ook but it seems that these latest updates haven't been included on
> >>> the orocos_toolchain_ros repository I pulled from
> >>> http://git.mech.kuleuven.be/robotics/orocos_toolchain_ros.git I'm
> >>> currently on the diamondback branch, ocl v2.3.2.
> >>
> >> Right!
> >>
> >>> in order to not work with outdated code, is it possible to merge
> >>> git://gitorious.org/~markusk/orocos-toolchain/ocl-mk.git with my
> >>> current install? and my main problem, how do I do this? (I'm not a
> >>> great git expert..)
> >>
> >> Yes, you could track that branch, but as I'm currently pushing all
> >> fixes directly to OCL/master you can just switch both OCL and RTT to
> >> master and recompile. Something like the following should work:
> >>
> >> $ roscd rtt
> >> $ git checkout master
> >> $ git pull
> >> $ roscd ocl
> >> $ git checkout master
> >> $ git pull
> >> $ rosmake
> >
> > after a make clean and rosmake, this worked just fine for me. All new
> > rttlua-stuff is available! a small remark however: I now have two
> > rttlua-gnulinux files:
> >
> > [rosrun] You have chosen a non-unique executable, please pick one of the
> > following: 1)
> > /home/s0178923/orocos_toolchain_ros_db/ocl/bin/rttlua-gnulinux 2)
> > /home/s0178923/orocos_toolchain_ros_db/ocl/install/bin/rttlua-gnulinux
> >
> > but besides that, no problems
>
> ignore that last remark, I forgot to recompile rtt_ros_integration, when
> doing so, a bunch of errors in rtt_ros_integration_std_msgs popped up (see
> attached log file), all with the same structure:
>
> /home/s0178923/orocos_toolchain_ros_db/rtt_ros_integration/src/ros_msg_trans
> porter.hpp: In instantiation of
> â??ros_integration::RosMsgTransporter<std_msgs::UInt32_ > > >â??:
> /home/s0178923/orocos_toolchain_ros_db/rtt_ros_integration_std_msgs/src/oro
> cos/types/ros_std_msgs_transport.cpp:48: instantiated from here
> /home/s0178923/orocos_toolchain_ros_db/rtt_ros_integration/src/ros_msg_tran
> sporter.hpp:222: error: conflicting return type specified for
> â??RTT::base::ChannelElementBase*
> ros_integration::RosMsgTransporter<T>::createStream(RTT::base::PortInterfac
> e*, const RTT::ConnPolicy&, bool) const [with T =
> std_msgs::UInt32_<std::allocator > /home/s0178923/orocos_toolchain_ros_db/rtt/install/include/rtt/types/TypeTr
> ansporter.hpp:81: error: overriding â??virtual
> boost::intrusive_ptr<RTT::base::ChannelElementBase>
> RTT::types::TypeTransporter::createStream(RTT::base::PortInterface*, const
> RTT::ConnPolicy&, bool) constâ??
>
>
> is there a fix for this or should I head back to v2.3.2 ?

Yes, orocos toolchain rtt master and orocos_toolchain_ros master are
incompatible. orocos_toolchain_ros is only compatible with the toolchain-2.3
branch of orocos toolchain rtt.

If you really need rtt master you can apply the attached patch on
orocos_toolchain_ros.

> Thanks,
> Gunther

-- Ruben

RTT Lua status

Submitted by willy on Sun, 2011-05-22 16:40.

2011/5/22 Gunther Struyf <gunther [dot] struyf [..] ...>

> Op 21/05/2011 21:57, Markus Klotzbuecher schreef:
> > Dear Gunther,
> >
> > On Fri, May 20, 2011 at 11:08:39PM +0200,
> gunther [dot] struyf [..] ... wrote:
> >> [/quote]
> >> I'm following your 'cookbook' on
> http://www.orocos.org/wiki/orocos/toolchain/orocostoolchainluacookbook
> >> but it seems that these latest updates haven't been included on the
> orocos_toolchain_ros repository I pulled from
> http://git.mech.kuleuven.be/robotics/orocos_toolchain_ros.git
> >> I'm currently on the diamondback branch, ocl v2.3.2.
> > Right!
> >
> >> in order to not work with outdated code, is it possible to merge
> >> git://gitorious.org/~markusk/orocos-toolchain/ocl-mk.git<http://gitorious.org/%7Emarkusk/orocos-toolchain/ocl-mk.git>with my
> >> current install? and my main problem, how do I do this? (I'm not a
> >> great git expert..)
> > Yes, you could track that branch, but as I'm currently pushing all
> > fixes directly to OCL/master you can just switch both OCL and RTT to
> > master and recompile. Something like the following should work:
> >
> > $ roscd rtt
> > $ git checkout master
> > $ git pull
> > $ roscd ocl
> > $ git checkout master
> > $ git pull
> > $ rosmake
> after a make clean and rosmake, this worked just fine for me. All new
> rttlua-stuff is available!
> a small remark however: I now have two rttlua-gnulinux files:
>
> [rosrun] You have chosen a non-unique executable, please pick one of the
> following:
> 1) /home/s0178923/orocos_toolchain_ros_db/ocl/bin/rttlua-gnulinux
> 2) /home/s0178923/orocos_toolchain_ros_db/ocl/install/bin/rttlua-gnulinux
>

this is "normal" I suppose. I always had this with ros and orocos.

>
> but besides that, no problems
>
> >
> >> Or do I just have to wait untill the next orocos_toolchain_ros
> >> release?
> > That's an option too, if you have that time.
> actually I hadn't :p
>
> > Best regards
> > Markus
> so thanks a lot for your help!
>
> qs
>
> --
> Orocos-Users mailing list
> Orocos-Users [..] ...
> http://lists.mech.kuleuven.be/mailman/listinfo/orocos-users
>

RTT Lua status

Submitted by peter on Sun, 2011-05-22 22:32.

On Sunday 22 May 2011 18:38:43 Willy Lambert wrote:
> 2011/5/22 Gunther Struyf <gunther [dot] struyf [..] ...>
>
> > Op 21/05/2011 21:57, Markus Klotzbuecher schreef:
> > > Dear Gunther,
> > >
> > > On Fri, May 20, 2011 at 11:08:39PM +0200,
> >
> > gunther [dot] struyf [..] ... wrote:
> > >> [/quote]
> > >> I'm following your 'cookbook' on
> >
> > http://www.orocos.org/wiki/orocos/toolchain/orocostoolchainluacookbook
> >
> > >> but it seems that these latest updates haven't been included on the
> >
> > orocos_toolchain_ros repository I pulled from
> > http://git.mech.kuleuven.be/robotics/orocos_toolchain_ros.git
> >
> > >> I'm currently on the diamondback branch, ocl v2.3.2.
> > >
> > > Right!
> > >
> > >> in order to not work with outdated code, is it possible to merge
> > >> git://gitorious.org/~markusk/orocos-toolchain/ocl-mk.git<http://gitori
> > >> ous.org/%7Emarkusk/orocos-toolchain/ocl-mk.git>with my current
> > >> install? and my main problem, how do I do this? (I'm not a great git
> > >> expert..)
> > >
> > > Yes, you could track that branch, but as I'm currently pushing all
> > > fixes directly to OCL/master you can just switch both OCL and RTT to
> > > master and recompile. Something like the following should work:
> > >
> > > $ roscd rtt
> > > $ git checkout master
> > > $ git pull
> > > $ roscd ocl
> > > $ git checkout master
> > > $ git pull
> > > $ rosmake
> >
> > after a make clean and rosmake, this worked just fine for me. All new
> > rttlua-stuff is available!
> > a small remark however: I now have two rttlua-gnulinux files:
> >
> > [rosrun] You have chosen a non-unique executable, please pick one of the
> > following:
> > 1) /home/s0178923/orocos_toolchain_ros_db/ocl/bin/rttlua-gnulinux
> > 2) /home/s0178923/orocos_toolchain_ros_db/ocl/install/bin/rttlua-gnulinux
>
> this is "normal" I suppose. I always had this with ros and orocos.

It has been fixed on the toolchain-2.3 and master branches for a while. You
should clean your ocl directory with

git clean -xdf

Such that the old executable file is removed, and then recompile OCL with
make/rosmake.

Peter

RTT Lua status

Submitted by markus.klotzbuecher on Sun, 2011-05-22 19:12.

On Sun, May 22, 2011 at 05:50:30PM +0200, Gunther Struyf wrote:
> Op 22/05/2011 17:10, Gunther Struyf schreef:
> > Op 21/05/2011 21:57, Markus Klotzbuecher schreef:
> >> Dear Gunther,
> >>
> >> On Fri, May 20, 2011 at 11:08:39PM +0200, gunther [dot] struyf [..] ... wrote:
> >>> [/quote]
> >>> I'm following your 'cookbook' on http://www.orocos.org/wiki/orocos/toolchain/orocostoolchainluacookbook
> >>> but it seems that these latest updates haven't been included on the orocos_toolchain_ros repository I pulled from http://git.mech.kuleuven.be/robotics/orocos_toolchain_ros.git
> >>> I'm currently on the diamondback branch, ocl v2.3.2.
> >> Right!
> >>
> >>> in order to not work with outdated code, is it possible to merge
> >>> git://gitorious.org/~markusk/orocos-toolchain/ocl-mk.git with my
> >>> current install? and my main problem, how do I do this? (I'm not a
> >>> great git expert..)
> >> Yes, you could track that branch, but as I'm currently pushing all
> >> fixes directly to OCL/master you can just switch both OCL and RTT to
> >> master and recompile. Something like the following should work:
> >>
> >> $ roscd rtt
> >> $ git checkout master
> >> $ git pull
> >> $ roscd ocl
> >> $ git checkout master
> >> $ git pull
> >> $ rosmake
> > after a make clean and rosmake, this worked just fine for me. All new rttlua-stuff is available!
> > a small remark however: I now have two rttlua-gnulinux files:
> >
> > [rosrun] You have chosen a non-unique executable, please pick one of the following:
> > 1) /home/s0178923/orocos_toolchain_ros_db/ocl/bin/rttlua-gnulinux
> > 2) /home/s0178923/orocos_toolchain_ros_db/ocl/install/bin/rttlua-gnulinux
> >
> > but besides that, no problems
> ignore that last remark, I forgot to recompile rtt_ros_integration, when doing so, a bunch of errors in rtt_ros_integration_std_msgs popped up (see attached log file), all with the same structure:
>
> /home/s0178923/orocos_toolchain_ros_db/rtt_ros_integration/src/ros_msg_transporter.hpp: In instantiation of ‘ros_integration::RosMsgTransporter<std_msgs::UInt32_ > /home/s0178923/orocos_toolchain_ros_db/rtt_ros_integration_std_msgs/src/orocos/types/ros_std_msgs_transport.cpp:48: instantiated from here
> /home/s0178923/orocos_toolchain_ros_db/rtt_ros_integration/src/ros_msg_transporter.hpp:222: error: conflicting return type specified for ‘RTT::base::ChannelElementBase* ros_integration::RosMsgTransporter<T>::createStream(RTT::base::PortInterface*, const RTT::ConnPolicy&, bool) const [with T = std_msgs::UInt32_<std::allocator > /home/s0178923/orocos_toolchain_ros_db/rtt/install/include/rtt/types/TypeTransporter.hpp:81: error: overriding ‘virtual boost::intrusive_ptr<RTT::base::ChannelElementBase> RTT::types::TypeTransporter::createStream(RTT::base::PortInterface*, const RTT::ConnPolicy&, bool) const’
>
>
> is there a fix for this or should I head back to v2.3.2 ?

I don't know what the exact problem is, but for RTT and OCL master I
would checkout orocos_toolchain_ros master too:

roscd orocos_toolchain_ros/
git checkout master
git pull

and rebuild.

Does this fix the problem?

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

RTT Lua status

Submitted by peter on Tue, 2011-05-24 08:33.

On Sunday 22 May 2011 21:10:41 Markus Klotzbuecher wrote:
> On Sun, May 22, 2011 at 05:50:30PM +0200, Gunther Struyf wrote:
> > Op 22/05/2011 17:10, Gunther Struyf schreef:
> > > Op 21/05/2011 21:57, Markus Klotzbuecher schreef:
> > >> Dear Gunther,
> > >>
> > >> On Fri, May 20, 2011 at 11:08:39PM +0200,
gunther [dot] struyf [..] ... wrote:
> > >>> [/quote]
> > >>> I'm following your 'cookbook' on
> > >>> http://www.orocos.org/wiki/orocos/toolchain/orocostoolchainluacookbo
> > >>> ok but it seems that these latest updates haven't been included on
> > >>> the orocos_toolchain_ros repository I pulled from
> > >>> http://git.mech.kuleuven.be/robotics/orocos_toolchain_ros.git I'm
> > >>> currently on the diamondback branch, ocl v2.3.2.
> > >>
> > >> Right!
> > >>
> > >>> in order to not work with outdated code, is it possible to merge
> > >>> git://gitorious.org/~markusk/orocos-toolchain/ocl-mk.git with my
> > >>> current install? and my main problem, how do I do this? (I'm not a
> > >>> great git expert..)
> > >>
> > >> Yes, you could track that branch, but as I'm currently pushing all
> > >> fixes directly to OCL/master you can just switch both OCL and RTT to
> > >> master and recompile. Something like the following should work:
> > >>
> > >> $ roscd rtt
> > >> $ git checkout master
> > >> $ git pull
> > >> $ roscd ocl
> > >> $ git checkout master
> > >> $ git pull
> > >> $ rosmake
> > >
> > > after a make clean and rosmake, this worked just fine for me. All new
> > > rttlua-stuff is available! a small remark however: I now have two
> > > rttlua-gnulinux files:
> > >
> > > [rosrun] You have chosen a non-unique executable, please pick one of
> > > the following: 1)
> > > /home/s0178923/orocos_toolchain_ros_db/ocl/bin/rttlua-gnulinux 2)
> > > /home/s0178923/orocos_toolchain_ros_db/ocl/install/bin/rttlua-gnulinux
> > >
> > > but besides that, no problems
> >
> > ignore that last remark, I forgot to recompile rtt_ros_integration, when
> > doing so, a bunch of errors in rtt_ros_integration_std_msgs popped up
> > (see attached log file), all with the same structure:
> >
> > /home/s0178923/orocos_toolchain_ros_db/rtt_ros_integration/src/ros_msg_tr
> > ansporter.hpp: In instantiation of
> > ‘ros_integration::RosMsgTransporter<std_msgs::UInt32_ > > d> > >’:
> > /home/s0178923/orocos_toolchain_ros_db/rtt_ros_integration_std_msgs/src/
> > orocos/types/ros_std_msgs_transport.cpp:48: instantiated from here
> > /home/s0178923/orocos_toolchain_ros_db/rtt_ros_integration/src/ros_msg_t
> > ransporter.hpp:222: error: conflicting return type specified for
> > ‘RTT::base::ChannelElementBase*
> > ros_integration::RosMsgTransporter<T>::createStream(RTT::base::PortInter
> > face*, const RTT::ConnPolicy&, bool) const [with T =
> > std_msgs::UInt32_<std::allocator > > /home/s0178923/orocos_toolchain_ros_db/rtt/install/include/rtt/types/Typ
> > eTransporter.hpp:81: error: overriding ‘virtual
> > boost::intrusive_ptr<RTT::base::ChannelElementBase>
> > RTT::types::TypeTransporter::createStream(RTT::base::PortInterface*,
> > const RTT::ConnPolicy&, bool) const’
> >
> >
> > is there a fix for this or should I head back to v2.3.2 ?

This error is caused by an old RTT and a new OCL version. You need to checkout
master of RTT too.

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

RTT Lua status

Submitted by gstruyf on Mon, 2011-05-23 20:56.

On 22-05-11 21:10, Markus Klotzbuecher wrote:
> On Sun, May 22, 2011 at 05:50:30PM +0200, Gunther Struyf wrote:
>> Op 22/05/2011 17:10, Gunther Struyf schreef:
>>> Op 21/05/2011 21:57, Markus Klotzbuecher schreef:
>>>> Dear Gunther,
>>>>
>>>> On Fri, May 20, 2011 at 11:08:39PM +0200, gunther [dot] struyf [..] ... wrote:
>>>>> [/quote]
>>>>> I'm following your 'cookbook' on http://www.orocos.org/wiki/orocos/toolchain/orocostoolchainluacookbook
>>>>> but it seems that these latest updates haven't been included on the orocos_toolchain_ros repository I pulled from http://git.mech.kuleuven.be/robotics/orocos_toolchain_ros.git
>>>>> I'm currently on the diamondback branch, ocl v2.3.2.
>>>> Right!
>>>>
>>>>> in order to not work with outdated code, is it possible to merge
>>>>> git://gitorious.org/~markusk/orocos-toolchain/ocl-mk.git with my
>>>>> current install? and my main problem, how do I do this? (I'm not a
>>>>> great git expert..)
>>>> Yes, you could track that branch, but as I'm currently pushing all
>>>> fixes directly to OCL/master you can just switch both OCL and RTT to
>>>> master and recompile. Something like the following should work:
>>>>
>>>> $ roscd rtt
>>>> $ git checkout master
>>>> $ git pull
>>>> $ roscd ocl
>>>> $ git checkout master
>>>> $ git pull
>>>> $ rosmake
>>> after a make clean and rosmake, this worked just fine for me. All new rttlua-stuff is available!
>>> a small remark however: I now have two rttlua-gnulinux files:
>>>
>>> [rosrun] You have chosen a non-unique executable, please pick one of the following:
>>> 1) /home/s0178923/orocos_toolchain_ros_db/ocl/bin/rttlua-gnulinux
>>> 2) /home/s0178923/orocos_toolchain_ros_db/ocl/install/bin/rttlua-gnulinux
>>>
>>> but besides that, no problems
>> ignore that last remark, I forgot to recompile rtt_ros_integration, when doing so, a bunch of errors in rtt_ros_integration_std_msgs popped up (see attached log file), all with the same structure:
>>
>> /home/s0178923/orocos_toolchain_ros_db/rtt_ros_integration/src/ros_msg_transporter.hpp: In instantiation of ‘ros_integration::RosMsgTransporter<std_msgs::UInt32_ >> /home/s0178923/orocos_toolchain_ros_db/rtt_ros_integration_std_msgs/src/orocos/types/ros_std_msgs_transport.cpp:48: instantiated from here
>> /home/s0178923/orocos_toolchain_ros_db/rtt_ros_integration/src/ros_msg_transporter.hpp:222: error: conflicting return type specified for ‘RTT::base::ChannelElementBase* ros_integration::RosMsgTransporter<T>::createStream(RTT::base::PortInterface*, const RTT::ConnPolicy&, bool) const [with T = std_msgs::UInt32_<std::allocator >> /home/s0178923/orocos_toolchain_ros_db/rtt/install/include/rtt/types/TypeTransporter.hpp:81: error: overriding ‘virtual boost::intrusive_ptr<RTT::base::ChannelElementBase> RTT::types::TypeTransporter::createStream(RTT::base::PortInterface*, const RTT::ConnPolicy&, bool) const’
>>
>>
>> is there a fix for this or should I head back to v2.3.2 ?
> I don't know what the exact problem is, but for RTT and OCL master I
> would checkout orocos_toolchain_ros master too:
>
> roscd orocos_toolchain_ros/
> git checkout master
> git pull
>
> and rebuild.
>
> Does this fix the problem?
>
> Best regards
> MArkus
no, the error persists, for the moment I'll stick to rttlua 1.0-beta2

Gunther

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

RTT Lua status

Submitted by gstruyf on Mon, 2011-05-23 18:12.

Gunther

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

RTT Lua status, here are the new API docs

Submitted by markus.klotzbuecher on Fri, 2011-05-13 08:08.

On Tue, May 10, 2011 at 08:28:49AM +0200, Markus Klotzbuecher wrote:
> Dear All,
>
> It has been fairly quiet from my side on the topic of rttlua,
> nevertheless a lot of enhacements, fixes and syntactial improvements
> have been flowing in:
>
> - '.new' constructors are gone, create RTT types with
> rtt.Variable('string') (btw: same with rFSM!)
>
> - the confusing syntax (TaskContext:call('start')) for invoking
> operations has gone, now just call tc:start() or
> deployer:loadComponent("lua", "OCL::LuaComponent")
>
> - fixed the type overriding issue
>
> - No basic datasources are returned from port:read, property:get
> etc., but instead automatically converted to Lua types. This solves
> equality issue which causes equal RTT and Lua types not to be
> equal.
>
> - add rttlib.info() which prints available types, typekits,
> components, etc.
>
> - made all Component hooks optional.
>
> - ...
>
> Dokumentationwise, I have started moving everything in a "Cookbook
> format" to the wiki (which some of you have discovered already):
>
> http://www.orocos.org/wiki/orocos/toolchain/LuaCookbook
>
> Next I will convert the existing API docs to the luadoc format which
> generates much nicer html.

And here they are (thanks to Peter!):

http://people.mech.kuleuven.be/~orocos/pub/devel/documentation/ocl/maste...

> All in all we are getting closer to 1.0! The only larger item
> remaining will be to add and test the hard-real time patches (TLSF
> support, alloc tracing hooks etc.)
>
> Thanks to everyone trying this and providing feedback!

Best regards
Markus