[prev in list] [next in list] [prev in thread] [next in thread] 

List:       orocos-users
Subject:    [Orocos-users] Cannot compile component
From:       peter () thesourceworks ! com (Peter Soetens)
Date:       2012-11-30 21:41:20
Message-ID: CAMYDobXO5s-nhkwtooZCx0KH9k2q+xbGUqt05UMBkPiJ0sO1eQ () mail ! gmail ! com
[Download RAW message or body]

On Fri, Nov 30, 2012 at 7:26 PM, Peter Soetens <peter at thesourceworks.com> wrote:
> On Fri, Nov 30, 2012 at 12:55 PM,  <mirko.kunze at web.de> wrote:
> > I have tracked the problem a little further:
> > 
> > It seems to be caused by the second argument
> > 
> > KDL::Frame & targetmatrix
> > 
> > If I remove that (both in definition and declaration of course), it compiles
> > fine.
> > 
> > Also, if I replace it with "KDL::Frame targetmatrix" or even "KDL::Frame *
> > targetmatrix", it compiles.
> > "KDL::Vector & targetmatrix" also causes the problem.
> 
> http://www.orocos.org/forum/orocos/orocos-users/cannot-compile-component
> 
> Thanks for reporting, there must be a bug in the operations code for
> this combination of arguments (one return value + 3 argument
> references). We certainly can fix this, but a bug report would also
> help for keeping track of this ( bugs.orocos.org ).
> 
> Regarding your example code, you don't need to encode the C++ type in
> the arg(...) function, RTT derives the argument type automatically, so
> just your variable name will do.

Some functions were missing for > 3 return arguments. I have attached
the patch and pushed the fix to toolchain-2.5

Peter
-------------- next part --------------
A non-text attachment was scrubbed...
Name: 0001-operations-support-collecting-arguments-up-to-6.patch
Type: application/octet-stream
Size: 7829 bytes
Desc: not available
Url : http://lists.mech.kuleuven.be/pipermail/orocos-users/attachments/20121130/c69c7ac6/attachment-0001.obj \



[prev in list] [next in list] [prev in thread] [next in thread]