Orocos Toolchain v2.1.0 Released

One month has passed since our historical 2.0.0 release, so it was about time to release the more-than-minor fixes and extensions of the v2.x line. Here is the Orocos Toolchain v2.1.0, helping us better than ever to build all sorts of robots and machines.

You can find all the info at the usual places, starting from the http://www.orocos.org/toolchain page, but here's the juicy stuff summarized:

  • Important fixes in the corba transport layer - memory management and bugfixes
  • Improved TaskBrowser - layout, help, ';' matlab-like syntax
  • Improved Deployer - new corbaComponent operation and better library loading
  • Improved user data type support - displaying and manipulating data in the

TaskBrowser and scripts

  • Improved win32 support - port of the 1.12.0 release fixes
  • New application building CMake macros - See the installation manual

And a bunch of overall bugfixes that were first tested on the 2.0.x branch. The documentation was also improved and updated. See the RTT 2.1 Changes document for a more extensive summary.

We will continue to focus on improving the tools around the RTT in the coming months in order to help you build, monitor and interact with applications.

You can choose to automate the installation using the bootstrap script, which will fetch the 2.1 branch for you, or download a zip/tar ball package:

A special thank you for all those brave souls that tested and improved the 2.0.x releases. You all make the Orocos Toolchain shine.

Peter

Orocos Toolchain v2.1.0 Released

I failed updating my Orocos.

I did :
autoproj update
autoproj build
And everything run without errors.

But my [autorpoj_path]/rrt/CMakeLists.txt chows a "2.0.2" version.

