The Orocos development team is pleased to announce the third bug fix
release of the Real-Time Toolkit v1.8, a C++ toolkit for building
component based, real-time robotics and machine control applications.
You can download this release from
http://www.orocos.org/stable/rtt/v1.8.3/orocos-rtt-1.8.3-src.tar.bz2
and read the installation instructions on
http://www.orocos.org/stable/documentation/rtt/v1.8.x/doc-xml/orocos-ins...
This release fixes a bug in the CORBA layer causing crashes in certain
cases. Timeouts when using semaphores in GNU/Linux were fixed.
Some overall documentation and cmake updates were included in this
release as well. This release also adds the VectorTemplateComposition
header for building custom types based on std::vector in the scripting
language.
For your information, this is essentially the svn trunk (apart from
version numbers).
I also had to reorder some wrongly placed include directives, but this
should fix problems instead of causing them. I also disabled Doxygen
IDL docs generation because it was interfering with the more important
C++ documentation.
You can see the full commit log by browsing our websvn on
http://svn.mech.kuleuven.be/websvn/orocos/trunk/rtt/?op=log&rev=0&isdir=1
Peter
Orocos Real-Time Tookit v1.8.3 released
A last-minute header 'fix' caused compile errors in the sources.
Didn't double check, sorry.
You can get RTT 1.8.4 from:
http://www.orocos.org/stable/rtt/v1.8.4/orocos-rtt-1.8.4-src.tar.bz2
The docs are being pushed to server as well.
Peter
Orocos Real-Time Tookit v1.8.3 released
On Jun 19, 2009, at 06:03 , Peter Soetens wrote:
> A last-minute header 'fix' caused compile errors in the sources.
> Didn't double check, sorry.
>
> You can get RTT 1.8.4 from:
>
> http://www.orocos.org/stable/rtt/v1.8.4/orocos-rtt-1.8.4-src.tar.bz2
>
> The docs are being pushed to server as well.
>
> Peter
With releases in mind, how do we want to handle these when it comes to
package managers (and their checksums in particular)? Given that the
package manager files are *inside* the release, checksumming the
release and then updating those files invalidates the checksum. Very
Bad.
How do we want to structure the overal codebase to deal with this? My
first thought is to place all package manager files outside of rtt/kdl/
bfl/ocl, but do others have any ideas?
Stephen