RTT and OCL 2.0.0-beta2 Released
| Submitted by peter on Fri, 2010-04-02 09:36 |
It's called beta, but it's closer to release candidate than its name
suggests. This preview release of RTT 2.0 is capable of doing anything
you could do in 1.x, but only better, faster and cheaper. We're very
close to a feature freeze at this point in time and focus on the
testing and taking the latest user feedback into account. The main
focus of this release was to get CORBA transport up and running. It
needs polishing, but you can taskbrowse corba-deployed components.
For the latest information, check out the 2.0.0-beta2 wiki page:
http://www.orocos.org/wiki/rtt/rtt-20/rtt-200-beta2
It links to a bunch of useful sub-pages concerning what changed and how users
can upgrade.
Where to find it ?
There are tar balls and online docs available in the devel section of the
server kindly provided by the University of Leuven:
http://people.mech.kuleuven.be/~orocos/pub/devel/rtt/v1.99.2/doc/api/html/
http://people.mech.kuleuven.be/~orocos/pub/devel/rtt/v1.99.2/orocos-rtt-...
http://people.mech.kuleuven.be/~orocos/pub/devel/ocl/v1.99.2/doc/api/html/
http://people.mech.kuleuven.be/~orocos/pub/devel/ocl/v1.99.2/orocos-ocl-...
The exercises of beta1 still apply (1.99.1):
http://people.mech.kuleuven.be/~orocos/pub/devel/examples/rtt/tutorial
Other official code resources for 2.0 are my git repositories on github: rtt-
examples, orocos-rtt and orocos-ocl. Check out the ocl-2.0-mainline and
rtt-2.0-mainline code. I will not host 2.0 in an SVN repository.
What's not in here ?
See the caveats section on the wiki. Attention is now going to easy typekit
generation and plugin loading.
What will this release allow you to do ?
- Test porting effort to the RTT 2.0 C++ and CORBA API.
We have created scripts for converting application code to the 2.0 API,
regarding the C++ part.
- Test RTT 2.0 on your distribution/target.
A lot of code changed, not all compilers or operating systems could be tested.
Now is the time to see if 2.0 *at least compiles* on your system.
Requires cmake 2.6-patch3 to build or later.
What can you do to help ?
- Test the conversion scripts and update the wiki or scripts if you find
issues.
- Update wiki pages, installation notes etc if you encounter inconsistencies.
- Send patches against this codebase, preferably using a git repository.
- Provide feedback on documentation or API changes.
Are we there yet ?
There's need for more testing and user feedback before we can make it
to a final release. I'm trying to postpone feature additions after
2.0.0 such that we can release as early as possible. A new release
will follow around end of April, that could qualify as release
candidate.
Enjoy !
Peter
RTT and OCL 2.0.0-beta2 Released
On Fri, Apr 02, 2010 at 11:33:04AM +0200, Peter Soetens wrote:
>
> - Test the conversion scripts and update the wiki or scripts if you find
> issues.
The tarball
http://www.orocos.org/files/rtt2-converter-0.2.tar__0.bz2
seems corrupted?!
There seems to be a comma missing in the perl script:
---
to-rtt-2.0.pl | 2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
diff --git a/to-rtt-2.0.pl b/to-rtt-2.0.pl
index 2491748..74e4c4c 100755
--- a/to-rtt-2.0.pl
+++ b/to-rtt-2.0.pl
@@ -26,7 +26,7 @@ if ($strict) {
"Ports.hpp" => "Port.hpp",
"Marshaller" => "MarshallInterface",
"Demarshaller" => "DemarshallInterface",
- "marshalling\(\)->" => "getProvider<Marshalling>(\"marshalling\")->"
+ "marshalling\(\)->" => "getProvider<Marshalling>(\"marshalling\")->",
"scripting\(\)->" => "getProvider<Scripting>(\"scripting\")->"
);
RTT and OCL 2.0.0-beta2 Released
On Thu, Apr 15, 2010 at 15:51, Markus Klotzbuecher
<markus [dot] klotzbuecher [..] ...> wrote:
> On Fri, Apr 02, 2010 at 11:33:04AM +0200, Peter Soetens wrote:
>>
>> - Test the conversion scripts and update the wiki or scripts if you find
>> issues.
>
> The tarball
>
> http://www.orocos.org/files/rtt2-converter-0.2.tar__0.bz2
>
> seems corrupted?!
>
>
> There seems to be a comma missing in the perl script:
Oh great :-/ Maybe I should upload this thing into a git repository as
well such that you can track/contribute easier...
Peter
RTT and OCL 2.0.0-beta2 Released
Hi,
On Fri, Apr 2, 2010 at 11:33 AM, Peter Soetens <peter [..] ...> wrote:
[...]
> For the latest information, check out the 2.0.0-beta2 wiki page:
> http://www.orocos.org/wiki/rtt/rtt-20/rtt-200-beta2
[disclaimer: I've ran the tests from the git repository, and ran a hg
update -C to the rtt-2.0-mainline]
Platform: debian testing, gcc 4.4.3, boost 1.40
I have 3 failing tests (instead of only types-test), it's not obvious
if this is due to timing issues.
Best regards,
Klaas
====================================================================================
Test project /tmp/orocos-rtt.git/build/tests
Constructing a list of tests
Done constructing a list of tests
Checking test dependency graph...
test 1
Start 1: main-test
1: Test command: /tmp/orocos-rtt.git/build/tests/main-test
1: Test timeout computed to be: 9.99988e+06
1/26 Test #1: main-test ........................ Passed 0.96 sec
test 2
Start 2: list-test
2: Test command: /tmp/orocos-rtt.git/build/tests/list-test
2: Test timeout computed to be: 9.99988e+06
2: Running 2 test cases...
2:
2: *** No errors detected
2/26 Test #2: list-test ........................ Passed 0.10 sec
test 3
Start 3: core-test
3: Test command: /tmp/orocos-rtt.git/build/tests/core-test
3: Test timeout computed to be: 9.99988e+06
3: Running 11 test cases...
3:
3: *** No errors detected
3/26 Test #3: core-test ........................ Passed 5.17 sec
test 4
Start 4: task-test
4: Test command: /tmp/orocos-rtt.git/build/tests/task-test
4: Test timeout computed to be: 9.99988e+06
4: Running 20 test cases...
4:
4: *** No errors detected
4/26 Test #4: task-test ........................ Passed 21.50 sec
test 5
Start 5: specactivities-test
5: Test command: /tmp/orocos-rtt.git/build/tests/specactivities-test
5: Test timeout computed to be: 9.99988e+06
5: Running 1 test case...
5:
5: *** No errors detected
5/26 Test #5: specactivities-test .............. Passed 2.32 sec
test 6
Start 6: mqueue-test
6: Test command: /tmp/orocos-rtt.git/build/tests/mqueue-test
6: Test timeout computed to be: 9.99988e+06
6: Running 5 test cases...
6:
6: *** No errors detected
6/26 Test #6: mqueue-test ...................... Passed 3.20 sec
test 7
Start 7: mqueue_archive_test
7: Test command: /tmp/orocos-rtt.git/build/tests/mqueue_archive_test
7: Test timeout computed to be: 9.99988e+06
7: Running 1 test case...
7:
7: *** No errors detected
7/26 Test #7: mqueue_archive_test .............. Passed 0.06 sec
test 8
Start 8: buffers_test
8: Test command: /tmp/orocos-rtt.git/build/tests/buffers_test
8: Test timeout computed to be: 9.99988e+06
8: Running 6 test cases...
8:
8: Total appends: 53498195
8: Total erases : 53498195
8: Left in Queue: 0
8:
8: *** No errors detected
8/26 Test #8: buffers_test ..................... Passed 40.40 sec
test 9
Start 9: method_test
9: Test command: /tmp/orocos-rtt.git/build/tests/method_test
9: Test timeout computed to be: 9.99988e+06
9: Running 7 test cases...
9:
9: *** No errors detected
9/26 Test #9: method_test ...................... Passed 0.14 sec
test 10
Start 10: functors_test
10: Test command: /tmp/orocos-rtt.git/build/tests/functors_test
10: Test timeout computed to be: 9.99988e+06
10: Running 3 test cases...
10:
10: *** No errors detected
10/26 Test #10: functors_test .................... Passed 0.09 sec
test 11
Start 11: service_test
11: Test command: /tmp/orocos-rtt.git/build/tests/service_test
11: Test timeout computed to be: 9.99988e+06
11: Running 4 test cases...
11:
11: *** No errors detected
11/26 Test #11: service_test ..................... Passed 0.10 sec
test 12
Start 12: event_test
12: Test command: /tmp/orocos-rtt.git/build/tests/event_test
12: Test timeout computed to be: 9.99988e+06
12: Running 11 test cases...
12:
12: *** No errors detected
12/26 Test #12: event_test ....................... Passed 1.20 sec
test 13
Start 13: operation_test
13: Test command: /tmp/orocos-rtt.git/build/tests/operation_test
13: Test timeout computed to be: 9.99988e+06
13: Running 7 test cases...
13:
13: *** No errors detected
13/26 Test #13: operation_test ................... Passed 0.09 sec
test 14
Start 14: taskstates_test
14: Test command: /tmp/orocos-rtt.git/build/tests/taskstates_test
14: Test timeout computed to be: 9.99988e+06
14: Running 5 test cases...
14:
14: *** No errors detected
14/26 Test #14: taskstates_test .................. Passed 0.10 sec
test 15
Start 15: ports_test
15: Test command: /tmp/orocos-rtt.git/build/tests/ports_test
15: Test timeout computed to be: 9.99988e+06
15: Running 8 test cases...
15:
15: *** No errors detected
15/26 Test #15: ports_test ....................... Passed 0.15 sec
test 16
Start 16: attributes_test
16: Test command: /tmp/orocos-rtt.git/build/tests/attributes_test
16: Test timeout computed to be: 9.99988e+06
16: Running 2 test cases...
16:
16: *** No errors detected
16/26 Test #16: attributes_test .................. Passed 0.07 sec
test 17
Start 17: dev_test
17: Test command: /tmp/orocos-rtt.git/build/tests/dev_test
17: Test timeout computed to be: 9.99988e+06
17: Running 2 test cases...
17:
17: *** No errors detected
17/26 Test #17: dev_test ......................... Passed 0.06 sec
test 18
Start 18: scripting_test
18: Test command: /tmp/orocos-rtt.git/build/tests/scripting_test
18: Test timeout computed to be: 9.99988e+06
18: Running 1 test case...
18: /tmp/orocos-rtt.git/tests/scripting_test.cpp(34): error in
"TestGetProvider": check sc->isProgramRunning("Foo") == false failed
18:
18: *** 1 failure detected in test suite "Master Test Suite"
18/26 Test #18: scripting_test ...................***Failed 0.17
sec
test 19
Start 19: types_test
19: Test command: /tmp/orocos-rtt.git/build/tests/types_test
19: Test timeout computed to be: 9.99988e+06
19: Running 7 test cases...
19: print:2
19: print:2
19: /tmp/orocos-rtt.git/tests/types_test.cpp(427): error in
"testTypes": check (*pg_list.begin())->start() failed
19: /tmp/orocos-rtt.git/tests/types_test.cpp(433): error in
"testTypes": State error on line 52.
19:
19:
19: *** 2 failures detected in test suite "Master Test Suite"
19/26 Test #19: types_test .......................***Failed 1.19
sec
test 20
Start 20: program_test
20: Test command: /tmp/orocos-rtt.git/build/tests/program_test
20: Test timeout computed to be: 9.99988e+06
20: Running 12 test cases...
20:
20: *** No errors detected
20/26 Test #20: program_test ..................... Passed 0.68 sec
test 21
Start 21: state_test
21: Test command: /tmp/orocos-rtt.git/build/tests/state_test
21: Test timeout computed to be: 9.99988e+06
21: Running 11 test cases...
21:
21: *** No errors detected
21/26 Test #21: state_test ....................... Passed 4.37 sec
test 22
Start 22: function_test
22: Test command: /tmp/orocos-rtt.git/build/tests/function_test
22: Test timeout computed to be: 9.99988e+06
22: Running 11 test cases...
22: /tmp/orocos-rtt.git/tests/function_test.cpp(129): error in
"testOnlyExportFunction": check foo.ready() failed
22: /tmp/orocos-rtt.git/tests/function_test.cpp(134): error in
"testOnlyExportFunction": check foo_ret.ready() failed
22: /tmp/orocos-rtt.git/tests/function_test.cpp(138): error in
"testOnlyExportFunction": check i == 3 failed [0 != 3]
22: /tmp/orocos-rtt.git/tests/function_test.cpp(142): error in
"testOnlyExportFunction": check foo_args.ready() failed
22: /tmp/orocos-rtt.git/tests/function_test.cpp(148): error in
"testOnlyExportFunction": check i == -1 failed [0 != -1]
22: /tmp/orocos-rtt.git/tests/function_test.cpp(152): error in
"testOnlyExportFunction": check i == +1 failed [0 != 1]
22:
22: *** 6 failures detected in test suite "Master Test Suite"
22/26 Test #22: function_test ....................***Failed 0.61 sec
test 23
Start 23: marshalling_test
23: Test command: /tmp/orocos-rtt.git/build/tests/marshalling_test
23: Test timeout computed to be: 9.99988e+06
23: Running 1 test case...
23:
23: *** No errors detected
23/26 Test #23: marshalling_test ................. Passed 0.07 sec
test 24
Start 24: property_loader_test
24: Test command: /tmp/orocos-rtt.git/build/tests/property_loader_test
24: Test timeout computed to be: 9.99988e+06
24: Running 1 test case...
24:
24: *** No errors detected
24/26 Test #24: property_loader_test ............. Passed 0.26 sec
test 25
Start 25: property_marsh_test
25: Test command: /tmp/orocos-rtt.git/build/tests/property_marsh_test
25: Test timeout computed to be: 9.99988e+06
25: Running 2 test cases...
25:
25: *** No errors detected
25/26 Test #25: property_marsh_test .............. Passed 0.07 sec
test 26
Start 26: property_test
26: Test command: /tmp/orocos-rtt.git/build/tests/property_test
26: Test timeout computed to be: 9.99988e+06
26: Running 9 test cases...
26:
26: *** No errors detected
26/26 Test #26: property_test .................... Passed 0.09 sec
88% tests passed, 3 tests failed out of 26
Total Test time (real) = 83.28 sec
The following tests FAILED:
18 - scripting_test (Failed)
19 - types_test (Failed)
22 - function_test (Failed)
RTT and OCL 2.0.0-beta2 Released
On Apr 15, 2010, at 04:01 , Klaas Gadeyne wrote:
> Hi,
>
> On Fri, Apr 2, 2010 at 11:33 AM, Peter Soetens <peter [..] ...> wrote:
> [...]
>> For the latest information, check out the 2.0.0-beta2 wiki page:
>> http://www.orocos.org/wiki/rtt/rtt-20/rtt-200-beta2
>
> [disclaimer: I've ran the tests from the git repository, and ran a hg
> update -C to the rtt-2.0-mainline]
>
> Platform: debian testing, gcc 4.4.3, boost 1.40
>
> I have 3 failing tests (instead of only types-test), it's not obvious
> if this is due to timing issues.
>
> Best regards,
>
> Klaas
There was brief talk of a "build farm" a few months back. Has this gone any further?
Alternatively, any chance of setting up CDash on a centralized server, so that some of us can run builds and upload results? Getting CDash itself working is easy, getting the scripts/cron-jobs on the client machine is a little tricky but quite doable. Automating this would save some of this back and forward perhaps ...?
Stephen
RTT and OCL 2.0.0-beta2 Released
On Thu, Apr 15, 2010 at 13:56, S Roderick <kiwi [dot] net [..] ...> wrote:
> On Apr 15, 2010, at 04:01 , Klaas Gadeyne wrote:
>
>> Hi,
>>
>> On Fri, Apr 2, 2010 at 11:33 AM, Peter Soetens <peter [..] ...> wrote:
>> [...]
>>> For the latest information, check out the 2.0.0-beta2 wiki page:
>>> http://www.orocos.org/wiki/rtt/rtt-20/rtt-200-beta2
>>
>> [disclaimer: I've ran the tests from the git repository, and ran a hg
>> update -C to the rtt-2.0-mainline]
>>
>> Platform: debian testing, gcc 4.4.3, boost 1.40
>>
>> I have 3 failing tests (instead of only types-test), it's not obvious
>> if this is due to timing issues.
>>
>> Best regards,
>>
>> Klaas
>
> There was brief talk of a "build farm" a few months back. Has this gone any further?
>
> Alternatively, any chance of setting up CDash on a centralized server, so that some of us can run builds and upload results? Getting CDash itself working is easy, getting the scripts/cron-jobs on the client machine is a little tricky but quite doable. Automating this would save some of this back and forward perhaps ...?
I'm running a hudson on my development machine, also KUL runs a
hudson, pulling from the public repositories. We only get emails for
failing builds (I believe), not for failing tests.
I prefer hudson above cdash... or are they complementary in a way ?
Peter
RTT and OCL 2.0.0-beta2 Released
On Apr 20, 2010, at 12:08 , Peter Soetens wrote:
> On Thu, Apr 15, 2010 at 13:56, S Roderick <kiwi [dot] net [..] ...> wrote:
>> On Apr 15, 2010, at 04:01 , Klaas Gadeyne wrote:
>>
>>> Hi,
>>>
>>> On Fri, Apr 2, 2010 at 11:33 AM, Peter Soetens <peter [..] ...> wrote:
>>> [...]
>>>> For the latest information, check out the 2.0.0-beta2 wiki page:
>>>> http://www.orocos.org/wiki/rtt/rtt-20/rtt-200-beta2
>>>
>>> [disclaimer: I've ran the tests from the git repository, and ran a hg
>>> update -C to the rtt-2.0-mainline]
>>>
>>> Platform: debian testing, gcc 4.4.3, boost 1.40
>>>
>>> I have 3 failing tests (instead of only types-test), it's not obvious
>>> if this is due to timing issues.
>>>
>>> Best regards,
>>>
>>> Klaas
>>
>> There was brief talk of a "build farm" a few months back. Has this gone any further?
>>
>> Alternatively, any chance of setting up CDash on a centralized server, so that some of us can run builds and upload results? Getting CDash itself working is easy, getting the scripts/cron-jobs on the client machine is a little tricky but quite doable. Automating this would save some of this back and forward perhaps ...?
>
> I'm running a hudson on my development machine, also KUL runs a
> hudson, pulling from the public repositories. We only get emails for
> failing builds (I believe), not for failing tests.
>
> I prefer hudson above cdash... or are they complementary in a way ?
>
> Peter
Hudson looks nice, with some nice infrastructure integration that CDash lacks, but how can an external entity publish build results to a Hudson server? It seems to be built around a fairly fixed master/slave architecture, whereas CDash provides the server plus tools to run slave builds anywhere (and publish them back to the server). For Hudson, it looks like you need a login to the master server to publish, if using something like the Build Publisher plugin. One of the really nice features of CDash is the ability to easily push build results, for those of us that have different configurations (eg Mac OS X) that aren't currently system tested. This distributes the test effort.
I also can't find an example hudson site to review - at least CDash presents several working sites for potential new users!
Is the project interested in publishing build results, having others contribute build results, and in general, having more system configurations tested? [I would hope Yes, Yes and Yes]
Is anyone else personally interested in pursuing this kind of direction?
Stephen
RTT and OCL 2.0.0-beta2 Released
On Tuesday 20 April 2010 18:08:54 Peter Soetens wrote:
> On Thu, Apr 15, 2010 at 13:56, S Roderick <kiwi [dot] net [..] ...> wrote:
> > On Apr 15, 2010, at 04:01 , Klaas Gadeyne wrote:
> >> Hi,
> >>
> >> On Fri, Apr 2, 2010 at 11:33 AM, Peter Soetens
> >> <peter [..] ...> wrote: [...]
> >>
> >>> For the latest information, check out the 2.0.0-beta2 wiki page:
> >>> http://www.orocos.org/wiki/rtt/rtt-20/rtt-200-beta2
> >>
> >> [disclaimer: I've ran the tests from the git repository, and ran a hg
> >> update -C to the rtt-2.0-mainline]
> >>
> >> Platform: debian testing, gcc 4.4.3, boost 1.40
> >>
> >> I have 3 failing tests (instead of only types-test), it's not obvious
> >> if this is due to timing issues.
> >>
> >> Best regards,
> >>
> >> Klaas
> >
> > There was brief talk of a "build farm" a few months back. Has this gone
> > any further?
> >
> > Alternatively, any chance of setting up CDash on a centralized server, so
> > that some of us can run builds and upload results? Getting CDash itself
> > working is easy, getting the scripts/cron-jobs on the client machine is
> > a little tricky but quite doable. Automating this would save some of
> > this back and forward perhaps ...?
>
> I'm running a hudson on my development machine, also KUL runs a
> hudson, pulling from the public repositories. We only get emails for
> failing builds (I believe), not for failing tests.
I can let it send mails for failing tests too if you want ;)
Ruben
> I prefer hudson above cdash... or are they complementary in a way ?
>
> Peter
RTT and OCL 2.0.0-beta2 Released
[...]
> Where to find it ?
>
> There are tar balls and online docs available in the devel section of the
> server kindly provided by the University of Leuven:
>
> http://people.mech.kuleuven.be/~orocos/pub/devel/rtt/v1.99.2/doc/api/html/
> http://people.mech.kuleuven.be/~orocos/pub/devel/rtt/v1.99.2/orocos-rtt-...
> http://people.mech.kuleuven.be/~orocos/pub/devel/ocl/v1.99.2/doc/api/html/
> http://people.mech.kuleuven.be/~orocos/pub/devel/ocl/v1.99.2/orocos-ocl-...
>
> The exercises of beta1 still apply (1.99.1):
> http://people.mech.kuleuven.be/~orocos/pub/devel/examples/rtt/tutorial
>
> Other official code resources for 2.0 are my git repositories on github: rtt-
> examples, orocos-rtt and orocos-ocl. Check out the ocl-2.0-mainline and
> rtt-2.0-mainline code. I will not host 2.0 in an SVN repository.
When I checked out the git tree, this stupid svn moron was expecting
to be able to "switch" to the tag beta2, but it doesn't seem that
obvious
[kgad@ampere /tmp/orocos-rtt.git]$
hg tags
tip 4105:617d1cf0c940
rtt-2.0-remoting 4105:617d1cf0c940
rtt-2.0-mainline 4105:617d1cf0c940
default/rtt-2.0-remoting 4105:617d1cf0c940
default/rtt-2.0-mainline 4105:617d1cf0c940
rtt-2.0-services 4010:3364c9aa6d81
default/rtt-2.0-services 4010:3364c9aa6d81
rtt-1.0-svn-patches 3701:e37b737f8fde
default/rtt-1.0-svn-patches 3701:e37b737f8fde
master 3404:49eec276f822
default/master 3404:49eec276f822
default/arm-port 2839:ccc832e24e9b
arm-port 2839:ccc832e24e9b
Some git expert that has a tip (not a git tip, that is :-)?
Klaas
ps. Yes, I am using the mercurial-git bindings
RTT and OCL 2.0.0-beta2 Released
On Tuesday 13 April 2010 17:57:00 Klaas Gadeyne wrote:
> [...]
>
> > Where to find it ?
> >
> > There are tar balls and online docs available in the devel section of the
> > server kindly provided by the University of Leuven:
> >
> > http://people.mech.kuleuven.be/~orocos/pub/devel/rtt/v1.99.2/doc/api/html
> >/
> > http://people.mech.kuleuven.be/~orocos/pub/devel/rtt/v1.99.2/orocos-rtt-1
> >.99.2-src.tar.gz
> > http://people.mech.kuleuven.be/~orocos/pub/devel/ocl/v1.99.2/doc/api/html
> >/
> > http://people.mech.kuleuven.be/~orocos/pub/devel/ocl/v1.99.2/orocos-ocl-1
> >.99.2-src.tar.gz
> >
> > The exercises of beta1 still apply (1.99.1):
> > http://people.mech.kuleuven.be/~orocos/pub/devel/examples/rtt/tutorial
> >
> > Other official code resources for 2.0 are my git repositories on github:
> > rtt- examples, orocos-rtt and orocos-ocl. Check out the ocl-2.0-mainline
> > and rtt-2.0-mainline code. I will not host 2.0 in an SVN repository.
>
> When I checked out the git tree, this stupid svn moron was expecting
> to be able to "switch" to the tag beta2, but it doesn't seem that
> obvious
>
> [kgad@ampere /tmp/orocos-rtt.git]$
> hg tags
> tip 4105:617d1cf0c940
> rtt-2.0-remoting 4105:617d1cf0c940
> rtt-2.0-mainline 4105:617d1cf0c940
> default/rtt-2.0-remoting 4105:617d1cf0c940
> default/rtt-2.0-mainline 4105:617d1cf0c940
> rtt-2.0-services 4010:3364c9aa6d81
> default/rtt-2.0-services 4010:3364c9aa6d81
> rtt-1.0-svn-patches 3701:e37b737f8fde
> default/rtt-1.0-svn-patches 3701:e37b737f8fde
> master 3404:49eec276f822
> default/master 3404:49eec276f822
> default/arm-port 2839:ccc832e24e9b
> arm-port 2839:ccc832e24e9b
>
> Some git expert that has a tip (not a git tip, that is :-)?
>
> Klaas
>
> ps. Yes, I am using the mercurial-git bindings
I forgot to push my tags to the github server (have to figure this out). It's
rtt-2.0-mainline you need, of tree 864fcbdbca174d616ed7d11a4636626ff1efbd31
which is the tip of the rtt-2.0-mainline at this moment.
Peter
RTT and OCL 2.0.0-beta2 Released
On Apr 2, 2010, at 05:33 , Peter Soetens wrote:
> It's called beta, but it's closer to release candidate than its name
<sni
> What can you do to help ?
>
> - Test the conversion scripts and update the wiki or scripts if you find
> issues.
> - Update wiki pages, installation notes etc if you encounter inconsistencies.
> - Send patches against this codebase, preferably using a git repository.
> - Provide feedback on documentation or API changes.
Builds RTT under Koala with omniORB (w/ previously emailed pull request), except for one test case (I've no idea how to fix this one). Also, types_test is failing too.
Mac still fails with the previously posted problem re boost locks not working with timed_mutex in our Condition class.
Stephen