I did try to re-download booststrap.sh (because it's not clear for me if
it's done with the autoproj update or not), re-run bootstrap.sh, and update
and build, but nothing changed.
I would appreciate that autoproj tells something about versions (I don't
know wether it's possible or not), because it would definitely help knowing
if we build the rigth toolchain

by the way, do the autoproj update erase my CMakeCache files ?

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

> One month has passed since our historical 2.0.0 release, so it was about
> time
> to release the more-than-minor fixes and extensions of the v2.x line. Here
> is
> the Orocos Toolchain v2.1.0, helping us better than ever to build all sorts
> of
> robots and machines.
>
> You can find all the info at the usual places, starting from the
> http://www.orocos.org/toolchain page, but here's the juicy stuff
> summarized:
>
> * Important fixes in the corba transport layer - memory management and
> bugfixes
> * Improved TaskBrowser - layout, help, ';' matlab-like syntax
> * Improved Deployer - new corbaComponent operation and better library
> loading
> * Improved user data type support - displaying and manipulating data in the
> TaskBrowser and scripts
> * Improved win32 support - port of the 1.12.0 release fixes
> * New application building CMake macros - See the installation manual
>
> And a bunch of overall bugfixes that were first tested on the 2.0.x branch.
> The
> documentation was also improved and updated. See the
> <http://www.orocos.org/stable/documentation/rtt/v2.1.x/doc-xml/orocos-rtt-
> changes.html<http://www.orocos.org/stable/documentation/rtt/v2.1.x/doc-xml/orocos-rtt-%0Achanges.html>>
> document for a more extensive summary.
>
> We will continue to focus on improving the tools around the RTT in the
> coming
> months in order to help you build, monitor and interact with applications.
>
> You can choose to automate the installation using the bootstrap script,
> which
> will fetch the 2.1 branch for you, or download a zip/tar ball package:
>
> * bootstrap: http://www.orocos.org/wiki/orocos/toolchain/quick-start
> * zip/tar: http://www.orocos.org/stable/toolchain/v2.1.0
>
> A special thank you for all those brave souls that tested and improved the
> 2.0.x releases. You all make the Orocos Toolchain shine.
>
> Peter
> --
> Orocos-Users mailing list
> Orocos-Users [..] ...
> http://lists.mech.kuleuven.be/mailman/listinfo/orocos-users
>

Orocos Toolchain v2.1.0 Released

On Wednesday 13 October 2010 09:38:11 Willy Lambert wrote:
> I failed updating my Orocos.
>
> I did :
> autoproj update
> autoproj build
> And everything run without errors.
>
> But my [autorpoj_path]/rrt/CMakeLists.txt chows a "2.0.2" version.

It does not upgrade you accross major releases. You need to re-bootstrap with
the new bootstrap.sh script in a fresh directory OR run these two commands:

autoproj switch-config git git://gitorious.com/orocos-toolchain/build.git \
branch=toolchain-2.1
autoproj update

then

autoproj build
as usual.

>
> I did try to re-download booststrap.sh (because it's not clear for me if
> it's done with the autoproj update or not), re-run bootstrap.sh, and update
> and build, but nothing changed.

Did you do this in a fresh directory ? There was a bug in the bootstrapping
process which prevented succesful completion which I just fixed.

> I would appreciate that autoproj tells something about versions (I don't
> know wether it's possible or not), because it would definitely help knowing
> if we build the rigth toolchain

autoproj has been told to checkout 'branches'. It knows about these branch
names, but indeed it does not display them. You can manually inspect
rtt/CMakeLists.txt though.

>
> by the way, do the autoproj update erase my CMakeCache files ?

I never saw this happening here.

I'll provide these upgrading instructions on the wiki.

Peter

Orocos Toolchain v2.1.0 Released

On 10/13/2010 11:06 AM, Peter Soetens wrote:
> On Wednesday 13 October 2010 09:38:11 Willy Lambert wrote:
>> I failed updating my Orocos.
>>
>> I did :
>> autoproj update
>> autoproj build
>> And everything run without errors.
>>
>> But my [autorpoj_path]/rrt/CMakeLists.txt chows a "2.0.2" version.
>
> It does not upgrade you accross major releases. You need to re-bootstrap with
> the new bootstrap.sh script in a fresh directory OR run these two commands:
>
> autoproj switch-config git git://gitorious.com/orocos-toolchain/build.git \
> branch=toolchain-2.1
> autoproj update

Yuk. Could we have a 'latest' branch that follows always the latest
version ?

>> by the way, do the autoproj update erase my CMakeCache files ?
Yes, it does. The problem is that CMake has a tendency to cache way too
much information and that is the best way to ensure smooth long time
upgrades.

What kind of issue did that cause for you ?

Orocos Toolchain v2.1.0 Released

On Mon, Oct 18, 2010 at 4:53 PM, Peter Soetens <peter [..] ...>wrote:

> On Wednesday 13 October 2010 15:27:24 Sylvain Joyeux wrote:
> > On 10/13/2010 11:06 AM, Peter Soetens wrote:
> > > On Wednesday 13 October 2010 09:38:11 Willy Lambert wrote:
> > >> I failed updating my Orocos.
> > >>
> > >> I did :
> > >> autoproj update
> > >> autoproj build
> > >> And everything run without errors.
> > >>
> > >> But my [autorpoj_path]/rrt/CMakeLists.txt chows a "2.0.2" version.
> > >
> > > It does not upgrade you accross major releases. You need to
> re-bootstrap
> > > with the new bootstrap.sh script in a fresh directory OR run these two
> > > commands:
> > >
> > > autoproj switch-config git git://
> gitorious.com/orocos-toolchain/build.git
> > > \ branch=toolchain-2.1
> > > autoproj update
> >
> > Yuk. Could we have a 'latest' branch that follows always the latest
> > version ?
>
> Sounds ok to me. So
> master = stable mainline (merges new features before a release is made),
> latest = latest stable release (tracks latest toolchain-2.x)
>

IMO a stable release should have stable in its name, probably nothing else.
Latest sounds closer to trunk than to stable. A similar discussion appeared
on the ROS list in recent months with respect to the "latest" tag. In the
end they dropped it because it was creating confusion.

http://code.ros.org/lurker/message/20100802.184003.33b953fd.ca.html

Adolfo

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

Orocos Toolchain v2.1.0 Released

On 10/20/2010 10:39 AM, Adolfo Rodríguez Tsouroukdissian wrote:
>
>
> On Mon, Oct 18, 2010 at 4:53 PM, Peter Soetens
> <peter [..] ... <mailto:peter [..] ...>> wrote:
>
> On Wednesday 13 October 2010 15:27:24 Sylvain Joyeux wrote:
> > On 10/13/2010 11:06 AM, Peter Soetens wrote:
> > > On Wednesday 13 October 2010 09:38:11 Willy Lambert wrote:
> > >> I failed updating my Orocos.
> > >>
> > >> I did :
> > >> autoproj update
> > >> autoproj build
> > >> And everything run without errors.
> > >>
> > >> But my [autorpoj_path]/rrt/CMakeLists.txt chows a "2.0.2"
> version.
> > >
> > > It does not upgrade you accross major releases. You need to
> re-bootstrap
> > > with the new bootstrap.sh script in a fresh directory OR run
> these two
> > > commands:
> > >
> > > autoproj switch-config git
> git://gitorious.com/orocos-toolchain/build.git
> <http://gitorious.com/orocos-toolchain/build.git>
> > > \ branch=toolchain-2.1
> > > autoproj update
> >
> > Yuk. Could we have a 'latest' branch that follows always the latest
> > version ?
>
> Sounds ok to me. So
> master = stable mainline (merges new features before a release is
> made),
> latest = latest stable release (tracks latest toolchain-2.x)
>
>
> IMO a stable release should have stable in its name, probably nothing
> else. Latest sounds closer to trunk than to stable. A similar
> discussion appeared on the ROS list in recent months with respect to
> the "latest" tag. In the end they dropped it because it was creating
> confusion.
>
> http://code.ros.org/lurker/message/20100802.184003.33b953fd.ca.html
Then I guess we should call the branch "stable" ;-)

Sylvain

Orocos Toolchain v2.1.0 Released

On Oct 20, 2010, at 04:42 , Sylvain Joyeux wrote:

> On 10/20/2010 10:39 AM, Adolfo Rodríguez Tsouroukdissian wrote:
>>
>>
>>
>> On Mon, Oct 18, 2010 at 4:53 PM, Peter Soetens <peter [..] ...> wrote:
>> On Wednesday 13 October 2010 15:27:24 Sylvain Joyeux wrote:
>> > On 10/13/2010 11:06 AM, Peter Soetens wrote:
>> > > On Wednesday 13 October 2010 09:38:11 Willy Lambert wrote:
>> > >> I failed updating my Orocos.
>> > >>
>> > >> I did :
>> > >> autoproj update
>> > >> autoproj build
>> > >> And everything run without errors.
>> > >>
>> > >> But my [autorpoj_path]/rrt/CMakeLists.txt chows a "2.0.2" version.
>> > >
>> > > It does not upgrade you accross major releases. You need to re-bootstrap
>> > > with the new bootstrap.sh script in a fresh directory OR run these two
>> > > commands:
>> > >
>> > > autoproj switch-config git git://gitorious.com/orocos-toolchain/build.git
>> > > \ branch=toolchain-2.1
>> > > autoproj update
>> >
>> > Yuk. Could we have a 'latest' branch that follows always the latest
>> > version ?
>>
>> Sounds ok to me. So
>> master = stable mainline (merges new features before a release is made),
>> latest = latest stable release (tracks latest toolchain-2.x)
>>
>> IMO a stable release should have stable in its name, probably nothing else. Latest sounds closer to trunk than to stable. A similar discussion appeared on the ROS list in recent months with respect to the "latest" tag. In the end they dropped it because it was creating confusion.
>>
>> http://code.ros.org/lurker/message/20100802.184003.33b953fd.ca.html
> Then I guess we should call the branch "stable" ;-)

+1 on the latest confusion.

So we have

toolchain-2.x for tracking v2 releases
master is the "stable" mainline with most recent features merged
stable follows the latest toolchain-2.x released?

Does v1 have a place in this list? For those of us stuck with it until 2011 ...
S

Orocos Toolchain v2.1.0 Released

On Wed, Oct 20, 2010 at 1:15 PM, S Roderick <kiwi [dot] net [..] ...> wrote:
> On Oct 20, 2010, at 04:42 , Sylvain Joyeux wrote:
>
> On 10/20/2010 10:39 AM, Adolfo Rodríguez Tsouroukdissian wrote:
>
> On Mon, Oct 18, 2010 at 4:53 PM, Peter Soetens <peter [..] ...>
> wrote:
>>
>> On Wednesday 13 October 2010 15:27:24 Sylvain Joyeux wrote:
>> > On 10/13/2010 11:06 AM, Peter Soetens wrote:
>> > > On Wednesday 13 October 2010 09:38:11 Willy Lambert wrote:
>> > >> I failed updating my Orocos.
>> > >>
>> > >> I did :
>> > >> autoproj update
>> > >> autoproj build
>> > >> And everything run without errors.
>> > >>
>> > >> But my [autorpoj_path]/rrt/CMakeLists.txt chows a "2.0.2" version.
>> > >
>> > > It does not upgrade you accross major releases. You need to
>> > > re-bootstrap
>> > > with the new bootstrap.sh script in a fresh directory OR run these two
>> > > commands:
>> > >
>> > > autoproj switch-config git
>> > > git://gitorious.com/orocos-toolchain/build.git
>> > > \ branch=toolchain-2.1
>> > > autoproj update
>> >
>> > Yuk. Could we have a 'latest' branch that follows always the latest
>> > version ?
>>
>> Sounds ok to me. So
>> master = stable mainline  (merges new features before a release is made),
>> latest =  latest stable release (tracks latest toolchain-2.x)
>
> IMO a stable release should have stable in its name, probably nothing else.
> Latest sounds closer to trunk than to stable. A similar discussion appeared
> on the ROS list in recent months with respect to the "latest" tag. In the
> end they dropped it because it was creating confusion.
>
> http://code.ros.org/lurker/message/20100802.184003.33b953fd.ca.html
>
> Then I guess we should call the branch "stable" ;-)
>
> +1 on the latest confusion.
> So we have
> toolchain-2.x for tracking v2 releases
> master is the "stable" mainline with most recent features merged
> stable follows the latest toolchain-2.x released?

Ack.

> Does v1 have a place in this list? For those of us stuck with it until 2011

I am only maintaining v1 on SVN branches/trunk. The only thing you got
is rtt-1.0-svn-patches which is a git mirror of the svn trunk. I can rename that
to rtt-1.x-trunk or so...

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

Orocos Toolchain v2.1.0 Released

2010/10/13 Sylvain Joyeux <sylvain [dot] joyeux [..] ...>

> On 10/13/2010 11:06 AM, Peter Soetens wrote:
>
>> On Wednesday 13 October 2010 09:38:11 Willy Lambert wrote:
>>
>>> I failed updating my Orocos.
>>>
>>> I did :
>>> autoproj update
>>> autoproj build
>>> And everything run without errors.
>>>
>>> But my [autorpoj_path]/rrt/CMakeLists.txt chows a "2.0.2" version.
>>>
>>
>> It does not upgrade you accross major releases. You need to re-bootstrap
>> with
>> the new bootstrap.sh script in a fresh directory OR run these two
>> commands:
>>
>> autoproj switch-config git git://gitorious.com/orocos-toolchain/build.git\
>> branch=toolchain-2.1
>> autoproj update
>>
>
> Yuk. Could we have a 'latest' branch that follows always the latest version
> ?
>
>
> by the way, do the autoproj update erase my CMakeCache files ?
>>>
>> Yes, it does. The problem is that CMake has a tendency to cache way too
> much information and that is the best way to ensure smooth long time
> upgrades.
>
> What kind of issue did that cause for you ?
>

nothing hurtfull, but i activated logging in ocl and changed rtt option in
order to use "real time logging" (as mentionned in the wiki); so the only
impact is that it broke my hudson builds ;)

maybe i should mention this variables in my cmake scripts, but as my orocos
integration in cmake is not perfect currently i used to modify cmake cache

> --
> Sylvain Joyeux (Dr. Ing.)
> Researcher - Space and Security Robotics
> DFKI Robotics Innovation Center
> Bremen, Robert-Hooke-Straße 5, 28359 Bremen, Germany
>
> Phone: +49 421 218-64136
> Fax: +49 421 218-64150
> Email: sylvain [dot] joyeux [..] ...
>
> Weitere Informationen: http://www.dfki.de
>

Orocos Toolchain v2.1.0 Released

You can also add/override CMake options in autoproj itself -- if you
don't want to modify the RTT/OCL tree.

Edit autoproj/overrides.rb and add

rtt = Autobuild::Package['rtt']
rtt.define "VAR", "VALUE"
rtt.define "VAR", "VALUE"
rtt.define "VAR", "VALUE"
rtt.define "VAR", "VALUE"

ocl = Autobuild::Package['ocl']
ocl.define "VAR", "VALUE"
ocl.define "VAR", "VALUE"
ocl.define "VAR", "VALUE"
ocl.define "VAR", "VALUE"

Orocos Toolchain v2.1.0 Released

2010/10/13 Sylvain Joyeux <sylvain [dot] joyeux [..] ...>

> You can also add/override CMake options in autoproj itself -- if you don't
> want to modify the RTT/OCL tree.
>
> Edit autoproj/overrides.rb and add
>
> rtt = Autobuild::Package['rtt']
> rtt.define "VAR", "VALUE"
> rtt.define "VAR", "VALUE"
> rtt.define "VAR", "VALUE"
> rtt.define "VAR", "VALUE"
>
> ocl = Autobuild::Package['ocl']
> ocl.define "VAR", "VALUE"
> ocl.define "VAR", "VALUE"
> ocl.define "VAR", "VALUE"
> ocl.define "VAR", "VALUE"
>
>
>
I up an old discussion. When I updated my toolchain from 2.0 to 2.1 things
went wrong because some of my cmake options were overrided by autoproj
update. As 2.2 migrating went wrong I create the toolchain back to zero, to
be sure having a working installation quickly, so I could not test if it
went better this time.

The usefull advice to prevent this lost of cmake options was to use
autoproj/overrides.rb. Can you confirm that this file is not reset when
switching branches and/or updating the toolchain ?

> --
> Sylvain Joyeux (Dr. Ing.)
> Researcher - Space and Security Robotics
> DFKI Robotics Innovation Center
> Bremen, Robert-Hooke-Straße 5, 28359 Bremen, Germany
>
> Phone: +49 421 218-64136
> Fax: +49 421 218-64150
> Email: sylvain [dot] joyeux [..] ...
>
> Weitere Informationen: http://www.dfki.de
>

Orocos Toolchain v2.1.0 Released

On 12/15/2010 01:27 PM, Willy Lambert wrote:
>
>
> 2010/10/13 Sylvain Joyeux <sylvain [dot] joyeux [..] ...
> <mailto:sylvain [dot] joyeux [..] ...>>
>
> You can also add/override CMake options in autoproj itself -- if you
> don't want to modify the RTT/OCL tree.
>
> Edit autoproj/overrides.rb and add
>
> rtt = Autobuild::Package['rtt']
> rtt.define "VAR", "VALUE"
> rtt.define "VAR", "VALUE"
> rtt.define "VAR", "VALUE"
> rtt.define "VAR", "VALUE"
>
> ocl = Autobuild::Package['ocl']
> ocl.define "VAR", "VALUE"
> ocl.define "VAR", "VALUE"
> ocl.define "VAR", "VALUE"
> ocl.define "VAR", "VALUE"
>
>
>
> I up an old discussion. When I updated my toolchain from 2.0 to 2.1
> things went wrong because some of my cmake options were overrided by
> autoproj update. As 2.2 migrating went wrong I create the toolchain back
> to zero, to be sure having a working installation quickly, so I could
> not test if it went better this time.
>
> The usefull advice to prevent this lost of cmake options was to use
> autoproj/overrides.rb. Can you confirm that this file is not reset when
> switching branches and/or updating the toolchain ?

overrides.rb is governed by the rules of git updates and autoproj
switch-config.

What does this mean in practice ?

* if you bootstrap anew, it *is* lost, obviously
* if you do switch-config and simply change the branch, it will be
considered by git as a local change. I.e. if the new branch has
modifications in overrides.rb, then autoproj will refuse updating
(you will have to merge yourself)

If you guys have a better way to store 'local' options, I'm listening.

Orocos Toolchain v2.1.0 Released

2010/12/15 Sylvain Joyeux <sylvain [dot] joyeux [..] ...>

> On 12/15/2010 01:27 PM, Willy Lambert wrote:
>
>>
>>
>> 2010/10/13 Sylvain Joyeux <sylvain [dot] joyeux [..] ...
>> <mailto:sylvain [dot] joyeux [..] ...>>
>>
>>
>> You can also add/override CMake options in autoproj itself -- if you
>> don't want to modify the RTT/OCL tree.
>>
>> Edit autoproj/overrides.rb and add
>>
>> rtt = Autobuild::Package['rtt']
>> rtt.define "VAR", "VALUE"
>> rtt.define "VAR", "VALUE"
>> rtt.define "VAR", "VALUE"
>> rtt.define "VAR", "VALUE"
>>
>> ocl = Autobuild::Package['ocl']
>> ocl.define "VAR", "VALUE"
>> ocl.define "VAR", "VALUE"
>> ocl.define "VAR", "VALUE"
>> ocl.define "VAR", "VALUE"
>>
>>
>>
>> I up an old discussion. When I updated my toolchain from 2.0 to 2.1
>> things went wrong because some of my cmake options were overrided by
>> autoproj update. As 2.2 migrating went wrong I create the toolchain back
>> to zero, to be sure having a working installation quickly, so I could
>> not test if it went better this time.
>>
>> The usefull advice to prevent this lost of cmake options was to use
>> autoproj/overrides.rb. Can you confirm that this file is not reset when
>> switching branches and/or updating the toolchain ?
>>
>
> overrides.rb is governed by the rules of git updates and autoproj
> switch-config.
>
> What does this mean in practice ?
>
> * if you bootstrap anew, it *is* lost, obviously
>

of course, it's my job to save it.

> * if you do switch-config and simply change the branch, it will be
> considered by git as a local change. I.e. if the new branch has
> modifications in overrides.rb, then autoproj will refuse updating
> (you will have to merge yourself)
>

in pratice this git-update is done in the "autoproj update" command, so is
there flag rised during this autorpoj step to inform me that I have a manual
merge to do ?
Will it be possible to have a "user_overrides.rb" that never change on git ?

> If you guys have a better way to store 'local' options, I'm listening.
>
> --
> Sylvain Joyeux (Dr. Ing.)
> Researcher - Space and Security Robotics
> DFKI Robotics Innovation Center
> Bremen, Robert-Hooke-Straße 5, 28359 Bremen, Germany
>
> Phone: +49 421 218-64136
> Fax: +49 421 218-64150
> Email: sylvain [dot] joyeux [..] ...
>
> Weitere Informationen: http://www.dfki.de
>

Orocos Toolchain v2.1.0 Released

On 12/15/2010 01:40 PM, Willy Lambert wrote:
> in pratice this git-update is done in the "autoproj update" command, so
> is there flag rised during this autorpoj step to inform me that I have a
> manual merge to do ?
If a merge is needed, autoproj will exit with an error and give you the
git output.

> Will it be possible to have a "user_overrides.rb" that never change on git ?
I guess so. I would prefer local_overrides.rb would be better IMO.

Sylvain

Orocos Toolchain v2.1.0 Released

On Oct 13, 2010, at 12:58 , Sylvain Joyeux wrote:

> You can also add/override CMake options in autoproj itself -- if you
> don't want to modify the RTT/OCL tree.
>
> Edit autoproj/overrides.rb and add
>
> rtt = Autobuild::Package['rtt']
> rtt.define "VAR", "VALUE"
> rtt.define "VAR", "VALUE"
> rtt.define "VAR", "VALUE"
> rtt.define "VAR", "VALUE"
>
> ocl = Autobuild::Package['ocl']
> ocl.define "VAR", "VALUE"
> ocl.define "VAR", "VALUE"
> ocl.define "VAR", "VALUE"
> ocl.define "VAR", "VALUE"

Very useful to know. Is that doc'd on the toolchain website/wiki?
S

Orocos Toolchain v2.1.0 Released

interesting

which is the recommanded use

2010/10/13 S Roderick <kiwi [dot] net [..] ...>

> On Oct 13, 2010, at 12:58 , Sylvain Joyeux wrote:
>
> > You can also add/override CMake options in autoproj itself -- if you
> > don't want to modify the RTT/OCL tree.
> >
> > Edit autoproj/overrides.rb and add
> >
> > rtt = Autobuild::Package['rtt']
> > rtt.define "VAR", "VALUE"
> > rtt.define "VAR", "VALUE"
> > rtt.define "VAR", "VALUE"
> > rtt.define "VAR", "VALUE"
> >
> > ocl = Autobuild::Package['ocl']
> > ocl.define "VAR", "VALUE"
> > ocl.define "VAR", "VALUE"
> > ocl.define "VAR", "VALUE"
> > ocl.define "VAR", "VALUE"
>
> Very useful to know. Is that doc'd on the toolchain website/wiki?
> S
>

Orocos Toolchain v2.1.0 Released

On Wed, Oct 13, 2010 at 8:53 PM, Willy Lambert <lambert [dot] willy [..] ...>wrote:

> interesting
>
> which is the recommanded use
>
>
> 2010/10/13 S Roderick <kiwi [dot] net [..] ...>
>
>> On Oct 13, 2010, at 12:58 , Sylvain Joyeux wrote:
>>
>>
>> > You can also add/override CMake options in autoproj itself -- if you
>> > don't want to modify the RTT/OCL tree.
>> >
>> > Edit autoproj/overrides.rb and add
>> >
>> > rtt = Autobuild::Package['rtt']
>> > rtt.define "VAR", "VALUE"
>> > rtt.define "VAR", "VALUE"
>> > rtt.define "VAR", "VALUE"
>> > rtt.define "VAR", "VALUE"
>> >
>> > ocl = Autobuild::Package['ocl']
>> > ocl.define "VAR", "VALUE"
>> > ocl.define "VAR", "VALUE"
>> > ocl.define "VAR", "VALUE"
>> > ocl.define "VAR", "VALUE"
>>
>> Very useful to know. Is that doc'd on the toolchain website/wiki?
>> S
>>
>
>
You can also invoke cmake with the -C command-line option and provide a
script that preloads cache variables. We use this a lot to customize builds.

Adolfo

Orocos Toolchain v2.1.0 Released

On Oct 13, 2010, at 12:02 , Willy Lambert wrote:

>
>
> 2010/10/13 Sylvain Joyeux <sylvain [dot] joyeux [..] ...>
> On 10/13/2010 11:06 AM, Peter Soetens wrote:
> On Wednesday 13 October 2010 09:38:11 Willy Lambert wrote:
> I failed updating my Orocos.
>
> I did :
> autoproj update
> autoproj build
> And everything run without errors.
>
> But my [autorpoj_path]/rrt/CMakeLists.txt chows a "2.0.2" version.
>
> It does not upgrade you accross major releases. You need to re-bootstrap with
> the new bootstrap.sh script in a fresh directory OR run these two commands:
>
> autoproj switch-config git git://gitorious.com/orocos-toolchain/build.git \
> branch=toolchain-2.1
> autoproj update
>
> Yuk. Could we have a 'latest' branch that follows always the latest version ?
>
>
> by the way, do the autoproj update erase my CMakeCache files ?
> Yes, it does. The problem is that CMake has a tendency to cache way too much information and that is the best way to ensure smooth long time upgrades.
>
> What kind of issue did that cause for you ?
>
> nothing hurtfull, but i activated logging in ocl and changed rtt option in order to use "real time logging" (as mentionned in the wiki); so the only impact is that it broke my hudson builds ;)
>
> maybe i should mention this variables in my cmake scripts, but as my orocos integration in cmake is not perfect currently i used to modify cmake cache

Create rtt/orocos-rtt.cmake and ocl/orocos-ocl.cmake files in the source tree, and set your defaults there. Then just cmake'ing again will keep your options.

Mine contain items like this for RTT

&#10;...&#10;OPTION( OS_RT_MALLOC &quot;&quot; ON)&#10;OPTION( OS_RT_MALLOC_SBRK &quot;&quot; OFF)&#10;OPTION( OS_RT_MALLOC_MMAP &quot;&quot; OFF)&#10;OPTION( OS_RT_MALLOC_STATS &quot;&quot; ON)&#10;OPTION( OS_RT_MALLOC_DEBUG &quot;&quot; ON)&#10;&#10;OPTION(OROSEM_LOG4CPP_LOGGING &quot;&quot; ON)&#10;...&#10;

and this for OCL

&#10;...&#10;OPTION(BUILD_RTALLOC &quot;&quot; ON)&#10;OPTION(BUILD_LOGGING &quot;&quot; ON)&#10;&#10;OPTION(BUILD_TESTS &quot;&quot; OFF)&#10;OPTION(BUILD_HELLOWORLD &quot;&quot; OFF)&#10;...&#10;

Orocos Toolchain v2.1.0 Released

2010/10/13 S Roderick <kiwi [dot] net [..] ...>

> On Oct 13, 2010, at 12:02 , Willy Lambert wrote:
>
>
>
> 2010/10/13 Sylvain Joyeux <sylvain [dot] joyeux [..] ...>
>
>> On 10/13/2010 11:06 AM, Peter Soetens wrote:
>>
>>> On Wednesday 13 October 2010 09:38:11 Willy Lambert wrote:
>>>
>>>> I failed updating my Orocos.
>>>>
>>>> I did :
>>>> autoproj update
>>>> autoproj build
>>>> And everything run without errors.
>>>>
>>>> But my [autorpoj_path]/rrt/CMakeLists.txt chows a "2.0.2" version.
>>>>
>>>
>>> It does not upgrade you accross major releases. You need to re-bootstrap
>>> with
>>> the new bootstrap.sh script in a fresh directory OR run these two
>>> commands:
>>>
>>> autoproj switch-config git git://
>>> gitorious.com/orocos-toolchain/build.git \
>>> branch=toolchain-2.1
>>> autoproj update
>>>
>>
>> Yuk. Could we have a 'latest' branch that follows always the latest
>> version ?
>>
>>
>> by the way, do the autoproj update erase my CMakeCache files ?
>>>>
>>> Yes, it does. The problem is that CMake has a tendency to cache way too
>> much information and that is the best way to ensure smooth long time
>> upgrades.
>>
>> What kind of issue did that cause for you ?
>>
>
> nothing hurtfull, but i activated logging in ocl and changed rtt option in
> order to use "real time logging" (as mentionned in the wiki); so the only
> impact is that it broke my hudson builds ;)
>
> maybe i should mention this variables in my cmake scripts, but as my orocos
> integration in cmake is not perfect currently i used to modify cmake cache
>
>
> Create rtt/orocos-rtt.cmake and ocl/orocos-ocl.cmake files in the source
> tree, and set your defaults there. Then just cmake'ing again will keep your
> options.
>

thanks for this advice i will apply this on my toolchain

>
> Mine contain items like this for RTT
>
> &#10;&gt; ...&#10;&gt; OPTION( OS_RT_MALLOC &quot;&quot; ON)&#10;&gt; OPTION( OS_RT_MALLOC_SBRK &quot;&quot; OFF)&#10;&gt; OPTION( OS_RT_MALLOC_MMAP &quot;&quot; OFF)&#10;&gt; OPTION( OS_RT_MALLOC_STATS &quot;&quot; ON)&#10;&gt; OPTION( OS_RT_MALLOC_DEBUG &quot;&quot; ON)&#10;&gt;&#10;&gt; OPTION(OROSEM_LOG4CPP_LOGGING &quot;&quot; ON&#10;&gt;&#10;...&#10;&gt;
>
> and this for OCL
>
> &#10;&gt; ...&#10;&gt; OPTION(BUILD_RTALLOC &quot;&quot; ON)&#10;&gt; OPTION(BUILD_LOGGING &quot;&quot; ON)&#10;&gt;&#10;&gt; OPTION(BUILD_TESTS &quot;&quot; OFF)&#10;&gt; OPTION(BUILD_HELLOWORLD &quot;&quot; OFF)&#10;&gt; ...&#10;&gt;
>
>
> are theses logging option and more generally real time log4cpp features in
2.1

Orocos Toolchain v2.1.0 Released

On Oct 13, 2010, at 12:32 , Willy Lambert wrote:

>
>
> 2010/10/13 S Roderick <kiwi [dot] net [..] ...>
> On Oct 13, 2010, at 12:02 , Willy Lambert wrote:
>
>>
>>
>> 2010/10/13 Sylvain Joyeux <sylvain [dot] joyeux [..] ...>
>> On 10/13/2010 11:06 AM, Peter Soetens wrote:
>> On Wednesday 13 October 2010 09:38:11 Willy Lambert wrote:
>> I failed updating my Orocos.
>>
>> I did :
>> autoproj update
>> autoproj build
>> And everything run without errors.
>>
>> But my [autorpoj_path]/rrt/CMakeLists.txt chows a "2.0.2" version.
>>
>> It does not upgrade you accross major releases. You need to re-bootstrap with
>> the new bootstrap.sh script in a fresh directory OR run these two commands:
>>
>> autoproj switch-config git git://gitorious.com/orocos-toolchain/build.git \
>> branch=toolchain-2.1
>> autoproj update
>>
>> Yuk. Could we have a 'latest' branch that follows always the latest version ?
>>
>>
>> by the way, do the autoproj update erase my CMakeCache files ?
>> Yes, it does. The problem is that CMake has a tendency to cache way too much information and that is the best way to ensure smooth long time upgrades.
>>
>> What kind of issue did that cause for you ?
>>
>> nothing hurtfull, but i activated logging in ocl and changed rtt option in order to use "real time logging" (as mentionned in the wiki); so the only impact is that it broke my hudson builds ;)
>>
>> maybe i should mention this variables in my cmake scripts, but as my orocos integration in cmake is not perfect currently i used to modify cmake cache
>
> Create rtt/orocos-rtt.cmake and ocl/orocos-ocl.cmake files in the source tree, and set your defaults there. Then just cmake'ing again will keep your options.
>
> thanks for this advice i will apply this on my toolchain
>
>
> Mine contain items like this for RTT
>
> &#10;&gt; ...&#10;&gt; OPTION( OS_RT_MALLOC &quot;&quot; ON)&#10;&gt; OPTION( OS_RT_MALLOC_SBRK &quot;&quot; OFF)&#10;&gt; OPTION( OS_RT_MALLOC_MMAP &quot;&quot; OFF)&#10;&gt; OPTION( OS_RT_MALLOC_STATS &quot;&quot; ON)&#10;&gt; OPTION( OS_RT_MALLOC_DEBUG &quot;&quot; ON)&#10;&gt; &#10;&gt; OPTION(OROSEM_LOG4CPP_LOGGING &quot;&quot; ON &#10;&gt; ...&#10;&gt;
>
> and this for OCL
>
> &#10;&gt; ...&#10;&gt; OPTION(BUILD_RTALLOC &quot;&quot; ON)&#10;&gt; OPTION(BUILD_LOGGING &quot;&quot; ON)&#10;&gt; &#10;&gt; OPTION(BUILD_TESTS &quot;&quot; OFF)&#10;&gt; OPTION(BUILD_HELLOWORLD &quot;&quot; OFF)&#10;&gt; ...&#10;&gt;
>
>
> are theses logging option and more generally real time log4cpp features in 2.1
>
These are the options for RTT and OCL v1. I have not yet updated to v2, so I'm not sure if they've changed (I don't believe that they have ...)
S

Orocos Toolchain v2.1.0 Released

2010/10/13 Peter Soetens <peter [..] ...>

> On Wednesday 13 October 2010 09:38:11 Willy Lambert wrote:
> > I failed updating my Orocos.
> >
> > I did :
> > autoproj update
> > autoproj build
> > And everything run without errors.
> >
> > But my [autorpoj_path]/rrt/CMakeLists.txt chows a "2.0.2" version.
>
> It does not upgrade you accross major releases. You need to re-bootstrap
> with
> the new bootstrap.sh script in a fresh directory OR run these two commands:
>

autoproj switch-config git git://gitorious.com/orocos-toolchain/build.git \
> branch=toolchain-2.1
> autoproj update
>
> then
>
> autoproj build
> as usual.
>
>
Thanks

> >
> > I did try to re-download booststrap.sh (because it's not clear for me if
> > it's done with the autoproj update or not), re-run bootstrap.sh, and
> update
> > and build, but nothing changed.
>
> Did you do this in a fresh directory ? There was a bug in the bootstrapping
> process which prevented succesful completion which I just fixed.
>

No I did not and apparently it failed

>
> > I would appreciate that autoproj tells something about versions (I don't
> > know wether it's possible or not), because it would definitely help
> knowing
> > if we build the rigth toolchain
>
> autoproj has been told to checkout 'branches'. It knows about these branch
> names, but indeed it does not display them. You can manually inspect
> rtt/CMakeLists.txt though.
>
> >
> > by the way, do the autoproj update erase my CMakeCache files ?
>
> I never saw this happening here.

and what about this ?
autoproj switch-config git git://gitorious.com/orocos-toolchain/build.git \
branch=toolchain-2.1

>
> I'll provide these upgrading instructions on the wiki.
>

Maybe this could be added in
http://www.orocos.org/wiki/orocos/toolchain/quick-start at "Maintaining the
toolchain uptodate" section ?

>
> Peter
>

Orocos Toolchain v2.1.0 Released

On Wednesday 13 October 2010 11:30:59 Willy Lambert wrote:
> 2010/10/13 Peter Soetens <peter [..] ...>
> and what about this ?
> autoproj switch-config git git://gitorious.com/orocos-toolchain/build.git \
> branch=toolchain-2.1
>
> > I'll provide these upgrading instructions on the wiki.
>
> Maybe this could be added in
> http://www.orocos.org/wiki/orocos/toolchain/quick-start at "Maintaining the
> toolchain uptodate" section ?

I have. There's now a 'Using Autoproj' wiki page that describes these steps
and some back-and-forth linking between wiki pages.

Peter