orocos_toolchain_ros for debian

On Wednesday 02 February 2011 18:47:48 Willy Lambert wrote:
> Hi,
>
> I am a "standard" orocos user and trying to become a "ros" orocos user.
> Therefore I built all from git but I had some problems with dependencies
> since I am on a Debian system. Here is my rosdep.yml :
>
> libreadline:
> ubuntu: libreadline-dev
> fedora: readline-devel
> debian: libreadline-dev
> omniorb:
> ubuntu: omniorb4 omniidl4 omniorb4-nameserver libomniorb4-1
> libomniorb4-dev libomnithread3-dev libomnithread3c2 debian: omniorb4
> omniidl4 omniorb4-nameserver libomniorb4-1 libomniorb4-dev
> libomnithread3-dev libomnithread3c2 gccxml:
> ubuntu: gccxml
> fedora: gccxml
> debian: gccxml
> antlr:
> fedora: antlr3-C antlr-C++
> ubuntu: antlr libantlr-dev
> debian: antlr libantlr-dev
> rubygems:
> fedora: rubygems
> ubuntu: rubygems1.8
> debian: rubygems1.8
> libxslt:
> fedora: libxslt-devel
> ubuntu: libxslt1-dev
> debian: libxslt1-dev
> ruby1.8-dev:
> ubuntu:
> '10.10': ruby1.8-dev libruby1.8
> '10.04': ruby1.8-dev libopenssl-ruby1.8
> '9.10': ruby1.8-dev libopenssl-ruby1.8
> '9.04': ruby1.8-dev libopenssl-ruby1.8
> '8.10': ruby1.8-dev libopenssl-ruby1.8
> '8.04': ruby1.8-dev libopenssl-ruby1.8
> fedora: ruby ruby-devel openssl-devel
> debian: ruby1.8-dev libruby1.8
>
>
> I would rather have send a patch but I do not really know how to do this (I
> am not used to open source processes)

If you used git you can easily create a patch with the 'git format-patch'
command.

>
> I don't know where to post this between Orocos or ROS mailing list. What
> would you suggest ?

Both are fine.

orocos_toolchain_ros for debian

2011/2/3 Ruben Smits <ruben [dot] smits [..] ...>

> On Wednesday 02 February 2011 18:47:48 Willy Lambert wrote:
> > Hi,
> >
> > I am a "standard" orocos user and trying to become a "ros" orocos user.
> > Therefore I built all from git but I had some problems with dependencies
> > since I am on a Debian system. Here is my rosdep.yml :
> >
> > libreadline:
> > ubuntu: libreadline-dev
> > fedora: readline-devel
> > debian: libreadline-dev
> > omniorb:
> > ubuntu: omniorb4 omniidl4 omniorb4-nameserver libomniorb4-1
> > libomniorb4-dev libomnithread3-dev libomnithread3c2 debian: omniorb4
> > omniidl4 omniorb4-nameserver libomniorb4-1 libomniorb4-dev
> > libomnithread3-dev libomnithread3c2 gccxml:
> > ubuntu: gccxml
> > fedora: gccxml
> > debian: gccxml
> > antlr:
> > fedora: antlr3-C antlr-C++
> > ubuntu: antlr libantlr-dev
> > debian: antlr libantlr-dev
> > rubygems:
> > fedora: rubygems
> > ubuntu: rubygems1.8
> > debian: rubygems1.8
> > libxslt:
> > fedora: libxslt-devel
> > ubuntu: libxslt1-dev
> > debian: libxslt1-dev
> > ruby1.8-dev:
> > ubuntu:
> > '10.10': ruby1.8-dev libruby1.8
> > '10.04': ruby1.8-dev libopenssl-ruby1.8
> > '9.10': ruby1.8-dev libopenssl-ruby1.8
> > '9.04': ruby1.8-dev libopenssl-ruby1.8
> > '8.10': ruby1.8-dev libopenssl-ruby1.8
> > '8.04': ruby1.8-dev libopenssl-ruby1.8
> > fedora: ruby ruby-devel openssl-devel
> > debian: ruby1.8-dev libruby1.8
> >
> >
> > I would rather have send a patch but I do not really know how to do this
> (I
> > am not used to open source processes)
>
> If you used git you can easily create a patch with the 'git format-patch'
> command.
>
> >
> > I don't know where to post this between Orocos or ROS mailing list. What
> > would you suggest ?
>
> Both are fine.
>

We using the command lines from
http://www.ros.org/wiki/orocos_toolchain_rosI have an error when
cloning the repository :

ard@ard-host-v5:/media/DD_data/home/ard/ros$ git clone
http://git.mech.kuleuven.be/robotics/orocos_toolchain_ros.git
Cloning into orocos_toolchain_ros...
error: inflate: data stream error (incorrect header check)

Is this normal ?
At the end it seems to have work properly as I have this in the folder (and
succeed a build yesterday) :

ard@ard-host-v5:/media/DD_data/home/ard/ros/orocos_toolchain_ros$ ls
CMakeLists.txt env.sh ocl rosdep.yaml rtt_exercises
rtt_ros_integration_example stack.xml utilmm
env.mk Makefile orogen rtt rtt_ros_integration
rtt_ros_integration_std_msgs typelib utilrb
ard@ard-host-v5:/media/DD_data/home/ard/ros/orocos_toolchain_ros$

orocos_toolchain_ros for debian

________________________________________
Van: orocos-users-bounces [..] ... [orocos-users-bounces [..] ...] namens Willy Lambert [lambert [dot] willy [..] ...]
Verzonden: donderdag 3 februari 2011 17:10
Aan: Ruben Smits
CC: orocos-users [..] ...; ros-users [..] ...
Onderwerp: Re: [Orocos-users] orocos_toolchain_ros for debian

2011/2/3 Ruben Smits <ruben [dot] smits [..] ...<mailto:ruben [dot] smits [..] ...>>
On Wednesday 02 February 2011 18:47:48 Willy Lambert wrote:
> Hi,
>
> I am a "standard" orocos user and trying to become a "ros" orocos user.
> Therefore I built all from git but I had some problems with dependencies
> since I am on a Debian system. Here is my rosdep.yml :
>
> libreadline:
> ubuntu: libreadline-dev
> fedora: readline-devel
> debian: libreadline-dev
> omniorb:
> ubuntu: omniorb4 omniidl4 omniorb4-nameserver libomniorb4-1
> libomniorb4-dev libomnithread3-dev libomnithread3c2 debian: omniorb4
> omniidl4 omniorb4-nameserver libomniorb4-1 libomniorb4-dev
> libomnithread3-dev libomnithread3c2 gccxml:
> ubuntu: gccxml
> fedora: gccxml
> debian: gccxml
> antlr:
> fedora: antlr3-C antlr-C++
> ubuntu: antlr libantlr-dev
> debian: antlr libantlr-dev
> rubygems:
> fedora: rubygems
> ubuntu: rubygems1.8
> debian: rubygems1.8
> libxslt:
> fedora: libxslt-devel
> ubuntu: libxslt1-dev
> debian: libxslt1-dev
> ruby1.8-dev:
> ubuntu:
> '10.10': ruby1.8-dev libruby1.8
> '10.04': ruby1.8-dev libopenssl-ruby1.8
> '9.10': ruby1.8-dev libopenssl-ruby1.8
> '9.04': ruby1.8-dev libopenssl-ruby1.8
> '8.10': ruby1.8-dev libopenssl-ruby1.8
> '8.04': ruby1.8-dev libopenssl-ruby1.8
> fedora: ruby ruby-devel openssl-devel
> debian: ruby1.8-dev libruby1.8
>
>
> I would rather have send a patch but I do not really know how to do this (I
> am not used to open source processes)

If you used git you can easily create a patch with the 'git format-patch'
command.

>
> I don't know where to post this between Orocos or ROS mailing list. What
> would you suggest ?

Both are fine.

We using the command lines from http://www.ros.org/wiki/orocos_toolchain_ros I have an error when cloning the repository :

ard@ard-host-v5:/media/DD_data/home/ard/ros$ git clone http://git.mech.kuleuven.be/robotics/orocos_toolchain_ros.git
Cloning into orocos_toolchain_ros...
error: inflate: data stream error (incorrect header check)

Is this normal ?
At the end it seems to have work properly as I have this in the folder (and succeed a build yesterday) :

ard@ard-host-v5:/media/DD_data/home/ard/ros/orocos_toolchain_ros$ ls
CMakeLists.txt env.sh ocl rosdep.yaml rtt_exercises rtt_ros_integration_example stack.xml utilmm
env.mk<http://env.mk> Makefile orogen rtt rtt_ros_integration rtt_ros_integration_std_msgs typelib utilrb
ard@ard-host-v5:/media/DD_data/home/ard/ros/orocos_toolchain_ros$

Same error here,

Tim

[ros-users] orocos_toolchain_ros for debian

2011/2/3 Willy Lambert <lambert [dot] willy [..] ...>:
>
>
> 2011/2/3 Ruben Smits <ruben [dot] smits [..] ...>
>>
>> On Wednesday 02 February 2011 18:47:48 Willy Lambert wrote:
>> > Hi,
>> >
>> > I am a "standard" orocos user and trying to become a "ros" orocos user.
>> > Therefore I built all from git but I had some problems with dependencies
>> > since I am on a Debian system. Here is my rosdep.yml :
>> >
>> > libreadline:
>> >   ubuntu: libreadline-dev
>> >   fedora: readline-devel
>> >   debian: libreadline-dev
>> > omniorb:
>> >   ubuntu: omniorb4 omniidl4 omniorb4-nameserver libomniorb4-1
>> > libomniorb4-dev libomnithread3-dev libomnithread3c2 debian: omniorb4
>> > omniidl4 omniorb4-nameserver libomniorb4-1 libomniorb4-dev
>> > libomnithread3-dev libomnithread3c2 gccxml:
>> >   ubuntu: gccxml
>> >   fedora: gccxml
>> >   debian: gccxml
>> > antlr:
>> >   fedora: antlr3-C antlr-C++
>> >   ubuntu: antlr libantlr-dev
>> >   debian: antlr libantlr-dev
>> > rubygems:
>> >   fedora: rubygems
>> >   ubuntu: rubygems1.8
>> >   debian: rubygems1.8
>> > libxslt:
>> >   fedora: libxslt-devel
>> >   ubuntu: libxslt1-dev
>> >   debian: libxslt1-dev
>> > ruby1.8-dev:
>> >   ubuntu:
>> >     '10.10': ruby1.8-dev libruby1.8
>> >     '10.04': ruby1.8-dev libopenssl-ruby1.8
>> >     '9.10': ruby1.8-dev libopenssl-ruby1.8
>> >     '9.04': ruby1.8-dev libopenssl-ruby1.8
>> >     '8.10': ruby1.8-dev libopenssl-ruby1.8
>> >     '8.04': ruby1.8-dev libopenssl-ruby1.8
>> >   fedora: ruby ruby-devel openssl-devel
>> >   debian: ruby1.8-dev libruby1.8
>> >
>> >
>> > I would rather have send a patch but I do not really know how to do this
>> > (I
>> > am not used to open source  processes)
>>
>> If you used git you can easily create a patch with the 'git format-patch'
>> command.
>>
>> >
>> > I don't know where to post this between Orocos or ROS mailing list. What
>> > would you suggest ?
>>
>> Both are fine.
>
> We using the command lines from http://www.ros.org/wiki/orocos_toolchain_ros
> I have an error when cloning the repository :
>
> ard@ard-host-v5:/media/DD_data/home/ard/ros$ git clone
> http://git.mech.kuleuven.be/robotics/orocos_toolchain_ros.git
> Cloning into orocos_toolchain_ros...
> error: inflate: data stream error (incorrect header check)
>
> Is this normal ?

I get the same error, but AFAIK it doesn't cause any further disfunctioning.

Steven

> At the end it seems to have work properly as I have this in the folder (and
> succeed a build yesterday) :
>
> ard@ard-host-v5:/media/DD_data/home/ard/ros/orocos_toolchain_ros$ ls
> CMakeLists.txt  env.sh    ocl     rosdep.yaml  rtt_exercises
> rtt_ros_integration_example   stack.xml  utilmm
> env.mk          Makefile  orogen  rtt          rtt_ros_integration
> rtt_ros_integration_std_msgs  typelib    utilrb
> ard@ard-host-v5:/media/DD_data/home/ard/ros/orocos_toolchain_ros$
>
>
>
> _______________________________________________
> ros-users mailing list
> ros-users [..] ...
> https://code.ros.org/mailman/listinfo/ros-users
>
>

[ros-users] orocos_toolchain_ros for debian

2011/2/3 Steven Bellens <steven [dot] bellens [..] ...>

> 2011/2/3 Willy Lambert <lambert [dot] willy [..] ...>:
> >
> >
> > 2011/2/3 Ruben Smits <ruben [dot] smits [..] ...>
> >>
> >> On Wednesday 02 February 2011 18:47:48 Willy Lambert wrote:
> >> > Hi,
> >> >
> >> > I am a "standard" orocos user and trying to become a "ros" orocos
> user.
> >> > Therefore I built all from git but I had some problems with
> dependencies
> >> > since I am on a Debian system. Here is my rosdep.yml :
> >> >
> >> > libreadline:
> >> > ubuntu: libreadline-dev
> >> > fedora: readline-devel
> >> > debian: libreadline-dev
> >> > omniorb:
> >> > ubuntu: omniorb4 omniidl4 omniorb4-nameserver libomniorb4-1
> >> > libomniorb4-dev libomnithread3-dev libomnithread3c2 debian: omniorb4
> >> > omniidl4 omniorb4-nameserver libomniorb4-1 libomniorb4-dev
> >> > libomnithread3-dev libomnithread3c2 gccxml:
> >> > ubuntu: gccxml
> >> > fedora: gccxml
> >> > debian: gccxml
> >> > antlr:
> >> > fedora: antlr3-C antlr-C++
> >> > ubuntu: antlr libantlr-dev
> >> > debian: antlr libantlr-dev
> >> > rubygems:
> >> > fedora: rubygems
> >> > ubuntu: rubygems1.8
> >> > debian: rubygems1.8
> >> > libxslt:
> >> > fedora: libxslt-devel
> >> > ubuntu: libxslt1-dev
> >> > debian: libxslt1-dev
> >> > ruby1.8-dev:
> >> > ubuntu:
> >> > '10.10': ruby1.8-dev libruby1.8
> >> > '10.04': ruby1.8-dev libopenssl-ruby1.8
> >> > '9.10': ruby1.8-dev libopenssl-ruby1.8
> >> > '9.04': ruby1.8-dev libopenssl-ruby1.8
> >> > '8.10': ruby1.8-dev libopenssl-ruby1.8
> >> > '8.04': ruby1.8-dev libopenssl-ruby1.8
> >> > fedora: ruby ruby-devel openssl-devel
> >> > debian: ruby1.8-dev libruby1.8
> >> >
> >> >
> >> > I would rather have send a patch but I do not really know how to do
> this
> >> > (I
> >> > am not used to open source processes)
> >>
> >> If you used git you can easily create a patch with the 'git
> format-patch'
> >> command.
> >>
> >> >
> >> > I don't know where to post this between Orocos or ROS mailing list.
> What
> >> > would you suggest ?
> >>
> >> Both are fine.
> >
> > We using the command lines from
> http://www.ros.org/wiki/orocos_toolchain_ros
> > I have an error when cloning the repository :
> >
> > ard@ard-host-v5:/media/DD_data/home/ard/ros$ git clone
> > http://git.mech.kuleuven.be/robotics/orocos_toolchain_ros.git
> > Cloning into orocos_toolchain_ros...
> > error: inflate: data stream error (incorrect header check)
> >
> > Is this normal ?
>
> I get the same error, but AFAIK it doesn't cause any further
> disfunctioning.
>
> Steven
>
>
it seems to miss the lua-dev dependency in the rosdem.yaml. Do you know this
Ruben ?

> > At the end it seems to have work properly as I have this in the folder
> (and
> > succeed a build yesterday) :
> >
> > ard@ard-host-v5:/media/DD_data/home/ard/ros/orocos_toolchain_ros$ ls
> > CMakeLists.txt env.sh ocl rosdep.yaml rtt_exercises
> > rtt_ros_integration_example stack.xml utilmm
> > env.mk Makefile orogen rtt rtt_ros_integration
> > rtt_ros_integration_std_msgs typelib utilrb
> > ard@ard-host-v5:/media/DD_data/home/ard/ros/orocos_toolchain_ros$
> >
> >
> >
> > _______________________________________________
> > ros-users mailing list
> > ros-users [..] ...
> > https://code.ros.org/mailman/listinfo/ros-users
> >
> >
> --
> Orocos-Users mailing list
> Orocos-Users [..] ...
> http://lists.mech.kuleuven.be/mailman/listinfo/orocos-users
>

[ros-users] orocos_toolchain_ros for debian

Hey Willy,

[...]
>
> it seems to miss the lua-dev dependency in the rosdem.yaml. Do you know this
> Ruben ?

Thanks for the patch. I've just applied it on master and merged master
with the orocos_toolchain_ros-0.2 branch. This should also resolve the
lua dependency, as it was not yet present on the master branch (but is
now after the merge).
Concerning the ROS warning about the invalid manifest file: this is a
known issue and will be solved with the next orocos release (they
don't have any further impact on your installation).
Let us know if you have any more problems.

regards,

Steven

>
>
>
>
>>
>> > At the end it seems to have work properly as I have this in the folder
>> > (and
>> > succeed a build yesterday) :
>> >
>> > ard@ard-host-v5:/media/DD_data/home/ard/ros/orocos_toolchain_ros$ ls
>> > CMakeLists.txt  env.sh    ocl     rosdep.yaml  rtt_exercises
>> > rtt_ros_integration_example   stack.xml  utilmm
>> > env.mk          Makefile  orogen  rtt          rtt_ros_integration
>> > rtt_ros_integration_std_msgs  typelib    utilrb
>> > ard@ard-host-v5:/media/DD_data/home/ard/ros/orocos_toolchain_ros$
>> >
>> >
>> >
>> > _______________________________________________
>> > ros-users mailing list
>> > ros-users [..] ...
>> > https://code.ros.org/mailman/listinfo/ros-users
>> >
>> >
>> --
>> Orocos-Users mailing list
>> Orocos-Users [..] ...
>> http://lists.mech.kuleuven.be/mailman/listinfo/orocos-users
>
>
> _______________________________________________
> ros-users mailing list
> ros-users [..] ...
> https://code.ros.org/mailman/listinfo/ros-users
>
>

[ros-users] orocos_toolchain_ros for debian

2011/2/4 Steven Bellens <steven [dot] bellens [..] ...>

> Hey Willy,
>
> [...]
> >
> > it seems to miss the lua-dev dependency in the rosdem.yaml. Do you know
> this
> > Ruben ?
>
> Thanks for the patch. I've just applied it on master and merged master
> with the orocos_toolchain_ros-0.2 branch. This should also resolve the
> lua dependency, as it was not yet present on the master branch (but is
> now after the merge).
> Concerning the ROS warning about the invalid manifest file: this is a
> known issue and will be solved with the next orocos release (they
> don't have any further impact on your installation).
> Let us know if you have any more problems.
>

I deleted my orocos_toolchain_ros and try from scratch a new installation
based on master branch (it means I didn't follow the wiki instructions :p)

I still have to play with submodules which is a pity I think but I can't
help with git I am too bad with it !

git clone http://git.mech.kuleuven.be/robotics/orocos_toolchain_ros.git

cd orocos_toolchain_ros
(!! no branching !!)
git submodule init
git submodule update --recursive

I appreciate the debian rosdep, but you forgot to add the one for lua-dev .
It is the same as ubuntu, I can provide a patch but for a copy paste line I
don't know if it worth it.

I suggest you add the --rosdep-install at the end of rosmake command line on
the wiki (or add a new command line for rosdep)

The rosdep step failed here :

[ rosmake ] rosdep install failed: QUITTING: due to conflicting rosdep
definitions, please resolve this conflict.
Rules for ruby do not match:
ruby [/home/ard/ros/ros/rosdep.yaml]
ruby1.8-dev libruby1.8 [/home/ard/ros/orocos_toolchain_ros/rosdep.yaml]

I don't have this if I use the unstable branch. I can't test on cturtle
branch because of this :
ard@ard-host-v5:~/ros/orocos_toolchain_ros$ git checkout -b cturtle
origin/cturtle
error: Untracked working tree file 'ocl/CMakeLists.txt' would be overwritten
by merge.

I to be honest I have enougth with git today to correct this :p

>
> regards,
>
> Steven
>
>
> >
> >
> >
> >
> >>
> >> > At the end it seems to have work properly as I have this in the folder
> >> > (and
> >> > succeed a build yesterday) :
> >> >
> >> > ard@ard-host-v5:/media/DD_data/home/ard/ros/orocos_toolchain_ros$ ls
> >> > CMakeLists.txt env.sh ocl rosdep.yaml rtt_exercises
> >> > rtt_ros_integration_example stack.xml utilmm
> >> > env.mk Makefile orogen rtt rtt_ros_integration
> >> > rtt_ros_integration_std_msgs typelib utilrb
> >> > ard@ard-host-v5:/media/DD_data/home/ard/ros/orocos_toolchain_ros$
> >> >
> >> >
> >> >
> >> > _______________________________________________
> >> > ros-users mailing list
> >> > ros-users [..] ...
> >> > https://code.ros.org/mailman/listinfo/ros-users
> >> >
> >> >
> >> --
> >> Orocos-Users mailing list
> >> Orocos-Users [..] ...
> >> http://lists.mech.kuleuven.be/mailman/listinfo/orocos-users
> >
> >
> > _______________________________________________
> > ros-users mailing list
> > ros-users [..] ...
> > https://code.ros.org/mailman/listinfo/ros-users
> >
> >
> _______________________________________________
> ros-users mailing list
> ros-users [..] ...
> https://code.ros.org/mailman/listinfo/ros-users
>

[ros-users] orocos_toolchain_ros for debian

2011/2/4 Willy Lambert <lambert [dot] willy [..] ...>:
>
>
> 2011/2/4 Steven Bellens <steven [dot] bellens [..] ...>
>>
>> Hey Willy,
>>
>> [...]
>> >
>> > it seems to miss the lua-dev dependency in the rosdem.yaml. Do you know
>> > this
>> > Ruben ?
>>
>> Thanks for the patch. I've just applied it on master and merged master
>> with the orocos_toolchain_ros-0.2 branch. This should also resolve the
>> lua dependency, as it was not yet present on the master branch (but is
>> now after the merge).
>> Concerning the ROS warning about the invalid manifest file: this is a
>> known issue and will be solved with the next orocos release (they
>> don't have any further impact on your installation).
>> Let us know if you have any more problems.
>
>
> I deleted my orocos_toolchain_ros and try from scratch a new installation
> based on master branch (it means I didn't follow the wiki instructions :p)
>
> I still have to play with submodules which is a pity I think but I can't
> help with git I am too bad with it !
>
> git clone http://git.mech.kuleuven.be/robotics/orocos_toolchain_ros.git
>
> cd orocos_toolchain_ros
> (!! no branching !!)
> git submodule init
> git submodule update --recursive
>
> I appreciate the debian rosdep, but you forgot to add the one for lua-dev .
> It is the same as ubuntu, I can provide a patch but for a copy paste line I
> don't know if it worth it.

Added.

>
> I suggest you add the --rosdep-install at the end of rosmake command line on
> the wiki (or add a new command line for rosdep)

The rosdep command is a basic ROS usage tool which users get familiar
with when then go through the online tutorials. We expect you to know
how to work with it :)

>
> The rosdep step failed here :
>
> [ rosmake ] rosdep install failed: QUITTING: due to conflicting rosdep
> definitions, please resolve this conflict.
> Rules for ruby do not match:
>     ruby [/home/ard/ros/ros/rosdep.yaml]
>     ruby1.8-dev libruby1.8 [/home/ard/ros/orocos_toolchain_ros/rosdep.yaml]
>
> I don't have this if I use the unstable branch. I can't test on cturtle
> branch because of this :
> ard@ard-host-v5:~/ros/orocos_toolchain_ros$ git checkout -b cturtle
> origin/cturtle
> error: Untracked working tree file 'ocl/CMakeLists.txt' would be overwritten
> by merge.

Are you sure your installation folder is really clean?
You can use 'git clean -fd' to remove all files in your folder which
are not on git (git help clean to get extra info)

>
> I to be honest I have enougth with git today to correct this :p
>
>>
>> regards,
>>
>> Steven
>>
>>
>> >
>> >
>> >
>> >
>> >>
>> >> > At the end it seems to have work properly as I have this in the
>> >> > folder
>> >> > (and
>> >> > succeed a build yesterday) :
>> >> >
>> >> > ard@ard-host-v5:/media/DD_data/home/ard/ros/orocos_toolchain_ros$ ls
>> >> > CMakeLists.txt  env.sh    ocl     rosdep.yaml  rtt_exercises
>> >> > rtt_ros_integration_example   stack.xml  utilmm
>> >> > env.mk          Makefile  orogen  rtt          rtt_ros_integration
>> >> > rtt_ros_integration_std_msgs  typelib    utilrb
>> >> > ard@ard-host-v5:/media/DD_data/home/ard/ros/orocos_toolchain_ros$
>> >> >
>> >> >
>> >> >
>> >> > _______________________________________________
>> >> > ros-users mailing list
>> >> > ros-users [..] ...
>> >> > https://code.ros.org/mailman/listinfo/ros-users
>> >> >
>> >> >
>> >> --
>> >> Orocos-Users mailing list
>> >> Orocos-Users [..] ...
>> >> http://lists.mech.kuleuven.be/mailman/listinfo/orocos-users
>> >
>> >
>> > _______________________________________________
>> > ros-users mailing list
>> > ros-users [..] ...
>> > https://code.ros.org/mailman/listinfo/ros-users
>> >
>> >
>> _______________________________________________
>> ros-users mailing list
>> ros-users [..] ...
>> https://code.ros.org/mailman/listinfo/ros-users
>
>
> _______________________________________________
> ros-users mailing list
> ros-users [..] ...
> https://code.ros.org/mailman/listinfo/ros-users
>
>

[ros-users] orocos_toolchain_ros for debian

2011/2/4 Willy Lambert <lambert [dot] willy [..] ...>

>
>
> 2011/2/4 Steven Bellens <steven [dot] bellens [..] ...>
>
> Hey Willy,
>>
>> [...]
>> >
>> > it seems to miss the lua-dev dependency in the rosdem.yaml. Do you know
>> this
>> > Ruben ?
>>
>> Thanks for the patch. I've just applied it on master and merged master
>> with the orocos_toolchain_ros-0.2 branch. This should also resolve the
>> lua dependency, as it was not yet present on the master branch (but is
>> now after the merge).
>> Concerning the ROS warning about the invalid manifest file: this is a
>> known issue and will be solved with the next orocos release (they
>> don't have any further impact on your installation).
>> Let us know if you have any more problems.
>>
>
>
> I deleted my orocos_toolchain_ros and try from scratch a new installation
> based on master branch (it means I didn't follow the wiki instructions :p)
>
> I still have to play with submodules which is a pity I think but I can't
> help with git I am too bad with it !
>
>
> git clone http://git.mech.kuleuven.be/robotics/orocos_toolchain_ros.git
>
> cd orocos_toolchain_ros
> (!! no branching !!)
> git submodule init
> git submodule update --recursive
>
>
> I appreciate the debian rosdep, but you forgot to add the one for lua-dev .
> It is the same as ubuntu, I can provide a patch but for a copy paste line I
> don't know if it worth it.
>
> I suggest you add the --rosdep-install at the end of rosmake command line
> on the wiki (or add a new command line for rosdep)
>
> The rosdep step failed here :
>
> [ rosmake ] rosdep install failed: QUITTING: due to conflicting rosdep
> definitions, please resolve this conflict.
> Rules for ruby do not match:
> ruby [/home/ard/ros/ros/rosdep.yaml]
> ruby1.8-dev libruby1.8 [/home/ard/ros/orocos_toolchain_ros/rosdep.yaml]
>
> I don't have this if I use the unstable branch. I can't test on cturtle
> branch because of this :
> ard@ard-host-v5:~/ros/orocos_toolchain_ros$ git checkout -b cturtle
> origin/cturtle
> error: Untracked working tree file 'ocl/CMakeLists.txt' would be
> overwritten by merge.
>
> I to be honest I have enougth with git today to correct this :p
>
>

Here is the output of the unstable branch compilation :
#No Packages to install
[ rosmake ] rosdep successfully installed all system
dependencies
[ rosmake ] Starting >>>
tools/rospack

[ rosmake ] Finished <<<
tools/rospack

[ rosmake ] Starting >>>
3rdparty/gtest

[ rosmake ] Finished <<<
3rdparty/gtest

[ rosmake ] Starting >>>
core/genmsg_cpp

[ rosmake ] Finished <<<
core/genmsg_cpp

[rosmake-0] Starting >>> log4cpp [ make
]

[rosmake-1] Starting >>> roslang [ make
]

[rosmake-1] Finished <<< roslang No Makefile in package
roslang
[rosmake-2] Starting >>> roslib [ make
]

[rosmake-3] Starting >>> xmlrpcpp [ make
]

[rosmake-1] Starting >>> rtt [ make
]

[rosmake-3] Finished <<< xmlrpcpp [PASS] [ 0.40 seconds
]
[rosmake-3] Starting >>> rosbuild [ make
]

[rosmake-3] Finished <<< rosbuild No Makefile in package
rosbuild
[rosmake-3] Starting >>> utilrb [ make
]

[rosmake-2] Finished <<< roslib [PASS] [ 1.70 seconds
]
[rosmake-2] Starting >>> rosconsole [ make
]

[ rosmake ] Output from build of package log4cpp written to: utilrb: 1.8 sec
] [ rosconsole: 0.5 ... [ 4 Active 6/45 Complete ]
[ rosmake ]
/home/ard/.ros/rosmake/rosmake_output-20110204-174116/log4cpp/build_output.log
[rosmake-0] Finished <<< log4cpp [PASS] [ 2.30 seconds ] -- WARNING: 1
compiler warnings
[rosmake-0] Starting >>> utilmm [ make
]

[rosmake-2] Finished <<< rosconsole [PASS] [ 1.12 seconds
]
[rosmake-2] Starting >>> roscpp [ make
]

[ rosmake ] Last 40 linest: 5.6 sec ] [ utilrb: 5.2 sec ] [ utilmm: 3.3 sec
] [ roscpp: 2.8 sec ] [ 4 Active 8/45 Complete ]
{-------------------------------------------------------------------------------
if [ ! -f utilmm.md5sum ]; then echo "Error: Couldn't find md5sum file
utilmm.md5sum" && false; fi
`rospack find rosbuild`/bin/download_checkmd5.py
http://people.mech.kuleuven.be/~sbellens/orocos-toolchain/orocos-toolcha...
`awk {'print $1'} utilmm.md5sum`
[rosbuild] Downloading
http://people.mech.kuleuven.be/~sbellens/orocos-toolchain/orocos-toolcha...
build/v2.1.0...Done
[rosbuild] Checking md5sum on build/v2.1.0
touch -c build/v2.1.0
rm -rf build/orocos-toolchain-utilmm
cd build; tar xzf ../build/v2.1.0
cd build/orocos-toolchain-utilmm && patch -p0 < ../../utilmm.patch;
patching file CMakeLists.txt
touch build/orocos-toolchain-utilmm/unpacked
mkdir -p bin
cd build && cmake -Wdev -DCMAKE_TOOLCHAIN_FILE=`rospack find
rosbuild`/rostoolchain.cmake -DCMAKE_INSTALL_PREFIX=`rospack find
utilmm`/install ..
-- The C compiler identification is GNU
-- The CXX compiler identification is GNU
-- Check for working C compiler: /usr/bin/gcc
-- Check for working C compiler: /usr/bin/gcc -- works
-- Detecting C compiler ABI info
-- Detecting C compiler ABI info - done
-- Check for working CXX compiler: /usr/bin/c++
-- Check for working CXX compiler: /usr/bin/c++ -- works
-- Detecting CXX compiler ABI info
-- Detecting CXX compiler ABI info - done
[rosbuild] Building package utilmm
[rosbuild] Cached build flags older than manifests; calling rospack to get
flags
[rosbuild] Including /home/ard/ros/ros/core/roscpp/cmake/roscpp.cmake
[rosbuild] Including /home/ard/ros/ros/core/rospy/cmake/rospy.cmake
[rosbuild] Including /home/ard/ros/ros/core/roslisp/cmake/roslisp.cmake
-- Found The Following Boost Libraries:
-- unit_test_framework
-- Boost Version: 1.42.0
-- cannot find boost/graph
CMake Error at build/orocos-toolchain-utilmm/cmake/FindBoost.cmake:367
(MESSAGE):
Boost and/or some required components not found. Please install the
Boost
libraries AND development packages
Call Stack (most recent call first):
build/orocos-toolchain-utilmm/CMakeLists.txt:9 (FIND_PACKAGE)

-- Configuring incomplete, errors occurred!
-------------------------------------------------------------------------------}
[ rosmake ] Output from build of package utilmm written to:
[ rosmake ]
/home/ard/.ros/rosmake/rosmake_output-20110204-174116/utilmm/build_output.log
[rosmake-0] Finished <<< utilmm [FAIL] [ 3.33 seconds
]
[ rosmake ] Halting due to failure in package utilmm.
[ rosmake ] Waiting for other threads to complete.
[rosmake-2] Finished <<< roscpp [PASS] [ 2.83 seconds
]
[ rosmake ] [ make ] [ rtt: 9.8 sec ] [ utilrb: 9.4 sec
] [ rosmake ] All 21 linestt: 41.3 sec ] [ utilrb:
4... [ 2 Active 9/45 Complete ]
{-------------------------------------------------------------------------------
gem install rake hoe rubyforge flexmock
ERROR: Error installing hoe:
hoe requires RubyGems version >= 1.4. Try 'gem update --system' to
update RubyGems itself.
Could not find main page README
Could not find main page README
Could not find main page README
Could not find main page README
Successfully installed rake-0.8.7
Successfully installed json_pure-1.5.1
Successfully installed rubyforge-2.0.4
Successfully installed flexmock-0.8.11
4 gems installed
Installing ri documentation for rake-0.8.7...
Installing ri documentation for json_pure-1.5.1...
Installing ri documentation for rubyforge-2.0.4...
Installing ri documentation for flexmock-0.8.11...
Installing RDoc documentation for rake-0.8.7...
Installing RDoc documentation for json_pure-1.5.1...
Installing RDoc documentation for rubyforge-2.0.4...
Installing RDoc documentation for flexmock-0.8.11...
-------------------------------------------------------------------------------}
[ rosmake ] Output from build of package utilrb written to:
[ rosmake ]
/home/ard/.ros/rosmake/rosmake_output-20110204-174116/utilrb/build_output.log
[rosmake-3] Finished <<< utilrb [FAIL] [ 40.97 seconds
]
[ rosmake ] Halting due to failure in package utilrb.
[ rosmake ] Waiting for other threads to complete.
[rosmake-1] Finished <<< rtt [PASS] [ 171.76 seconds
]
[ rosmake ]
Results:

[ rosmake ] Built 12 packages with 2
failures.

[ rosmake ] Summary output to
directory

[ rosmake ] /home/ard/.ros/rosmake/rosmake_output-20110204-174116

>
>> regards,
>>
>> Steven
>>
>>
>> >
>> >
>> >
>> >
>> >>
>> >> > At the end it seems to have work properly as I have this in the
>> folder
>> >> > (and
>> >> > succeed a build yesterday) :
>> >> >
>> >> > ard@ard-host-v5:/media/DD_data/home/ard/ros/orocos_toolchain_ros$ ls
>> >> > CMakeLists.txt env.sh ocl rosdep.yaml rtt_exercises
>> >> > rtt_ros_integration_example stack.xml utilmm
>> >> > env.mk Makefile orogen rtt rtt_ros_integration
>> >> > rtt_ros_integration_std_msgs typelib utilrb
>> >> > ard@ard-host-v5:/media/DD_data/home/ard/ros/orocos_toolchain_ros$
>> >> >
>> >> >
>> >> >
>> >> > _______________________________________________
>> >> > ros-users mailing list
>> >> > ros-users [..] ...
>> >> > https://code.ros.org/mailman/listinfo/ros-users
>> >> >
>> >> >
>> >> --
>> >> Orocos-Users mailing list
>> >> Orocos-Users [..] ...
>> >> http://lists.mech.kuleuven.be/mailman/listinfo/orocos-users
>> >
>> >
>> > _______________________________________________
>> > ros-users mailing list
>> > ros-users [..] ...
>> > https://code.ros.org/mailman/listinfo/ros-users
>> >
>> >
>> _______________________________________________
>> ros-users mailing list
>> ros-users [..] ...
>> https://code.ros.org/mailman/listinfo/ros-users
>>
>
>

[ros-users] orocos_toolchain_ros for debian

2011/2/4 Willy Lambert <lambert [dot] willy [..] ...>

>
>
> 2011/2/4 Willy Lambert <lambert [dot] willy [..] ...>
>
>
>>
>> 2011/2/4 Steven Bellens <steven [dot] bellens [..] ...>
>>
>> Hey Willy,
>>>
>>> [...]
>>> >
>>> > it seems to miss the lua-dev dependency in the rosdem.yaml. Do you know
>>> this
>>> > Ruben ?
>>>
>>> Thanks for the patch. I've just applied it on master and merged master
>>> with the orocos_toolchain_ros-0.2 branch. This should also resolve the
>>> lua dependency, as it was not yet present on the master branch (but is
>>> now after the merge).
>>> Concerning the ROS warning about the invalid manifest file: this is a
>>> known issue and will be solved with the next orocos release (they
>>> don't have any further impact on your installation).
>>> Let us know if you have any more problems.
>>>
>>
>>
>> I deleted my orocos_toolchain_ros and try from scratch a new installation
>> based on master branch (it means I didn't follow the wiki instructions :p)
>>
>> I still have to play with submodules which is a pity I think but I can't
>> help with git I am too bad with it !
>>
>>
>> git clone http://git.mech.kuleuven.be/robotics/orocos_toolchain_ros.git
>>
>> cd orocos_toolchain_ros
>> (!! no branching !!)
>> git submodule init
>> git submodule update --recursive
>>
>>
>> I appreciate the debian rosdep, but you forgot to add the one for lua-dev
>> . It is the same as ubuntu, I can provide a patch but for a copy paste line
>> I don't know if it worth it.
>>
>> I suggest you add the --rosdep-install at the end of rosmake command line
>> on the wiki (or add a new command line for rosdep)
>>
>> The rosdep step failed here :
>>
>> [ rosmake ] rosdep install failed: QUITTING: due to conflicting rosdep
>> definitions, please resolve this conflict.
>> Rules for ruby do not match:
>> ruby [/home/ard/ros/ros/rosdep.yaml]
>> ruby1.8-dev libruby1.8
>> [/home/ard/ros/orocos_toolchain_ros/rosdep.yaml]
>>
>> I don't have this if I use the unstable branch. I can't test on cturtle
>> branch because of this :
>> ard@ard-host-v5:~/ros/orocos_toolchain_ros$ git checkout -b cturtle
>> origin/cturtle
>> error: Untracked working tree file 'ocl/CMakeLists.txt' would be
>> overwritten by merge.
>>
>> I to be honest I have enougth with git today to correct this :p
>>
>>
>
> Here is the output of the unstable branch compilation :
> #No Packages to install
> [ rosmake ] rosdep successfully installed all system
> dependencies
> [ rosmake ] Starting >>>
> tools/rospack
>
> [ rosmake ] Finished <<<
> tools/rospack
>
> [ rosmake ] Starting >>>
> 3rdparty/gtest
>
> [ rosmake ] Finished <<<
> 3rdparty/gtest
>
> [ rosmake ] Starting >>>
> core/genmsg_cpp
>
> [ rosmake ] Finished <<<
> core/genmsg_cpp
>
> [rosmake-0] Starting >>> log4cpp [ make
> ]
>
> [rosmake-1] Starting >>> roslang [ make
> ]
>
> [rosmake-1] Finished <<< roslang No Makefile in package
> roslang
> [rosmake-2] Starting >>> roslib [ make
> ]
>
> [rosmake-3] Starting >>> xmlrpcpp [ make
> ]
>
> [rosmake-1] Starting >>> rtt [ make
> ]
>
> [rosmake-3] Finished <<< xmlrpcpp [PASS] [ 0.40 seconds
> ]
> [rosmake-3] Starting >>> rosbuild [ make
> ]
>
> [rosmake-3] Finished <<< rosbuild No Makefile in package
> rosbuild
> [rosmake-3] Starting >>> utilrb [ make
> ]
>
> [rosmake-2] Finished <<< roslib [PASS] [ 1.70 seconds
> ]
> [rosmake-2] Starting >>> rosconsole [ make
> ]
>
> [ rosmake ] Output from build of package log4cpp written to: utilrb: 1.8
> sec ] [ rosconsole: 0.5 ... [ 4 Active 6/45 Complete ]
> [ rosmake ]
> /home/ard/.ros/rosmake/rosmake_output-20110204-174116/log4cpp/build_output.log
> [rosmake-0] Finished <<< log4cpp [PASS] [ 2.30 seconds ] -- WARNING: 1
> compiler warnings
> [rosmake-0] Starting >>> utilmm [ make
> ]
>
> [rosmake-2] Finished <<< rosconsole [PASS] [ 1.12 seconds
> ]
> [rosmake-2] Starting >>> roscpp [ make
> ]
>
> [ rosmake ] Last 40 linest: 5.6 sec ] [ utilrb: 5.2 sec ] [ utilmm: 3.3 sec
> ] [ roscpp: 2.8 sec ] [ 4 Active 8/45 Complete ]
>
> {-------------------------------------------------------------------------------
> if [ ! -f utilmm.md5sum ]; then echo "Error: Couldn't find md5sum file
> utilmm.md5sum" && false; fi
> `rospack find rosbuild`/bin/download_checkmd5.py
> http://people.mech.kuleuven.be/~sbellens/orocos-toolchain/orocos-toolcha... `awk {'print $1'} utilmm.md5sum`
> [rosbuild] Downloading
> http://people.mech.kuleuven.be/~sbellens/orocos-toolchain/orocos-toolcha... build/v2.1.0...Done
> [rosbuild] Checking md5sum on build/v2.1.0
> touch -c build/v2.1.0
> rm -rf build/orocos-toolchain-utilmm
> cd build; tar xzf ../build/v2.1.0
> cd build/orocos-toolchain-utilmm && patch -p0 < ../../utilmm.patch;
> patching file CMakeLists.txt
> touch build/orocos-toolchain-utilmm/unpacked
>
> mkdir -p bin
> cd build && cmake -Wdev -DCMAKE_TOOLCHAIN_FILE=`rospack find
> rosbuild`/rostoolchain.cmake -DCMAKE_INSTALL_PREFIX=`rospack find
> utilmm`/install ..
> -- The C compiler identification is GNU
> -- The CXX compiler identification is GNU
> -- Check for working C compiler: /usr/bin/gcc
> -- Check for working C compiler: /usr/bin/gcc -- works
> -- Detecting C compiler ABI info
> -- Detecting C compiler ABI info - done
> -- Check for working CXX compiler: /usr/bin/c++
> -- Check for working CXX compiler: /usr/bin/c++ -- works
> -- Detecting CXX compiler ABI info
> -- Detecting CXX compiler ABI info - done
> [rosbuild] Building package utilmm
> [rosbuild] Cached build flags older than manifests; calling rospack to
> get flags
>
> [rosbuild] Including /home/ard/ros/ros/core/roscpp/cmake/roscpp.cmake
> [rosbuild] Including /home/ard/ros/ros/core/rospy/cmake/rospy.cmake
> [rosbuild] Including /home/ard/ros/ros/core/roslisp/cmake/roslisp.cmake
> -- Found The Following Boost Libraries:
> -- unit_test_framework
> -- Boost Version: 1.42.0
>
> -- cannot find boost/graph
> CMake Error at build/orocos-toolchain-utilmm/cmake/FindBoost.cmake:367
> (MESSAGE):
> Boost and/or some required components not found. Please install the
> Boost
> libraries AND development packages
> Call Stack (most recent call first):
> build/orocos-toolchain-utilmm/CMakeLists.txt:9 (FIND_PACKAGE)
>
>
> -- Configuring incomplete, errors occurred!
>
> -------------------------------------------------------------------------------}
> [ rosmake ] Output from build of package utilmm written to:
> [ rosmake ]
> /home/ard/.ros/rosmake/rosmake_output-20110204-174116/utilmm/build_output.log
> [rosmake-0] Finished <<< utilmm [FAIL] [ 3.33 seconds
> ]
> [ rosmake ] Halting due to failure in package utilmm.
> [ rosmake ] Waiting for other threads to complete.
> [rosmake-2] Finished <<< roscpp [PASS] [ 2.83 seconds
> ]
> [ rosmake ] [ make ] [ rtt: 9.8 sec ] [ utilrb: 9.4 sec
> ] [ rosmake ] All 21 linestt: 41.3 sec ] [ utilrb:
> 4... [ 2 Active 9/45 Complete ]
>
>
> {-------------------------------------------------------------------------------
> gem install rake hoe rubyforge flexmock
> ERROR: Error installing hoe:
> hoe requires RubyGems version >= 1.4. Try 'gem update --system' to
> update RubyGems itself.
> Could not find main page README
> Could not find main page README
> Could not find main page README
> Could not find main page README
> Successfully installed rake-0.8.7
> Successfully installed json_pure-1.5.1
>
> Successfully installed rubyforge-2.0.4
> Successfully installed flexmock-0.8.11
> 4 gems installed
> Installing ri documentation for rake-0.8.7...
> Installing ri documentation for json_pure-1.5.1...
>
> Installing ri documentation for rubyforge-2.0.4...
> Installing ri documentation for flexmock-0.8.11...
> Installing RDoc documentation for rake-0.8.7...
> Installing RDoc documentation for json_pure-1.5.1...
>
> Installing RDoc documentation for rubyforge-2.0.4...
> Installing RDoc documentation for flexmock-0.8.11...
>
> -------------------------------------------------------------------------------}
> [ rosmake ] Output from build of package utilrb written to:
> [ rosmake ]
> /home/ard/.ros/rosmake/rosmake_output-20110204-174116/utilrb/build_output.log
> [rosmake-3] Finished <<< utilrb [FAIL] [ 40.97 seconds
> ]
> [ rosmake ] Halting due to failure in package utilrb.
> [ rosmake ] Waiting for other threads to complete.
> [rosmake-1] Finished <<< rtt [PASS] [ 171.76 seconds
> ]
> [ rosmake ]
> Results:
>
> [ rosmake ] Built 12 packages with 2
> failures.
>
> [ rosmake ] Summary output to
> directory
>
> [ rosmake ] /home/ard/.ros/rosmake/rosmake_output-20110204-174116
>
> I forgot to precise I am in a Cturtle environnement, and the unstable
branch may not be compatible

>
>
>
>
>>
>>> regards,
>>>
>>> Steven
>>>
>>>
>>> >
>>> >
>>> >
>>> >
>>> >>
>>> >> > At the end it seems to have work properly as I have this in the
>>> folder
>>> >> > (and
>>> >> > succeed a build yesterday) :
>>> >> >
>>> >> > ard@ard-host-v5:/media/DD_data/home/ard/ros/orocos_toolchain_ros$
>>> ls
>>> >> > CMakeLists.txt env.sh ocl rosdep.yaml rtt_exercises
>>> >> > rtt_ros_integration_example stack.xml utilmm
>>> >> > env.mk Makefile orogen rtt rtt_ros_integration
>>> >> > rtt_ros_integration_std_msgs typelib utilrb
>>> >> > ard@ard-host-v5:/media/DD_data/home/ard/ros/orocos_toolchain_ros$
>>> >> >
>>> >> >
>>> >> >
>>> >> > _______________________________________________
>>> >> > ros-users mailing list
>>> >> > ros-users [..] ...
>>> >> > https://code.ros.org/mailman/listinfo/ros-users
>>> >> >
>>> >> >
>>> >> --
>>> >> Orocos-Users mailing list
>>> >> Orocos-Users [..] ...
>>> >> http://lists.mech.kuleuven.be/mailman/listinfo/orocos-users
>>> >
>>> >
>>> > _______________________________________________
>>> > ros-users mailing list
>>> > ros-users [..] ...
>>> > https://code.ros.org/mailman/listinfo/ros-users
>>> >
>>> >
>>> _______________________________________________
>>> ros-users mailing list
>>> ros-users [..] ...
>>> https://code.ros.org/mailman/listinfo/ros-users
>>>
>>
>>
>

[ros-users] orocos_toolchain_ros for debian

2011/2/4 Willy Lambert <lambert [dot] willy [..] ...>

>
>
> 2011/2/4 Willy Lambert <lambert [dot] willy [..] ...>
>
>>
>>
>> 2011/2/4 Willy Lambert <lambert [dot] willy [..] ...>
>>
>>
>>>
>>> 2011/2/4 Steven Bellens <steven [dot] bellens [..] ...>
>>>
>>> Hey Willy,
>>>>
>>>> [...]
>>>> >
>>>> > it seems to miss the lua-dev dependency in the rosdem.yaml. Do you
>>>> know this
>>>> > Ruben ?
>>>>
>>>> Thanks for the patch. I've just applied it on master and merged master
>>>> with the orocos_toolchain_ros-0.2 branch. This should also resolve the
>>>> lua dependency, as it was not yet present on the master branch (but is
>>>> now after the merge).
>>>> Concerning the ROS warning about the invalid manifest file: this is a
>>>> known issue and will be solved with the next orocos release (they
>>>> don't have any further impact on your installation).
>>>> Let us know if you have any more problems.
>>>>
>>>
>>>
>>> I deleted my orocos_toolchain_ros and try from scratch a new installation
>>> based on master branch (it means I didn't follow the wiki instructions :p)
>>>
>>> I still have to play with submodules which is a pity I think but I can't
>>> help with git I am too bad with it !
>>>
>>>
>>> git clone http://git.mech.kuleuven.be/robotics/orocos_toolchain_ros.git
>>>
>>> cd orocos_toolchain_ros
>>> (!! no branching !!)
>>> git submodule init
>>> git submodule update --recursive
>>>
>>>
>>> I appreciate the debian rosdep, but you forgot to add the one for lua-dev
>>> . It is the same as ubuntu, I can provide a patch but for a copy paste line
>>> I don't know if it worth it.
>>>
>>> I suggest you add the --rosdep-install at the end of rosmake command line
>>> on the wiki (or add a new command line for rosdep)
>>>
>>> The rosdep step failed here :
>>>
>>> [ rosmake ] rosdep install failed: QUITTING: due to conflicting rosdep
>>> definitions, please resolve this conflict.
>>> Rules for ruby do not match:
>>> ruby [/home/ard/ros/ros/rosdep.yaml]
>>> ruby1.8-dev libruby1.8
>>> [/home/ard/ros/orocos_toolchain_ros/rosdep.yaml]
>>>
>>> I don't have this if I use the unstable branch. I can't test on cturtle
>>> branch because of this :
>>> ard@ard-host-v5:~/ros/orocos_toolchain_ros$ git checkout -b cturtle
>>> origin/cturtle
>>> error: Untracked working tree file 'ocl/CMakeLists.txt' would be
>>> overwritten by merge.
>>>
>>> I to be honest I have enougth with git today to correct this :p
>>>
>>>
>>
>> Here is the output of the unstable branch compilation :
>> #No Packages to install
>> [ rosmake ] rosdep successfully installed all system
>> dependencies
>> [ rosmake ] Starting >>>
>> tools/rospack
>>
>> [ rosmake ] Finished <<<
>> tools/rospack
>>
>> [ rosmake ] Starting >>>
>> 3rdparty/gtest
>>
>> [ rosmake ] Finished <<<
>> 3rdparty/gtest
>>
>> [ rosmake ] Starting >>>
>> core/genmsg_cpp
>>
>> [ rosmake ] Finished <<<
>> core/genmsg_cpp
>>
>> [rosmake-0] Starting >>> log4cpp [ make
>> ]
>>
>> [rosmake-1] Starting >>> roslang [ make
>> ]
>>
>> [rosmake-1] Finished <<< roslang No Makefile in package
>> roslang
>> [rosmake-2] Starting >>> roslib [ make
>> ]
>>
>> [rosmake-3] Starting >>> xmlrpcpp [ make
>> ]
>>
>> [rosmake-1] Starting >>> rtt [ make
>> ]
>>
>> [rosmake-3] Finished <<< xmlrpcpp [PASS] [ 0.40 seconds
>> ]
>> [rosmake-3] Starting >>> rosbuild [ make
>> ]
>>
>> [rosmake-3] Finished <<< rosbuild No Makefile in package
>> rosbuild
>> [rosmake-3] Starting >>> utilrb [ make
>> ]
>>
>> [rosmake-2] Finished <<< roslib [PASS] [ 1.70 seconds
>> ]
>> [rosmake-2] Starting >>> rosconsole [ make
>> ]
>>
>> [ rosmake ] Output from build of package log4cpp written to: utilrb: 1.8
>> sec ] [ rosconsole: 0.5 ... [ 4 Active 6/45 Complete ]
>> [ rosmake ]
>> /home/ard/.ros/rosmake/rosmake_output-20110204-174116/log4cpp/build_output.log
>> [rosmake-0] Finished <<< log4cpp [PASS] [ 2.30 seconds ] -- WARNING: 1
>> compiler warnings
>> [rosmake-0] Starting >>> utilmm [ make
>> ]
>>
>> [rosmake-2] Finished <<< rosconsole [PASS] [ 1.12 seconds
>> ]
>> [rosmake-2] Starting >>> roscpp [ make
>> ]
>>
>> [ rosmake ] Last 40 linest: 5.6 sec ] [ utilrb: 5.2 sec ] [ utilmm: 3.3
>> sec ] [ roscpp: 2.8 sec ] [ 4 Active 8/45 Complete ]
>>
>> {-------------------------------------------------------------------------------
>> if [ ! -f utilmm.md5sum ]; then echo "Error: Couldn't find md5sum file
>> utilmm.md5sum" && false; fi
>> `rospack find rosbuild`/bin/download_checkmd5.py
>> http://people.mech.kuleuven.be/~sbellens/orocos-toolchain/orocos-toolcha... `awk {'print $1'} utilmm.md5sum`
>> [rosbuild] Downloading
>> http://people.mech.kuleuven.be/~sbellens/orocos-toolchain/orocos-toolcha... build/v2.1.0...Done
>> [rosbuild] Checking md5sum on build/v2.1.0
>> touch -c build/v2.1.0
>> rm -rf build/orocos-toolchain-utilmm
>> cd build; tar xzf ../build/v2.1.0
>> cd build/orocos-toolchain-utilmm && patch -p0 < ../../utilmm.patch;
>> patching file CMakeLists.txt
>> touch build/orocos-toolchain-utilmm/unpacked
>>
>> mkdir -p bin
>> cd build && cmake -Wdev -DCMAKE_TOOLCHAIN_FILE=`rospack find
>> rosbuild`/rostoolchain.cmake -DCMAKE_INSTALL_PREFIX=`rospack find
>> utilmm`/install ..
>> -- The C compiler identification is GNU
>> -- The CXX compiler identification is GNU
>> -- Check for working C compiler: /usr/bin/gcc
>> -- Check for working C compiler: /usr/bin/gcc -- works
>> -- Detecting C compiler ABI info
>> -- Detecting C compiler ABI info - done
>> -- Check for working CXX compiler: /usr/bin/c++
>> -- Check for working CXX compiler: /usr/bin/c++ -- works
>> -- Detecting CXX compiler ABI info
>> -- Detecting CXX compiler ABI info - done
>> [rosbuild] Building package utilmm
>> [rosbuild] Cached build flags older than manifests; calling rospack to
>> get flags
>>
>> [rosbuild] Including /home/ard/ros/ros/core/roscpp/cmake/roscpp.cmake
>> [rosbuild] Including /home/ard/ros/ros/core/rospy/cmake/rospy.cmake
>> [rosbuild] Including /home/ard/ros/ros/core/roslisp/cmake/roslisp.cmake
>> -- Found The Following Boost Libraries:
>> -- unit_test_framework
>> -- Boost Version: 1.42.0
>>
>> -- cannot find boost/graph
>> CMake Error at build/orocos-toolchain-utilmm/cmake/FindBoost.cmake:367
>> (MESSAGE):
>> Boost and/or some required components not found. Please install the
>> Boost
>> libraries AND development packages
>> Call Stack (most recent call first):
>> build/orocos-toolchain-utilmm/CMakeLists.txt:9 (FIND_PACKAGE)
>>
>>
>> -- Configuring incomplete, errors occurred!
>>
>> -------------------------------------------------------------------------------}
>> [ rosmake ] Output from build of package utilmm written to:
>> [ rosmake ]
>> /home/ard/.ros/rosmake/rosmake_output-20110204-174116/utilmm/build_output.log
>> [rosmake-0] Finished <<< utilmm [FAIL] [ 3.33 seconds
>> ]
>> [ rosmake ] Halting due to failure in package utilmm.
>> [ rosmake ] Waiting for other threads to complete.
>> [rosmake-2] Finished <<< roscpp [PASS] [ 2.83 seconds
>> ]
>> [ rosmake ] [ make ] [ rtt: 9.8 sec ] [ utilrb: 9.4 sec
>> ] [ rosmake ] All 21 linestt: 41.3 sec ] [ utilrb:
>> 4... [ 2 Active 9/45 Complete ]
>>
>>
>> {-------------------------------------------------------------------------------
>> gem install rake hoe rubyforge flexmock
>> ERROR: Error installing hoe:
>> hoe requires RubyGems version >= 1.4. Try 'gem update --system' to
>> update RubyGems itself.
>> Could not find main page README
>> Could not find main page README
>> Could not find main page README
>> Could not find main page README
>> Successfully installed rake-0.8.7
>> Successfully installed json_pure-1.5.1
>>
>> Successfully installed rubyforge-2.0.4
>> Successfully installed flexmock-0.8.11
>> 4 gems installed
>> Installing ri documentation for rake-0.8.7...
>> Installing ri documentation for json_pure-1.5.1...
>>
>> Installing ri documentation for rubyforge-2.0.4...
>> Installing ri documentation for flexmock-0.8.11...
>> Installing RDoc documentation for rake-0.8.7...
>> Installing RDoc documentation for json_pure-1.5.1...
>>
>> Installing RDoc documentation for rubyforge-2.0.4...
>> Installing RDoc documentation for flexmock-0.8.11...
>>
>> -------------------------------------------------------------------------------}
>> [ rosmake ] Output from build of package utilrb written to:
>> [ rosmake ]
>> /home/ard/.ros/rosmake/rosmake_output-20110204-174116/utilrb/build_output.log
>> [rosmake-3] Finished <<< utilrb [FAIL] [ 40.97 seconds
>> ]
>> [ rosmake ] Halting due to failure in package utilrb.
>> [ rosmake ] Waiting for other threads to complete.
>> [rosmake-1] Finished <<< rtt [PASS] [ 171.76 seconds
>> ]
>> [ rosmake ]
>> Results:
>>
>> [ rosmake ] Built 12 packages with 2
>> failures.
>>
>> [ rosmake ] Summary output to
>> directory
>>
>> [ rosmake ] /home/ard/.ros/rosmake/rosmake_output-20110204-174116
>>
>> I forgot to precise I am in a Cturtle environnement, and the unstable
> branch may not be compatible
>
>
>
Here is the outputs of the cturtle branch :
set -o errexit
#No Packages to install
[ rosmake ] rosdep successfully installed all system
dependencies
[ rosmake ] Starting >>>
tools/rospack

[ rosmake ] Finished <<<
tools/rospack

[ rosmake ] Starting >>>
3rdparty/gtest

[ rosmake ] Finished <<<
3rdparty/gtest

[ rosmake ] Starting >>>
core/genmsg_cpp

[ rosmake ] Finished <<<
core/genmsg_cpp

[rosmake-0] Starting >>> roslang [ make
]

[rosmake-0] Finished <<< roslang No Makefile in package
roslang
[rosmake-1] Starting >>> roslib [ make
]

[rosmake-0] Starting >>> xmlrpcpp [ make
]

[rosmake-0] Finished <<< xmlrpcpp [PASS] [ 0.39 seconds
]
[rosmake-0] Starting >>> rosbuild [ make
]

[rosmake-0] Finished <<< rosbuild No Makefile in package
rosbuild
[rosmake-0] Starting >>> rtt [ make
]

[rosmake-1] Finished <<< roslib [PASS] [ 0.94 seconds
]
[rosmake-1] Starting >>> rosconsole [ make
]

[rosmake-1] Finished <<< rosconsole [PASS] [ 0.67 seconds
]
[rosmake-1] Starting >>> roscpp [ make
]

[rosmake-1] Finished <<< roscpp [PASS] [ 1.72 seconds
]
[rosmake-1] Starting >>> std_msgs [ make
]

[rosmake-1] Finished <<< std_msgs [PASS] [ 5.76 seconds
]
[rosmake-1] Starting >>> utilrb [ make
]

[ rosmake ] All 18 linestt: 27.8 sec ] [ utilrb: 19.1 sec
] [ 2 Active 9/20 Complete ]
{-------------------------------------------------------------------------------
gem install rake hoe rubyforge flexmock
ERROR: Error installing hoe:
hoe requires RubyGems version >= 1.4. Try 'gem update --system' to
update RubyGems itself.
Could not find main page README
Could not find main page README
Could not find main page README
Could not find main page README
Successfully installed rake-0.8.7
Successfully installed rubyforge-2.0.4
Successfully installed flexmock-0.8.11
3 gems installed
Installing ri documentation for rake-0.8.7...
Installing ri documentation for rubyforge-2.0.4...
Installing ri documentation for flexmock-0.8.11...
Installing RDoc documentation for rake-0.8.7...
Installing RDoc documentation for rubyforge-2.0.4...
Installing RDoc documentation for flexmock-0.8.11...
-------------------------------------------------------------------------------}
[ rosmake ] Output from build of package utilrb written to:
[ rosmake ]
/home/ard/.ros/rosmake/rosmake_output-20110204-180841/utilrb/build_output.log
[rosmake-1] Finished <<< utilrb [FAIL] [ 19.09 seconds
]
[ rosmake ] Halting due to failure in package utilrb.
[ rosmake ] Waiting for other threads to complete.
[ rosmake ] Output from build of package rtt written
to: [ 1 Active 9/20 Complete ]
[ rosmake ]
/home/ard/.ros/rosmake/rosmake_output-20110204-180841/rtt/build_output.log
[rosmake-0] Finished <<< rtt [PASS] [ 139.80 seconds ] -- WARNING: 1
compiler warnings
[ rosmake ]
Results:

[ rosmake ] Built 11 packages with 1
failures.

[ rosmake ] Summary output to
directory

[ rosmake ]
/home/ard/.ros/rosmake/rosmake_output-20110204-180841

>
>
>
>>
>>
>>
>>
>>>
>>>> regards,
>>>>
>>>> Steven
>>>>
>>>>
>>>> >
>>>> >
>>>> >
>>>> >
>>>> >>
>>>> >> > At the end it seems to have work properly as I have this in the
>>>> folder
>>>> >> > (and
>>>> >> > succeed a build yesterday) :
>>>> >> >
>>>> >> > ard@ard-host-v5:/media/DD_data/home/ard/ros/orocos_toolchain_ros$
>>>> ls
>>>> >> > CMakeLists.txt env.sh ocl rosdep.yaml rtt_exercises
>>>> >> > rtt_ros_integration_example stack.xml utilmm
>>>> >> > env.mk Makefile orogen rtt rtt_ros_integration
>>>> >> > rtt_ros_integration_std_msgs typelib utilrb
>>>> >> > ard@ard-host-v5:/media/DD_data/home/ard/ros/orocos_toolchain_ros$
>>>> >> >
>>>> >> >
>>>> >> >
>>>> >> > _______________________________________________
>>>> >> > ros-users mailing list
>>>> >> > ros-users [..] ...
>>>> >> > https://code.ros.org/mailman/listinfo/ros-users
>>>> >> >
>>>> >> >
>>>> >> --
>>>> >> Orocos-Users mailing list
>>>> >> Orocos-Users [..] ...
>>>> >> http://lists.mech.kuleuven.be/mailman/listinfo/orocos-users
>>>> >
>>>> >
>>>> > _______________________________________________
>>>> > ros-users mailing list
>>>> > ros-users [..] ...
>>>> > https://code.ros.org/mailman/listinfo/ros-users
>>>> >
>>>> >
>>>> _______________________________________________
>>>> ros-users mailing list
>>>> ros-users [..] ...
>>>> https://code.ros.org/mailman/listinfo/ros-users
>>>>
>>>
>>>
>>
>

[ros-users] orocos_toolchain_ros for debian

2011/2/4 Willy Lambert <lambert [dot] willy [..] ...>:
>
>
> 2011/2/4 Willy Lambert <lambert [dot] willy [..] ...>
>>
>>
>> 2011/2/4 Willy Lambert <lambert [dot] willy [..] ...>
>>>
>>>
>>> 2011/2/4 Willy Lambert <lambert [dot] willy [..] ...>
>>>>
>>>>
>>>> 2011/2/4 Steven Bellens <steven [dot] bellens [..] ...>
>>>>>
>>>>> Hey Willy,
>>>>>
>>>>> [...]
>>>>> >
>>>>> > it seems to miss the lua-dev dependency in the rosdem.yaml. Do you
>>>>> > know this
>>>>> > Ruben ?
>>>>>
>>>>> Thanks for the patch. I've just applied it on master and merged master
>>>>> with the orocos_toolchain_ros-0.2 branch. This should also resolve the
>>>>> lua dependency, as it was not yet present on the master branch (but is
>>>>> now after the merge).
>>>>> Concerning the ROS warning about the invalid manifest file: this is a
>>>>> known issue and will be solved with the next orocos release (they
>>>>> don't have any further impact on your installation).
>>>>> Let us know if you have any more problems.
>>>>
>>>>
>>>> I deleted my orocos_toolchain_ros and try from scratch a new
>>>> installation based on master branch (it means I didn't follow the wiki
>>>> instructions :p)
>>>>
>>>> I still have to play with submodules which is a pity I think but I can't
>>>> help with git I am too bad with it !
>>>>
>>>> git clone http://git.mech.kuleuven.be/robotics/orocos_toolchain_ros.git
>>>>
>>>> cd orocos_toolchain_ros
>>>> (!! no branching !!)
>>>> git submodule init
>>>> git submodule update --recursive
>>>>
>>>> I appreciate the debian rosdep, but you forgot to add the one for
>>>> lua-dev . It is the same as ubuntu, I can provide a patch but for a copy
>>>> paste line I don't know if it worth it.
>>>>
>>>> I suggest you add the --rosdep-install at the end of rosmake command
>>>> line on the wiki (or add a new command line for rosdep)
>>>>
>>>> The rosdep step failed here :
>>>>
>>>> [ rosmake ] rosdep install failed: QUITTING: due to conflicting rosdep
>>>> definitions, please resolve this conflict.
>>>> Rules for ruby do not match:
>>>>     ruby [/home/ard/ros/ros/rosdep.yaml]
>>>>     ruby1.8-dev libruby1.8
>>>> [/home/ard/ros/orocos_toolchain_ros/rosdep.yaml]
>>>>
>>>> I don't have this if I use the unstable branch. I can't test on cturtle
>>>> branch because of this :
>>>> ard@ard-host-v5:~/ros/orocos_toolchain_ros$ git checkout -b cturtle
>>>> origin/cturtle
>>>> error: Untracked working tree file 'ocl/CMakeLists.txt' would be
>>>> overwritten by merge.
>>>>
>>>> I to be honest I have enougth with git today to correct this :p
>>>>
>>>
>>> Here is the output of the unstable branch compilation :
>>> #No Packages to install
>>> [ rosmake ] rosdep successfully installed all system
>>> dependencies
>>> [ rosmake ] Starting >>>
>>> tools/rospack
>>> [ rosmake ] Finished <<<
>>> tools/rospack
>>> [ rosmake ] Starting >>>
>>> 3rdparty/gtest
>>> [ rosmake ] Finished <<<
>>> 3rdparty/gtest
>>> [ rosmake ] Starting >>>
>>> core/genmsg_cpp
>>> [ rosmake ] Finished <<<
>>> core/genmsg_cpp
>>> [rosmake-0] Starting >>> log4cpp [ make
>>> ]
>>> [rosmake-1] Starting >>> roslang [ make
>>> ]
>>> [rosmake-1] Finished <<< roslang  No Makefile in package
>>> roslang
>>> [rosmake-2] Starting >>> roslib [ make
>>> ]
>>> [rosmake-3] Starting >>> xmlrpcpp [ make
>>> ]
>>> [rosmake-1] Starting >>> rtt [ make
>>> ]
>>> [rosmake-3] Finished <<< xmlrpcpp [PASS] [ 0.40 seconds
>>> ]
>>> [rosmake-3] Starting >>> rosbuild [ make
>>> ]
>>> [rosmake-3] Finished <<< rosbuild  No Makefile in package
>>> rosbuild
>>> [rosmake-3] Starting >>> utilrb [ make
>>> ]
>>> [rosmake-2] Finished <<< roslib [PASS] [ 1.70 seconds
>>> ]
>>> [rosmake-2] Starting >>> rosconsole [ make
>>> ]
>>> [ rosmake ] Output from build of package log4cpp written to: utilrb: 1.8
>>> sec ] [ rosconsole: 0.5 ... [ 4 Active 6/45 Complete ]
>>> [ rosmake ]
>>> /home/ard/.ros/rosmake/rosmake_output-20110204-174116/log4cpp/build_output.log
>>> [rosmake-0] Finished <<< log4cpp [PASS] [ 2.30 seconds ] -- WARNING: 1
>>> compiler warnings
>>> [rosmake-0] Starting >>> utilmm [ make
>>> ]
>>> [rosmake-2] Finished <<< rosconsole [PASS] [ 1.12 seconds
>>> ]
>>> [rosmake-2] Starting >>> roscpp [ make
>>> ]
>>> [ rosmake ] Last 40 linest: 5.6 sec ] [ utilrb: 5.2 sec ] [ utilmm: 3.3
>>> sec ] [ roscpp: 2.8 sec ]    [ 4 Active 8/45 Complete ]
>>>
>>> {-------------------------------------------------------------------------------
>>>   if [ ! -f utilmm.md5sum ]; then echo "Error: Couldn't find md5sum file
>>> utilmm.md5sum" && false; fi
>>>   `rospack find rosbuild`/bin/download_checkmd5.py
>>> http://people.mech.kuleuven.be/~sbellens/orocos-toolchain/orocos-toolcha...
>>> build/v2.1.0 `awk {'print $1'} utilmm.md5sum`
>>>   [rosbuild] Downloading
>>> http://people.mech.kuleuven.be/~sbellens/orocos-toolchain/orocos-toolcha...
>>> to build/v2.1.0...Done
>>>   [rosbuild] Checking md5sum on build/v2.1.0
>>>   touch -c build/v2.1.0
>>>   rm -rf build/orocos-toolchain-utilmm
>>>   cd build; tar xzf ../build/v2.1.0
>>>   cd build/orocos-toolchain-utilmm &&  patch -p0 < ../../utilmm.patch;
>>>   patching file CMakeLists.txt
>>>   touch build/orocos-toolchain-utilmm/unpacked
>>>   mkdir -p bin
>>>   cd build && cmake -Wdev -DCMAKE_TOOLCHAIN_FILE=`rospack find
>>> rosbuild`/rostoolchain.cmake -DCMAKE_INSTALL_PREFIX=`rospack find
>>> utilmm`/install ..
>>>   -- The C compiler identification is GNU
>>>   -- The CXX compiler identification is GNU
>>>   -- Check for working C compiler: /usr/bin/gcc
>>>   -- Check for working C compiler: /usr/bin/gcc -- works
>>>   -- Detecting C compiler ABI info
>>>   -- Detecting C compiler ABI info - done
>>>   -- Check for working CXX compiler: /usr/bin/c++
>>>   -- Check for working CXX compiler: /usr/bin/c++ -- works
>>>   -- Detecting CXX compiler ABI info
>>>   -- Detecting CXX compiler ABI info - done
>>>   [rosbuild] Building package utilmm
>>>   [rosbuild] Cached build flags older than manifests; calling rospack to
>>> get flags
>>>   [rosbuild] Including /home/ard/ros/ros/core/roscpp/cmake/roscpp.cmake
>>>   [rosbuild] Including /home/ard/ros/ros/core/rospy/cmake/rospy.cmake
>>>   [rosbuild] Including /home/ard/ros/ros/core/roslisp/cmake/roslisp.cmake
>>>   -- Found The Following Boost Libraries:
>>>   --   unit_test_framework
>>>   -- Boost Version: 1.42.0
>>>   -- cannot find boost/graph
>>>   CMake Error at build/orocos-toolchain-utilmm/cmake/FindBoost.cmake:367
>>> (MESSAGE):
>>>     Boost and/or some required components not found.  Please install the
>>> Boost
>>>     libraries AND development packages
>>>   Call Stack (most recent call first):
>>>     build/orocos-toolchain-utilmm/CMakeLists.txt:9 (FIND_PACKAGE)
>>>
>>>
>>>   -- Configuring incomplete, errors occurred!
>>>
>>> -------------------------------------------------------------------------------}
>>> [ rosmake ] Output from build of package utilmm written to:
>>> [ rosmake ]
>>> /home/ard/.ros/rosmake/rosmake_output-20110204-174116/utilmm/build_output.log
>>> [rosmake-0] Finished <<< utilmm [FAIL] [ 3.33 seconds
>>> ]
>>> [ rosmake ] Halting due to failure in package utilmm.
>>> [ rosmake ] Waiting for other threads to complete.
>>> [rosmake-2] Finished <<< roscpp [PASS] [ 2.83 seconds
>>> ]
>>> [ rosmake ] [ make ] [ rtt: 9.8 sec ] [ utilrb: 9.4 sec
>>> ]                       [ rosmake ] All 21 linestt: 41.3 sec ] [ utilrb:
>>> 4... [ 2 Active 9/45 Complete ]
>>>
>>> {-------------------------------------------------------------------------------
>>>   gem install rake hoe rubyforge flexmock
>>>   ERROR:  Error installing hoe:
>>>       hoe requires RubyGems version >= 1.4. Try 'gem update --system' to
>>> update RubyGems itself.
>>>   Could not find main page README
>>>   Could not find main page README
>>>   Could not find main page README
>>>   Could not find main page README
>>>   Successfully installed rake-0.8.7
>>>   Successfully installed json_pure-1.5.1
>>>   Successfully installed rubyforge-2.0.4
>>>   Successfully installed flexmock-0.8.11
>>>   4 gems installed
>>>   Installing ri documentation for rake-0.8.7...
>>>   Installing ri documentation for json_pure-1.5.1...
>>>   Installing ri documentation for rubyforge-2.0.4...
>>>   Installing ri documentation for flexmock-0.8.11...
>>>   Installing RDoc documentation for rake-0.8.7...
>>>   Installing RDoc documentation for json_pure-1.5.1...
>>>   Installing RDoc documentation for rubyforge-2.0.4...
>>>   Installing RDoc documentation for flexmock-0.8.11...
>>>
>>> -------------------------------------------------------------------------------}
>>> [ rosmake ] Output from build of package utilrb written to:
>>> [ rosmake ]
>>> /home/ard/.ros/rosmake/rosmake_output-20110204-174116/utilrb/build_output.log
>>> [rosmake-3] Finished <<< utilrb [FAIL] [ 40.97 seconds
>>> ]
>>> [ rosmake ] Halting due to failure in package utilrb.
>>> [ rosmake ] Waiting for other threads to complete.
>>> [rosmake-1] Finished <<< rtt [PASS] [ 171.76 seconds
>>> ]
>>> [ rosmake ]
>>> Results:
>>> [ rosmake ] Built 12 packages with 2
>>> failures.
>>> [ rosmake ] Summary output to
>>> directory
>>> [ rosmake ] /home/ard/.ros/rosmake/rosmake_output-20110204-174116
>>>
>> I forgot to precise I am in a Cturtle environnement, and the unstable
>> branch may not be compatible
>>
>>
>
> Here is the outputs of the cturtle branch :
> set -o errexit
> #No Packages to install
> [ rosmake ] rosdep successfully installed all system
> dependencies
> [ rosmake ] Starting >>>
> tools/rospack
> [ rosmake ] Finished <<<
> tools/rospack
> [ rosmake ] Starting >>>
> 3rdparty/gtest
> [ rosmake ] Finished <<<
> 3rdparty/gtest
> [ rosmake ] Starting >>>
> core/genmsg_cpp
> [ rosmake ] Finished <<<
> core/genmsg_cpp
> [rosmake-0] Starting >>> roslang [ make
> ]
> [rosmake-0] Finished <<< roslang  No Makefile in package
> roslang
> [rosmake-1] Starting >>> roslib [ make
> ]
> [rosmake-0] Starting >>> xmlrpcpp [ make
> ]
> [rosmake-0] Finished <<< xmlrpcpp [PASS] [ 0.39 seconds
> ]
> [rosmake-0] Starting >>> rosbuild [ make
> ]
> [rosmake-0] Finished <<< rosbuild  No Makefile in package
> rosbuild
> [rosmake-0] Starting >>> rtt [ make
> ]
> [rosmake-1] Finished <<< roslib [PASS] [ 0.94 seconds
> ]
> [rosmake-1] Starting >>> rosconsole [ make
> ]
> [rosmake-1] Finished <<< rosconsole [PASS] [ 0.67 seconds
> ]
> [rosmake-1] Starting >>> roscpp [ make
> ]
> [rosmake-1] Finished <<< roscpp [PASS] [ 1.72 seconds
> ]
> [rosmake-1] Starting >>> std_msgs [ make
> ]
> [rosmake-1] Finished <<< std_msgs [PASS] [ 5.76 seconds
> ]
> [rosmake-1] Starting >>> utilrb [ make
> ]
> [ rosmake ] All 18 linestt: 27.8 sec ] [ utilrb: 19.1 sec
> ]                                          [ 2 Active 9/20 Complete ]
> {-------------------------------------------------------------------------------
>   gem install rake hoe rubyforge flexmock
>   ERROR:  Error installing hoe:
>       hoe requires RubyGems version >= 1.4. Try 'gem update --system' to
> update RubyGems itself.
>   Could not find main page README
>   Could not find main page README
>   Could not find main page README
>   Could not find main page README
>   Successfully installed rake-0.8.7
>   Successfully installed rubyforge-2.0.4
>   Successfully installed flexmock-0.8.11
>   3 gems installed
>   Installing ri documentation for rake-0.8.7...
>   Installing ri documentation for rubyforge-2.0.4...
>   Installing ri documentation for flexmock-0.8.11...
>   Installing RDoc documentation for rake-0.8.7...
>   Installing RDoc documentation for rubyforge-2.0.4...
>   Installing RDoc documentation for flexmock-0.8.11...
> -------------------------------------------------------------------------------}
> [ rosmake ] Output from build of package utilrb written to:
> [ rosmake ]
> /home/ard/.ros/rosmake/rosmake_output-20110204-180841/utilrb/build_output.log
> [rosmake-1] Finished <<< utilrb [FAIL] [ 19.09 seconds
> ]
> [ rosmake ] Halting due to failure in package utilrb.
> [ rosmake ] Waiting for other threads to complete.
> [ rosmake ] Output from build of package rtt written
> to:                                             [ 1 Active 9/20 Complete ]
> [ rosmake ]
> /home/ard/.ros/rosmake/rosmake_output-20110204-180841/rtt/build_output.log
> [rosmake-0] Finished <<< rtt [PASS] [ 139.80 seconds ] -- WARNING: 1
> compiler warnings
> [ rosmake ]
> Results:
> [ rosmake ] Built 11 packages with 1
> failures.
> [ rosmake ] Summary output to
> directory
> [ rosmake ]
> /home/ard/.ros/rosmake/rosmake_output-20110204-180841

I've pushed a fixed for this to the orocos_toolchain_ros_0.2 branch.
Other branches will be updated when Ruben triggers a new release.

Steven

>
>
>
>>
>>
>>>
>>>
>>>>>
>>>>> regards,
>>>>>
>>>>> Steven
>>>>>
>>>>>
>>>>> >
>>>>> >
>>>>> >
>>>>> >
>>>>> >>
>>>>> >> > At the end it seems to have work properly as I have this in the
>>>>> >> > folder
>>>>> >> > (and
>>>>> >> > succeed a build yesterday) :
>>>>> >> >
>>>>> >> > ard@ard-host-v5:/media/DD_data/home/ard/ros/orocos_toolchain_ros$
>>>>> >> > ls
>>>>> >> > CMakeLists.txt  env.sh    ocl     rosdep.yaml  rtt_exercises
>>>>> >> > rtt_ros_integration_example   stack.xml  utilmm
>>>>> >> > env.mk          Makefile  orogen  rtt          rtt_ros_integration
>>>>> >> > rtt_ros_integration_std_msgs  typelib    utilrb
>>>>> >> > ard@ard-host-v5:/media/DD_data/home/ard/ros/orocos_toolchain_ros$
>>>>> >> >
>>>>> >> >
>>>>> >> >
>>>>> >> > _______________________________________________
>>>>> >> > ros-users mailing list
>>>>> >> > ros-users [..] ...
>>>>> >> > https://code.ros.org/mailman/listinfo/ros-users
>>>>> >> >
>>>>> >> >
>>>>> >> --
>>>>> >> Orocos-Users mailing list
>>>>> >> Orocos-Users [..] ...
>>>>> >> http://lists.mech.kuleuven.be/mailman/listinfo/orocos-users
>>>>> >
>>>>> >
>>>>> > _______________________________________________
>>>>> > ros-users mailing list
>>>>> > ros-users [..] ...
>>>>> > https://code.ros.org/mailman/listinfo/ros-users
>>>>> >
>>>>> >
>>>>> _______________________________________________
>>>>> ros-users mailing list
>>>>> ros-users [..] ...
>>>>> https://code.ros.org/mailman/listinfo/ros-users
>>>>
>>>
>>
>
>
> _______________________________________________
> ros-users mailing list
> ros-users [..] ...
> https://code.ros.org/mailman/listinfo/ros-users
>
>

[ros-users] orocos_toolchain_ros for debian

2011/2/7 Steven Bellens <steven [dot] bellens [..] ...>

> 2011/2/4 Willy Lambert <lambert [dot] willy [..] ...>:
> >
> >
> > 2011/2/4 Willy Lambert <lambert [dot] willy [..] ...>
> >>
> >>
> >> 2011/2/4 Willy Lambert <lambert [dot] willy [..] ...>
> >>>
> >>>
> >>> 2011/2/4 Willy Lambert <lambert [dot] willy [..] ...>
> >>>>
> >>>>
> >>>> 2011/2/4 Steven Bellens <steven [dot] bellens [..] ...>
> >>>>>
> >>>>> Hey Willy,
> >>>>>
> >>>>> [...]
> >>>>> >
> >>>>> > it seems to miss the lua-dev dependency in the rosdem.yaml. Do you
> >>>>> > know this
> >>>>> > Ruben ?
> >>>>>
> >>>>> Thanks for the patch. I've just applied it on master and merged
> master
> >>>>> with the orocos_toolchain_ros-0.2 branch. This should also resolve
> the
> >>>>> lua dependency, as it was not yet present on the master branch (but
> is
> >>>>> now after the merge).
> >>>>> Concerning the ROS warning about the invalid manifest file: this is a
> >>>>> known issue and will be solved with the next orocos release (they
> >>>>> don't have any further impact on your installation).
> >>>>> Let us know if you have any more problems.
> >>>>
> >>>>
> >>>> I deleted my orocos_toolchain_ros and try from scratch a new
> >>>> installation based on master branch (it means I didn't follow the wiki
> >>>> instructions :p)
> >>>>
> >>>> I still have to play with submodules which is a pity I think but I
> can't
> >>>> help with git I am too bad with it !
> >>>>
> >>>> git clone
> http://git.mech.kuleuven.be/robotics/orocos_toolchain_ros.git
> >>>>
> >>>> cd orocos_toolchain_ros
> >>>> (!! no branching !!)
> >>>> git submodule init
> >>>> git submodule update --recursive
> >>>>
> >>>> I appreciate the debian rosdep, but you forgot to add the one for
> >>>> lua-dev . It is the same as ubuntu, I can provide a patch but for a
> copy
> >>>> paste line I don't know if it worth it.
> >>>>
> >>>> I suggest you add the --rosdep-install at the end of rosmake command
> >>>> line on the wiki (or add a new command line for rosdep)
> >>>>
> >>>> The rosdep step failed here :
> >>>>
> >>>> [ rosmake ] rosdep install failed: QUITTING: due to conflicting rosdep
> >>>> definitions, please resolve this conflict.
> >>>> Rules for ruby do not match:
> >>>> ruby [/home/ard/ros/ros/rosdep.yaml]
> >>>> ruby1.8-dev libruby1.8
> >>>> [/home/ard/ros/orocos_toolchain_ros/rosdep.yaml]
> >>>>
> >>>> I don't have this if I use the unstable branch. I can't test on
> cturtle
> >>>> branch because of this :
> >>>> ard@ard-host-v5:~/ros/orocos_toolchain_ros$ git checkout -b cturtle
> >>>> origin/cturtle
> >>>> error: Untracked working tree file 'ocl/CMakeLists.txt' would be
> >>>> overwritten by merge.
> >>>>
> >>>> I to be honest I have enougth with git today to correct this :p
> >>>>
> >>>
> >>> Here is the output of the unstable branch compilation :
> >>> #No Packages to install
> >>> [ rosmake ] rosdep successfully installed all system
> >>> dependencies
> >>> [ rosmake ] Starting >>>
> >>> tools/rospack
> >>> [ rosmake ] Finished <<<
> >>> tools/rospack
> >>> [ rosmake ] Starting >>>
> >>> 3rdparty/gtest
> >>> [ rosmake ] Finished <<<
> >>> 3rdparty/gtest
> >>> [ rosmake ] Starting >>>
> >>> core/genmsg_cpp
> >>> [ rosmake ] Finished <<<
> >>> core/genmsg_cpp
> >>> [rosmake-0] Starting >>> log4cpp [ make
> >>> ]
> >>> [rosmake-1] Starting >>> roslang [ make
> >>> ]
> >>> [rosmake-1] Finished <<< roslang No Makefile in package
> >>> roslang
> >>> [rosmake-2] Starting >>> roslib [ make
> >>> ]
> >>> [rosmake-3] Starting >>> xmlrpcpp [ make
> >>> ]
> >>> [rosmake-1] Starting >>> rtt [ make
> >>> ]
> >>> [rosmake-3] Finished <<< xmlrpcpp [PASS] [ 0.40 seconds
> >>> ]
> >>> [rosmake-3] Starting >>> rosbuild [ make
> >>> ]
> >>> [rosmake-3] Finished <<< rosbuild No Makefile in package
> >>> rosbuild
> >>> [rosmake-3] Starting >>> utilrb [ make
> >>> ]
> >>> [rosmake-2] Finished <<< roslib [PASS] [ 1.70 seconds
> >>> ]
> >>> [rosmake-2] Starting >>> rosconsole [ make
> >>> ]
> >>> [ rosmake ] Output from build of package log4cpp written to: utilrb:
> 1.8
> >>> sec ] [ rosconsole: 0.5 ... [ 4 Active 6/45 Complete ]
> >>> [ rosmake ]
> >>>
> /home/ard/.ros/rosmake/rosmake_output-20110204-174116/log4cpp/build_output.log
> >>> [rosmake-0] Finished <<< log4cpp [PASS] [ 2.30 seconds ] -- WARNING: 1
> >>> compiler warnings
> >>> [rosmake-0] Starting >>> utilmm [ make
> >>> ]
> >>> [rosmake-2] Finished <<< rosconsole [PASS] [ 1.12 seconds
> >>> ]
> >>> [rosmake-2] Starting >>> roscpp [ make
> >>> ]
> >>> [ rosmake ] Last 40 linest: 5.6 sec ] [ utilrb: 5.2 sec ] [ utilmm: 3.3
> >>> sec ] [ roscpp: 2.8 sec ] [ 4 Active 8/45 Complete ]
> >>>
> >>>
> {-------------------------------------------------------------------------------
> >>> if [ ! -f utilmm.md5sum ]; then echo "Error: Couldn't find md5sum
> file
> >>> utilmm.md5sum" && false; fi
> >>> `rospack find rosbuild`/bin/download_checkmd5.py
> >>>
> http://people.mech.kuleuven.be/~sbellens/orocos-toolchain/orocos-toolcha...
> >>> build/v2.1.0 `awk {'print $1'} utilmm.md5sum`
> >>> [rosbuild] Downloading
> >>>
> http://people.mech.kuleuven.be/~sbellens/orocos-toolchain/orocos-toolcha...
> >>> to build/v2.1.0...Done
> >>> [rosbuild] Checking md5sum on build/v2.1.0
> >>> touch -c build/v2.1.0
> >>> rm -rf build/orocos-toolchain-utilmm
> >>> cd build; tar xzf ../build/v2.1.0
> >>> cd build/orocos-toolchain-utilmm && patch -p0 < ../../utilmm.patch;
> >>> patching file CMakeLists.txt
> >>> touch build/orocos-toolchain-utilmm/unpacked
> >>> mkdir -p bin
> >>> cd build && cmake -Wdev -DCMAKE_TOOLCHAIN_FILE=`rospack find
> >>> rosbuild`/rostoolchain.cmake -DCMAKE_INSTALL_PREFIX=`rospack find
> >>> utilmm`/install ..
> >>> -- The C compiler identification is GNU
> >>> -- The CXX compiler identification is GNU
> >>> -- Check for working C compiler: /usr/bin/gcc
> >>> -- Check for working C compiler: /usr/bin/gcc -- works
> >>> -- Detecting C compiler ABI info
> >>> -- Detecting C compiler ABI info - done
> >>> -- Check for working CXX compiler: /usr/bin/c++
> >>> -- Check for working CXX compiler: /usr/bin/c++ -- works
> >>> -- Detecting CXX compiler ABI info
> >>> -- Detecting CXX compiler ABI info - done
> >>> [rosbuild] Building package utilmm
> >>> [rosbuild] Cached build flags older than manifests; calling rospack
> to
> >>> get flags
> >>> [rosbuild] Including /home/ard/ros/ros/core/roscpp/cmake/roscpp.cmake
> >>> [rosbuild] Including /home/ard/ros/ros/core/rospy/cmake/rospy.cmake
> >>> [rosbuild] Including
> /home/ard/ros/ros/core/roslisp/cmake/roslisp.cmake
> >>> -- Found The Following Boost Libraries:
> >>> -- unit_test_framework
> >>> -- Boost Version: 1.42.0
> >>> -- cannot find boost/graph
> >>> CMake Error at
> build/orocos-toolchain-utilmm/cmake/FindBoost.cmake:367
> >>> (MESSAGE):
> >>> Boost and/or some required components not found. Please install
> the
> >>> Boost
> >>> libraries AND development packages
> >>> Call Stack (most recent call first):
> >>> build/orocos-toolchain-utilmm/CMakeLists.txt:9 (FIND_PACKAGE)
> >>>
> >>>
> >>> -- Configuring incomplete, errors occurred!
> >>>
> >>>
> -------------------------------------------------------------------------------}
> >>> [ rosmake ] Output from build of package utilmm written to:
> >>> [ rosmake ]
> >>>
> /home/ard/.ros/rosmake/rosmake_output-20110204-174116/utilmm/build_output.log
> >>> [rosmake-0] Finished <<< utilmm [FAIL] [ 3.33 seconds
> >>> ]
> >>> [ rosmake ] Halting due to failure in package utilmm.
> >>> [ rosmake ] Waiting for other threads to complete.
> >>> [rosmake-2] Finished <<< roscpp [PASS] [ 2.83 seconds
> >>> ]
> >>> [ rosmake ] [ make ] [ rtt: 9.8 sec ] [ utilrb: 9.4 sec
> >>> ] [ rosmake ] All 21 linestt: 41.3 sec ] [
> utilrb:
> >>> 4... [ 2 Active 9/45 Complete ]
> >>>
> >>>
> {-------------------------------------------------------------------------------
> >>> gem install rake hoe rubyforge flexmock
> >>> ERROR: Error installing hoe:
> >>> hoe requires RubyGems version >= 1.4. Try 'gem update --system'
> to
> >>> update RubyGems itself.
> >>> Could not find main page README
> >>> Could not find main page README
> >>> Could not find main page README
> >>> Could not find main page README
> >>> Successfully installed rake-0.8.7
> >>> Successfully installed json_pure-1.5.1
> >>> Successfully installed rubyforge-2.0.4
> >>> Successfully installed flexmock-0.8.11
> >>> 4 gems installed
> >>> Installing ri documentation for rake-0.8.7...
> >>> Installing ri documentation for json_pure-1.5.1...
> >>> Installing ri documentation for rubyforge-2.0.4...
> >>> Installing ri documentation for flexmock-0.8.11...
> >>> Installing RDoc documentation for rake-0.8.7...
> >>> Installing RDoc documentation for json_pure-1.5.1...
> >>> Installing RDoc documentation for rubyforge-2.0.4...
> >>> Installing RDoc documentation for flexmock-0.8.11...
> >>>
> >>>
> -------------------------------------------------------------------------------}
> >>> [ rosmake ] Output from build of package utilrb written to:
> >>> [ rosmake ]
> >>>
> /home/ard/.ros/rosmake/rosmake_output-20110204-174116/utilrb/build_output.log
> >>> [rosmake-3] Finished <<< utilrb [FAIL] [ 40.97 seconds
> >>> ]
> >>> [ rosmake ] Halting due to failure in package utilrb.
> >>> [ rosmake ] Waiting for other threads to complete.
> >>> [rosmake-1] Finished <<< rtt [PASS] [ 171.76 seconds
> >>> ]
> >>> [ rosmake ]
> >>> Results:
> >>> [ rosmake ] Built 12 packages with 2
> >>> failures.
> >>> [ rosmake ] Summary output to
> >>> directory
> >>> [ rosmake ] /home/ard/.ros/rosmake/rosmake_output-20110204-174116
> >>>
> >> I forgot to precise I am in a Cturtle environnement, and the unstable
> >> branch may not be compatible
> >>
> >>
> >
> > Here is the outputs of the cturtle branch :
> > set -o errexit
> > #No Packages to install
> > [ rosmake ] rosdep successfully installed all system
> > dependencies
> > [ rosmake ] Starting >>>
> > tools/rospack
> > [ rosmake ] Finished <<<
> > tools/rospack
> > [ rosmake ] Starting >>>
> > 3rdparty/gtest
> > [ rosmake ] Finished <<<
> > 3rdparty/gtest
> > [ rosmake ] Starting >>>
> > core/genmsg_cpp
> > [ rosmake ] Finished <<<
> > core/genmsg_cpp
> > [rosmake-0] Starting >>> roslang [ make
> > ]
> > [rosmake-0] Finished <<< roslang No Makefile in package
> > roslang
> > [rosmake-1] Starting >>> roslib [ make
> > ]
> > [rosmake-0] Starting >>> xmlrpcpp [ make
> > ]
> > [rosmake-0] Finished <<< xmlrpcpp [PASS] [ 0.39 seconds
> > ]
> > [rosmake-0] Starting >>> rosbuild [ make
> > ]
> > [rosmake-0] Finished <<< rosbuild No Makefile in package
> > rosbuild
> > [rosmake-0] Starting >>> rtt [ make
> > ]
> > [rosmake-1] Finished <<< roslib [PASS] [ 0.94 seconds
> > ]
> > [rosmake-1] Starting >>> rosconsole [ make
> > ]
> > [rosmake-1] Finished <<< rosconsole [PASS] [ 0.67 seconds
> > ]
> > [rosmake-1] Starting >>> roscpp [ make
> > ]
> > [rosmake-1] Finished <<< roscpp [PASS] [ 1.72 seconds
> > ]
> > [rosmake-1] Starting >>> std_msgs [ make
> > ]
> > [rosmake-1] Finished <<< std_msgs [PASS] [ 5.76 seconds
> > ]
> > [rosmake-1] Starting >>> utilrb [ make
> > ]
> > [ rosmake ] All 18 linestt: 27.8 sec ] [ utilrb: 19.1 sec
> > ] [ 2 Active 9/20 Complete ]
> >
> {-------------------------------------------------------------------------------
> > gem install rake hoe rubyforge flexmock
> > ERROR: Error installing hoe:
> > hoe requires RubyGems version >= 1.4. Try 'gem update --system' to
> > update RubyGems itself.
> > Could not find main page README
> > Could not find main page README
> > Could not find main page README
> > Could not find main page README
> > Successfully installed rake-0.8.7
> > Successfully installed rubyforge-2.0.4
> > Successfully installed flexmock-0.8.11
> > 3 gems installed
> > Installing ri documentation for rake-0.8.7...
> > Installing ri documentation for rubyforge-2.0.4...
> > Installing ri documentation for flexmock-0.8.11...
> > Installing RDoc documentation for rake-0.8.7...
> > Installing RDoc documentation for rubyforge-2.0.4...
> > Installing RDoc documentation for flexmock-0.8.11...
> >
> -------------------------------------------------------------------------------}
> > [ rosmake ] Output from build of package utilrb written to:
> > [ rosmake ]
> >
> /home/ard/.ros/rosmake/rosmake_output-20110204-180841/utilrb/build_output.log
> > [rosmake-1] Finished <<< utilrb [FAIL] [ 19.09 seconds
> > ]
> > [ rosmake ] Halting due to failure in package utilrb.
> > [ rosmake ] Waiting for other threads to complete.
> > [ rosmake ] Output from build of package rtt written
> > to: [ 1 Active 9/20 Complete
> ]
> > [ rosmake ]
> >
> /home/ard/.ros/rosmake/rosmake_output-20110204-180841/rtt/build_output.log
> > [rosmake-0] Finished <<< rtt [PASS] [ 139.80 seconds ] -- WARNING: 1
> > compiler warnings
> > [ rosmake ]
> > Results:
> > [ rosmake ] Built 11 packages with 1
> > failures.
> > [ rosmake ] Summary output to
> > directory
> > [ rosmake ]
> > /home/ard/.ros/rosmake/rosmake_output-20110204-180841
>
> I've pushed a fixed for this to the orocos_toolchain_ros_0.2 branch.
> Other branches will be updated when Ruben triggers a new release.
>

Ok thanks. I am a bit lost with versionning and compatibility.
May I have a proper install with cturtle or diamonback with the
orocos_toolchain_ros_0.2 ? Or should I only wait for next release (if so I
would be glad to have a goal of it, with no guarantee of course, but i'll
help my scheduling)

>
> Steven
>
> >
> >
> >
> >>
> >>
> >>>
> >>>
> >>>>>
> >>>>> regards,
> >>>>>
> >>>>> Steven
> >>>>>
> >>>>>
> >>>>> >
> >>>>> >
> >>>>> >
> >>>>> >
> >>>>> >>
> >>>>> >> > At the end it seems to have work properly as I have this in the
> >>>>> >> > folder
> >>>>> >> > (and
> >>>>> >> > succeed a build yesterday) :
> >>>>> >> >
> >>>>> >> > ard@ard-host-v5
> :/media/DD_data/home/ard/ros/orocos_toolchain_ros$
> >>>>> >> > ls
> >>>>> >> > CMakeLists.txt env.sh ocl rosdep.yaml rtt_exercises
> >>>>> >> > rtt_ros_integration_example stack.xml utilmm
> >>>>> >> > env.mk Makefile orogen rtt
> rtt_ros_integration
> >>>>> >> > rtt_ros_integration_std_msgs typelib utilrb
> >>>>> >> > ard@ard-host-v5
> :/media/DD_data/home/ard/ros/orocos_toolchain_ros$
> >>>>> >> >
> >>>>> >> >
> >>>>> >> >
> >>>>> >> > _______________________________________________
> >>>>> >> > ros-users mailing list
> >>>>> >> > ros-users [..] ...
> >>>>> >> > https://code.ros.org/mailman/listinfo/ros-users
> >>>>> >> >
> >>>>> >> >
> >>>>> >> --
> >>>>> >> Orocos-Users mailing list
> >>>>> >> Orocos-Users [..] ...
> >>>>> >> http://lists.mech.kuleuven.be/mailman/listinfo/orocos-users
> >>>>> >
> >>>>> >
> >>>>> > _______________________________________________
> >>>>> > ros-users mailing list
> >>>>> > ros-users [..] ...
> >>>>> > https://code.ros.org/mailman/listinfo/ros-users
> >>>>> >
> >>>>> >
> >>>>> _______________________________________________
> >>>>> ros-users mailing list
> >>>>> ros-users [..] ...
> >>>>> https://code.ros.org/mailman/listinfo/ros-users
> >>>>
> >>>
> >>
> >
> >
> > _______________________________________________
> > ros-users mailing list
> > ros-users [..] ...
> > https://code.ros.org/mailman/listinfo/ros-users
> >
> >
> --
> Orocos-Users mailing list
> Orocos-Users [..] ...
> http://lists.mech.kuleuven.be/mailman/listinfo/orocos-users
>

[ros-users] orocos_toolchain_ros for debian

[...]

>>
>> I've pushed a fixed for this to the orocos_toolchain_ros_0.2 branch.
>> Other branches will be updated when Ruben triggers a new release.
>
> Ok thanks. I am a bit lost with versionning and compatibility.
> May I have a proper install with cturtle or diamonback with the
> orocos_toolchain_ros_0.2  ? Or should I only wait for next release (if so I
> would be glad to have a goal of it, with no guarantee of course, but i'll
> help my scheduling)

Ruben did a new release of the orocos_toolchain_ros packages this
morning. It will take some time before the software is available, as
it needs to pass some tests on the ROS build farm first. It then
should be available for installation when a new release is triggered
at willowgarage (no idea when this will be).

In the meantime you can of course work on the git repositories. We're
deleting the orocos_toolchain_ros_0.2 branch and continue development
on master (as they both serve the same purpose anyway). This
development is diamondback based. If you work with cturtle - use the
cturtle_next branch.

regards,

Steven

>
>
>>
>> Steven
>>
>> >
>> >
>> >
>> >>
>> >>
>> >>>
>> >>>
>> >>>>>
>> >>>>> regards,
>> >>>>>
>> >>>>> Steven
>> >>>>>
>> >>>>>
>> >>>>> >
>> >>>>> >
>> >>>>> >
>> >>>>> >
>> >>>>> >>
>> >>>>> >> > At the end it seems to have work properly as I have this in the
>> >>>>> >> > folder
>> >>>>> >> > (and
>> >>>>> >> > succeed a build yesterday) :
>> >>>>> >> >
>> >>>>> >> >
>> >>>>> >> > ard@ard-host-v5:/media/DD_data/home/ard/ros/orocos_toolchain_ros$
>> >>>>> >> > ls
>> >>>>> >> > CMakeLists.txt  env.sh    ocl     rosdep.yaml  rtt_exercises
>> >>>>> >> > rtt_ros_integration_example   stack.xml  utilmm
>> >>>>> >> > env.mk          Makefile  orogen  rtt
>> >>>>> >> > rtt_ros_integration
>> >>>>> >> > rtt_ros_integration_std_msgs  typelib    utilrb
>> >>>>> >> >
>> >>>>> >> > ard@ard-host-v5:/media/DD_data/home/ard/ros/orocos_toolchain_ros$
>> >>>>> >> >
>> >>>>> >> >
>> >>>>> >> >
>> >>>>> >> > _______________________________________________
>> >>>>> >> > ros-users mailing list
>> >>>>> >> > ros-users [..] ...
>> >>>>> >> > https://code.ros.org/mailman/listinfo/ros-users
>> >>>>> >> >
>> >>>>> >> >
>> >>>>> >> --
>> >>>>> >> Orocos-Users mailing list
>> >>>>> >> Orocos-Users [..] ...
>> >>>>> >> http://lists.mech.kuleuven.be/mailman/listinfo/orocos-users
>> >>>>> >
>> >>>>> >
>> >>>>> > _______________________________________________
>> >>>>> > ros-users mailing list
>> >>>>> > ros-users [..] ...
>> >>>>> > https://code.ros.org/mailman/listinfo/ros-users
>> >>>>> >
>> >>>>> >
>> >>>>> _______________________________________________
>> >>>>> ros-users mailing list
>> >>>>> ros-users [..] ...
>> >>>>> https://code.ros.org/mailman/listinfo/ros-users
>> >>>>
>> >>>
>> >>
>> >
>> >
>> > _______________________________________________
>> > ros-users mailing list
>> > ros-users [..] ...
>> > https://code.ros.org/mailman/listinfo/ros-users
>> >
>> >
>> --
>> Orocos-Users mailing list
>> Orocos-Users [..] ...
>> http://lists.mech.kuleuven.be/mailman/listinfo/orocos-users
>
>
> _______________________________________________
> ros-users mailing list
> ros-users [..] ...
> https://code.ros.org/mailman/listinfo/ros-users
>
>

[ros-users] orocos_toolchain_ros for debian

2011/2/7 Steven Bellens <steven [dot] bellens [..] ...>

> [...]
>
> >>
> >> I've pushed a fixed for this to the orocos_toolchain_ros_0.2 branch.
> >> Other branches will be updated when Ruben triggers a new release.
> >
> > Ok thanks. I am a bit lost with versionning and compatibility.
> > May I have a proper install with cturtle or diamonback with the
> > orocos_toolchain_ros_0.2 ? Or should I only wait for next release (if so
> I
> > would be glad to have a goal of it, with no guarantee of course, but i'll
> > help my scheduling)
>
> Ruben did a new release of the orocos_toolchain_ros packages this
> morning. It will take some time before the software is available, as
> it needs to pass some tests on the ROS build farm first. It then
> should be available for installation when a new release is triggered
> at willowgarage (no idea when this will be).
>
> In the meantime you can of course work on the git repositories. We're
> deleting the orocos_toolchain_ros_0.2 branch and continue development
> on master (as they both serve the same purpose anyway). This
> development is diamondback based. If you work with cturtle - use the
> cturtle_next branch.
>
>
as diamondback is still not installing properly on my pc I can't test it.

In my cturtle installation I used the cturtle_next as you suggested, from
scratch (so no git problem), using
http://www.ros.org/wiki/orocos_toolchain_ros
and "cturtle_next" instead of cturtle

but it is still not ok :

ard@ard-host-v5:~/ros$* rosdep install orocos_toolchain_ros*
Invalid manifest
file[/home/ard/ros/orocos_toolchain_ros/rtt_exercises/rtt-exercises/hello-7-deployment/manifest.xml]:
missing required 'license' element
........... and so many others
ERROR: QUITTING: due to conflicting rosdep definitions, please resolve this
conflict.
Rules for ruby do not match:
ruby [/home/ard/ros/ros/rosdep.yaml]
ruby1.8-dev libruby1.8 [/home/ard/ros/orocos_toolchain_ros/rosdep.yaml]
ard@ard-host-v5:~/ros$

ard@ard-host-v5:~/ros/orocos_toolchain_ros$* rosmake*
[ rosmake ] No package specified. Building stack
['orocos_toolchain_ros']

[ rosmake ] Packages requested are:
['orocos_toolchain_ros']

[ rosmake ] Logging to
directory/home/ard/.ros/rosmake/rosmake_output-20110207-210422

[ rosmake ] Expanded args ['orocos_toolchain_ros'] to:
['log4cpp', 'rtt_ros_integration_example', 'ocl', 'utilrb', 'typelib',
'rtt', 'hello-7-deployment', 'helloworld', 'hello-2-properties',
'hello-5-services', 'controller-1', 'hello-3-dataports',
'hello-6-scripting', 'hello-1-task-execution', 'hello-4-operations',
'utilmm', 'orogen', 'rtt_ros_integration_nav_msgs', 'rtt_ros_integration',
'rtt_ros_param', 'rtt_ros_integration_geometry_msgs',
'rtt_ros_integration_roslib_msgs', 'rtt_ros_integration_std_msgs']
[ rosmake ] Checking rosdeps compliance for packages orocos_toolchain_ros.
This may take a few
seconds.

Invalid manifest
file[/home/ard/ros/orocos_toolchain_ros/rtt_exercises/rtt-exercises/hello-7-deployment/manifest.xml]:
missing required 'license' element
..................... and so many other
QUITTING: due to conflicting rosdep definitions, please resolve this
conflict.
Rules for ruby do not match:
ruby [/home/ard/ros/ros/rosdep.yaml]
ruby1.8-dev libruby1.8 [/home/ard/ros/orocos_toolchain_ros/rosdep.yaml]
[ rosmake ] rosdep check passed all system dependencies in
packages

[ rosmake ] Starting >>>
tools/rospack

[ rosmake ] Finished <<<
tools/rospack

[ rosmake ] Starting >>>
3rdparty/gtest

[ rosmake ] Finished <<<
3rdparty/gtest

[ rosmake ] Starting >>>
core/genmsg_cpp

[ rosmake ] Finished <<<
core/genmsg_cpp

[rosmake-0] Starting >>> log4cpp [ make
]

[rosmake-1] Starting >>> roslang [ make
]

[rosmake-1] Finished <<< roslang No Makefile in package
roslang

[rosmake-1] Starting >>> roslib [ make
]

[rosmake-1] Finished <<< roslib [PASS] [ 0.91 seconds
]

[rosmake-1] Starting >>> xmlrpcpp [ make
]

[rosmake-1] Finished <<< xmlrpcpp [PASS] [ 0.37 seconds
]

[rosmake-1] Starting >>> rosconsole [ make
]

[rosmake-1] Finished <<< rosconsole [PASS] [ 0.69 seconds
]

[rosmake-1] Starting >>> roscpp [ make
]

[rosmake-1] Finished <<< roscpp [PASS] [ 1.30 seconds
]

[rosmake-1] Starting >>> rtt [ make
]

[ rosmake ] Output from build of package log4cpp written
to:
[ 2 Active 7/45 Complete ]
[ rosmake ]
/home/ard/.ros/rosmake/rosmake_output-20110207-210422/log4cpp/build_output.log

[rosmake-0] Finished <<< log4cpp [PASS] [ 56.40 seconds ] -- WARNING: 1
compiler
warnings

[rosmake-0] Starting >>> rosbuild [ make
]

[rosmake-0] Finished <<< rosbuild No Makefile in package
rosbuild

[rosmake-0] Starting >>> std_msgs [ make
]

[rosmake-0] Finished <<< std_msgs [PASS] [ 5.61 seconds
]

[rosmake-0] Starting >>> utilrb [ make
]

[ rosmake ] Output from build of package utilrb written
to:]
[ 2 Active 10/45 Complete ]
[ rosmake ]
/home/ard/.ros/rosmake/rosmake_output-20110207-210422/utilrb/build_output.log

[rosmake-0] Finished <<< utilrb [PASS] [ 49.13 seconds ] -- WARNING: 1
compiler
warnings

[rosmake-0] Starting >>> utilmm [ make
]

[ rosmake ] Last 40 linest: 110.4 sec ] [ utilmm: 2.5 sec
]
[ 2 Active 11/45 Complete ]
{-------------------------------------------------------------------------------
if [ ! -f utilmm.md5sum ]; then echo "Error: Couldn't find md5sum file
utilmm.md5sum" && false; fi
`rospack find rosbuild`/bin/download_checkmd5.py
http://people.mech.kuleuven.be/~sbellens/orocos-toolchain/orocos-toolcha...
`awk {'print $1'} utilmm.md5sum`
[rosbuild] Downloading
http://people.mech.kuleuven.be/~sbellens/orocos-toolchain/orocos-toolcha...
build/v2.1.0...Done
[rosbuild] Checking md5sum on build/v2.1.0
touch -c build/v2.1.0
rm -rf build/orocos-toolchain-utilmm
cd build; tar xzf ../build/v2.1.0
cd build/orocos-toolchain-utilmm && patch -p0 < ../../utilmm.patch;
patching file CMakeLists.txt
touch build/orocos-toolchain-utilmm/unpacked
mkdir -p bin
cd build && cmake -Wdev -DCMAKE_TOOLCHAIN_FILE=`rospack find
rosbuild`/rostoolchain.cmake -DCMAKE_INSTALL_PREFIX=`rospack find
utilmm`/install ..
-- The C compiler identification is GNU
-- The CXX compiler identification is GNU
-- Check for working C compiler: /usr/bin/gcc
-- Check for working C compiler: /usr/bin/gcc -- works
-- Detecting C compiler ABI info
-- Detecting C compiler ABI info - done
-- Check for working CXX compiler: /usr/bin/c++
-- Check for working CXX compiler: /usr/bin/c++ -- works
-- Detecting CXX compiler ABI info
-- Detecting CXX compiler ABI info - done
[rosbuild] Building package utilmm
[rosbuild] Cached build flags older than manifests; calling rospack to get
flags
[rosbuild] Including /home/ard/ros/ros/core/roscpp/cmake/roscpp.cmake
[rosbuild] Including /home/ard/ros/ros/core/rospy/cmake/rospy.cmake
[rosbuild] Including /home/ard/ros/ros/core/roslisp/cmake/roslisp.cmake
-- Found The Following Boost Libraries:
-- unit_test_framework
-- Boost Version: 1.42.0
-- cannot find boost/graph
CMake Error at build/orocos-toolchain-utilmm/cmake/FindBoost.cmake:367
(MESSAGE):
Boost and/or some required components not found. Please install the
Boost
libraries AND development packages
Call Stack (most recent call first):
build/orocos-toolchain-utilmm/CMakeLists.txt:9 (FIND_PACKAGE)

-- Configuring incomplete, errors occurred!
-------------------------------------------------------------------------------}
[ rosmake ] Output from build of package utilmm written to:
[ rosmake ]
/home/ard/.ros/rosmake/rosmake_output-20110207-210422/utilmm/build_output.log

[rosmake-0] Finished <<< utilmm [FAIL] [ 2.55 seconds
]

[ rosmake ] Halting due to failure in package utilmm.
[ rosmake ] Waiting for other threads to
complete.

[rosmake-1] Finished <<< rtt [PASS] [ 262.82 seconds
]

[ rosmake ]
Results:

[ rosmake ] Built 13 packages with 1
failures.

[ rosmake ] Summary output to
directory

[ rosmake ]
/home/ard/.ros/rosmake/rosmake_output-20110207-210422

ard@ard-host-v5:~/ros/orocos_toolchain_ros$

> regards,
>
> Steven
>
> >
> >
> >>
> >> Steven
> >>
> >> >
> >> >
> >> >
> >> >>
> >> >>
> >> >>>
> >> >>>
> >> >>>>>
> >> >>>>> regards,
> >> >>>>>
> >> >>>>> Steven
> >> >>>>>
> >> >>>>>
> >> >>>>> >
> >> >>>>> >
> >> >>>>> >
> >> >>>>> >
> >> >>>>> >>
> >> >>>>> >> > At the end it seems to have work properly as I have this in
> the
> >> >>>>> >> > folder
> >> >>>>> >> > (and
> >> >>>>> >> > succeed a build yesterday) :
> >> >>>>> >> >
> >> >>>>> >> >
> >> >>>>> >> > ard@ard-host-v5
> :/media/DD_data/home/ard/ros/orocos_toolchain_ros$
> >> >>>>> >> > ls
> >> >>>>> >> > CMakeLists.txt env.sh ocl rosdep.yaml rtt_exercises
> >> >>>>> >> > rtt_ros_integration_example stack.xml utilmm
> >> >>>>> >> > env.mk Makefile orogen rtt
> >> >>>>> >> > rtt_ros_integration
> >> >>>>> >> > rtt_ros_integration_std_msgs typelib utilrb
> >> >>>>> >> >
> >> >>>>> >> > ard@ard-host-v5
> :/media/DD_data/home/ard/ros/orocos_toolchain_ros$
> >> >>>>> >> >
> >> >>>>> >> >
> >> >>>>> >> >
> >> >>>>> >> > _______________________________________________
> >> >>>>> >> > ros-users mailing list
> >> >>>>> >> > ros-users [..] ...
> >> >>>>> >> > https://code.ros.org/mailman/listinfo/ros-users
> >> >>>>> >> >
> >> >>>>> >> >
> >> >>>>> >> --
> >> >>>>> >> Orocos-Users mailing list
> >> >>>>> >> Orocos-Users [..] ...
> >> >>>>> >> http://lists.mech.kuleuven.be/mailman/listinfo/orocos-users
> >> >>>>> >
> >> >>>>> >
> >> >>>>> > _______________________________________________
> >> >>>>> > ros-users mailing list
> >> >>>>> > ros-users [..] ...
> >> >>>>> > https://code.ros.org/mailman/listinfo/ros-users
> >> >>>>> >
> >> >>>>> >
> >> >>>>> _______________________________________________
> >> >>>>> ros-users mailing list
> >> >>>>> ros-users [..] ...
> >> >>>>> https://code.ros.org/mailman/listinfo/ros-users
> >> >>>>
> >> >>>
> >> >>
> >> >
> >> >
> >> > _______________________________________________
> >> > ros-users mailing list
> >> > ros-users [..] ...
> >> > https://code.ros.org/mailman/listinfo/ros-users
> >> >
> >> >
> >> --
> >> Orocos-Users mailing list
> >> Orocos-Users [..] ...
> >> http://lists.mech.kuleuven.be/mailman/listinfo/orocos-users
> >
> >
> > _______________________________________________
> > ros-users mailing list
> > ros-users [..] ...
> > https://code.ros.org/mailman/listinfo/ros-users
> >
> >
> --
> Orocos-Users mailing list
> Orocos-Users [..] ...
> http://lists.mech.kuleuven.be/mailman/listinfo/orocos-users
>

[ros-users] orocos_toolchain_ros for debian

2011/2/7 Willy Lambert <lambert [dot] willy [..] ...>:
>
>
> 2011/2/7 Steven Bellens <steven [dot] bellens [..] ...>
>>
>> [...]
>>
>> >>
>> >> I've pushed a fixed for this to the orocos_toolchain_ros_0.2 branch.
>> >> Other branches will be updated when Ruben triggers a new release.
>> >
>> > Ok thanks. I am a bit lost with versionning and compatibility.
>> > May I have a proper install with cturtle or diamonback with the
>> > orocos_toolchain_ros_0.2  ? Or should I only wait for next release (if
>> > so I
>> > would be glad to have a goal of it, with no guarantee of course, but
>> > i'll
>> > help my scheduling)
>>
>> Ruben did a new release of the orocos_toolchain_ros packages this
>> morning. It will take some time before the software is available, as
>> it needs to pass some tests on the ROS build farm first. It then
>> should be available for installation when a new release is triggered
>> at willowgarage (no idea when this will be).
>>
>> In the meantime you can of course work on the git repositories. We're
>> deleting the orocos_toolchain_ros_0.2 branch and continue development
>> on master (as they both serve the same purpose anyway). This
>> development is diamondback based. If you work with cturtle - use the
>> cturtle_next branch.
>>
>
> as diamondback is still not installing properly on my pc I can't test it.
>
> In my cturtle installation I used the cturtle_next as you suggested, from
> scratch (so no git problem), using
> http://www.ros.org/wiki/orocos_toolchain_ros
> and "cturtle_next" instead of cturtle
>
>  but it is still not ok :
>
> ard@ard-host-v5:~/ros$ rosdep install orocos_toolchain_ros
> Invalid manifest
> file[/home/ard/ros/orocos_toolchain_ros/rtt_exercises/rtt-exercises/hello-7-deployment/manifest.xml]:
> missing required 'license' element
> ........... and so many others
> ERROR: QUITTING: due to conflicting rosdep definitions, please resolve this
> conflict.
> Rules for ruby do not match:
>     ruby [/home/ard/ros/ros/rosdep.yaml]
>     ruby1.8-dev libruby1.8 [/home/ard/ros/orocos_toolchain_ros/rosdep.yaml]
> ard@ard-host-v5:~/ros$
>
>
>
>
> ard@ard-host-v5:~/ros/orocos_toolchain_ros$ rosmake
> [ rosmake ] No package specified.  Building stack
> ['orocos_toolchain_ros']
> [ rosmake ] Packages requested are:
> ['orocos_toolchain_ros']
> [ rosmake ] Logging to
> directory/home/ard/.ros/rosmake/rosmake_output-20110207-210422
> [ rosmake ] Expanded args ['orocos_toolchain_ros'] to:
> ['log4cpp', 'rtt_ros_integration_example', 'ocl', 'utilrb', 'typelib',
> 'rtt', 'hello-7-deployment', 'helloworld', 'hello-2-properties',
> 'hello-5-services', 'controller-1', 'hello-3-dataports',
> 'hello-6-scripting', 'hello-1-task-execution', 'hello-4-operations',
> 'utilmm', 'orogen', 'rtt_ros_integration_nav_msgs', 'rtt_ros_integration',
> 'rtt_ros_param', 'rtt_ros_integration_geometry_msgs',
> 'rtt_ros_integration_roslib_msgs', 'rtt_ros_integration_std_msgs']
> [ rosmake ] Checking rosdeps compliance for packages orocos_toolchain_ros.
> This may take a few
> seconds.
> Invalid manifest
> file[/home/ard/ros/orocos_toolchain_ros/rtt_exercises/rtt-exercises/hello-7-deployment/manifest.xml]:
> missing required 'license' element
>  ..................... and so many other
> QUITTING: due to conflicting rosdep definitions, please resolve this
> conflict.
> Rules for ruby do not match:
>     ruby [/home/ard/ros/ros/rosdep.yaml]
>     ruby1.8-dev libruby1.8 [/home/ard/ros/orocos_toolchain_ros/rosdep.yaml]

We overwrite the ruby dependency in the toolchain stack because we
need the 1.8 version. You can either update the entry in ($find
ros)/rosdep.yaml for your platform to match the one in $(find
orocos_toolchain_ros)/rosdep.yaml or just remove the entry in $(find
ros)/rosdep.yaml completely. The ruby dependency is actually removed
in the $(find ros)/rosdep.yaml file in diamondback I see.

regards,

Steven

> [ rosmake ] rosdep check passed all system dependencies in
> packages
> [ rosmake ] Starting >>>
> tools/rospack
> [ rosmake ] Finished <<<
> tools/rospack
> [ rosmake ] Starting >>>
> 3rdparty/gtest
> [ rosmake ] Finished <<<
> 3rdparty/gtest
> [ rosmake ] Starting >>>
> core/genmsg_cpp
> [ rosmake ] Finished <<<
> core/genmsg_cpp
> [rosmake-0] Starting >>> log4cpp [ make
> ]
> [rosmake-1] Starting >>> roslang [ make
> ]
> [rosmake-1] Finished <<< roslang  No Makefile in package
> roslang
> [rosmake-1] Starting >>> roslib [ make
> ]
> [rosmake-1] Finished <<< roslib [PASS] [ 0.91 seconds
> ]
> [rosmake-1] Starting >>> xmlrpcpp [ make
> ]
> [rosmake-1] Finished <<< xmlrpcpp [PASS] [ 0.37 seconds
> ]
> [rosmake-1] Starting >>> rosconsole [ make
> ]
> [rosmake-1] Finished <<< rosconsole [PASS] [ 0.69 seconds
> ]
> [rosmake-1] Starting >>> roscpp [ make
> ]
> [rosmake-1] Finished <<< roscpp [PASS] [ 1.30 seconds
> ]
> [rosmake-1] Starting >>> rtt [ make
> ]
> [ rosmake ] Output from build of package log4cpp written
> to:
> [ 2 Active 7/45 Complete ]
> [ rosmake ]
> /home/ard/.ros/rosmake/rosmake_output-20110207-210422/log4cpp/build_output.log
> [rosmake-0] Finished <<< log4cpp [PASS] [ 56.40 seconds ] -- WARNING: 1
> compiler
> warnings
> [rosmake-0] Starting >>> rosbuild [ make
> ]
> [rosmake-0] Finished <<< rosbuild  No Makefile in package
> rosbuild
> [rosmake-0] Starting >>> std_msgs [ make
> ]
> [rosmake-0] Finished <<< std_msgs [PASS] [ 5.61 seconds
> ]
> [rosmake-0] Starting >>> utilrb [ make
> ]
> [ rosmake ] Output from build of package utilrb written
> to:]
> [ 2 Active 10/45 Complete ]
> [ rosmake ]
> /home/ard/.ros/rosmake/rosmake_output-20110207-210422/utilrb/build_output.log
> [rosmake-0] Finished <<< utilrb [PASS] [ 49.13 seconds ] -- WARNING: 1
> compiler
> warnings
> [rosmake-0] Starting >>> utilmm [ make
> ]
> [ rosmake ] Last 40 linest: 110.4 sec ] [ utilmm: 2.5 sec
> ]
> [ 2 Active 11/45 Complete ]
> {-------------------------------------------------------------------------------
>   if [ ! -f utilmm.md5sum ]; then echo "Error: Couldn't find md5sum file
> utilmm.md5sum" && false; fi
>   `rospack find rosbuild`/bin/download_checkmd5.py
> http://people.mech.kuleuven.be/~sbellens/orocos-toolchain/orocos-toolcha...
> build/v2.1.0 `awk {'print $1'} utilmm.md5sum`
>   [rosbuild] Downloading
> http://people.mech.kuleuven.be/~sbellens/orocos-toolchain/orocos-toolcha...
> to build/v2.1.0...Done
>   [rosbuild] Checking md5sum on build/v2.1.0
>   touch -c build/v2.1.0
>   rm -rf build/orocos-toolchain-utilmm
>   cd build; tar xzf ../build/v2.1.0
>   cd build/orocos-toolchain-utilmm &&  patch -p0 < ../../utilmm.patch;
>   patching file CMakeLists.txt
>   touch build/orocos-toolchain-utilmm/unpacked
>   mkdir -p bin
>   cd build && cmake -Wdev -DCMAKE_TOOLCHAIN_FILE=`rospack find
> rosbuild`/rostoolchain.cmake -DCMAKE_INSTALL_PREFIX=`rospack find
> utilmm`/install ..
>   -- The C compiler identification is GNU
>   -- The CXX compiler identification is GNU
>   -- Check for working C compiler: /usr/bin/gcc
>   -- Check for working C compiler: /usr/bin/gcc -- works
>   -- Detecting C compiler ABI info
>   -- Detecting C compiler ABI info - done
>   -- Check for working CXX compiler: /usr/bin/c++
>   -- Check for working CXX compiler: /usr/bin/c++ -- works
>   -- Detecting CXX compiler ABI info
>   -- Detecting CXX compiler ABI info - done
>   [rosbuild] Building package utilmm
>   [rosbuild] Cached build flags older than manifests; calling rospack to get
> flags
>   [rosbuild] Including /home/ard/ros/ros/core/roscpp/cmake/roscpp.cmake
>   [rosbuild] Including /home/ard/ros/ros/core/rospy/cmake/rospy.cmake
>   [rosbuild] Including /home/ard/ros/ros/core/roslisp/cmake/roslisp.cmake
>   -- Found The Following Boost Libraries:
>   --   unit_test_framework
>   -- Boost Version: 1.42.0
>   -- cannot find boost/graph
>   CMake Error at build/orocos-toolchain-utilmm/cmake/FindBoost.cmake:367
> (MESSAGE):
>     Boost and/or some required components not found.  Please install the
> Boost
>     libraries AND development packages
>   Call Stack (most recent call first):
>     build/orocos-toolchain-utilmm/CMakeLists.txt:9 (FIND_PACKAGE)
>
>
>   -- Configuring incomplete, errors occurred!
> -------------------------------------------------------------------------------}
> [ rosmake ] Output from build of package utilmm written to:
> [ rosmake ]
> /home/ard/.ros/rosmake/rosmake_output-20110207-210422/utilmm/build_output.log
> [rosmake-0] Finished <<< utilmm [FAIL] [ 2.55 seconds
> ]
> [ rosmake ] Halting due to failure in package utilmm.
> [ rosmake ] Waiting for other threads to
> complete.
> [rosmake-1] Finished <<< rtt [PASS] [ 262.82 seconds
> ]
> [ rosmake ]
> Results:
> [ rosmake ] Built 13 packages with 1
> failures.
> [ rosmake ] Summary output to
> directory
> [ rosmake ]
> /home/ard/.ros/rosmake/rosmake_output-20110207-210422
> ard@ard-host-v5:~/ros/orocos_toolchain_ros$
>
>
>
>
>>
>> regards,
>>
>> Steven
>>
>> >
>> >
>> >>
>> >> Steven
>> >>
>> >> >
>> >> >
>> >> >
>> >> >>
>> >> >>
>> >> >>>
>> >> >>>
>> >> >>>>>
>> >> >>>>> regards,
>> >> >>>>>
>> >> >>>>> Steven
>> >> >>>>>
>> >> >>>>>
>> >> >>>>> >
>> >> >>>>> >
>> >> >>>>> >
>> >> >>>>> >
>> >> >>>>> >>
>> >> >>>>> >> > At the end it seems to have work properly as I have this in
>> >> >>>>> >> > the
>> >> >>>>> >> > folder
>> >> >>>>> >> > (and
>> >> >>>>> >> > succeed a build yesterday) :
>> >> >>>>> >> >
>> >> >>>>> >> >
>> >> >>>>> >> >
>> >> >>>>> >> > ard@ard-host-v5:/media/DD_data/home/ard/ros/orocos_toolchain_ros$
>> >> >>>>> >> > ls
>> >> >>>>> >> > CMakeLists.txt  env.sh    ocl     rosdep.yaml  rtt_exercises
>> >> >>>>> >> > rtt_ros_integration_example   stack.xml  utilmm
>> >> >>>>> >> > env.mk          Makefile  orogen  rtt
>> >> >>>>> >> > rtt_ros_integration
>> >> >>>>> >> > rtt_ros_integration_std_msgs  typelib    utilrb
>> >> >>>>> >> >
>> >> >>>>> >> >
>> >> >>>>> >> > ard@ard-host-v5:/media/DD_data/home/ard/ros/orocos_toolchain_ros$
>> >> >>>>> >> >
>> >> >>>>> >> >
>> >> >>>>> >> >
>> >> >>>>> >> > _______________________________________________
>> >> >>>>> >> > ros-users mailing list
>> >> >>>>> >> > ros-users [..] ...
>> >> >>>>> >> > https://code.ros.org/mailman/listinfo/ros-users
>> >> >>>>> >> >
>> >> >>>>> >> >
>> >> >>>>> >> --
>> >> >>>>> >> Orocos-Users mailing list
>> >> >>>>> >> Orocos-Users [..] ...
>> >> >>>>> >> http://lists.mech.kuleuven.be/mailman/listinfo/orocos-users
>> >> >>>>> >
>> >> >>>>> >
>> >> >>>>> > _______________________________________________
>> >> >>>>> > ros-users mailing list
>> >> >>>>> > ros-users [..] ...
>> >> >>>>> > https://code.ros.org/mailman/listinfo/ros-users
>> >> >>>>> >
>> >> >>>>> >
>> >> >>>>> _______________________________________________
>> >> >>>>> ros-users mailing list
>> >> >>>>> ros-users [..] ...
>> >> >>>>> https://code.ros.org/mailman/listinfo/ros-users
>> >> >>>>
>> >> >>>
>> >> >>
>> >> >
>> >> >
>> >> > _______________________________________________
>> >> > ros-users mailing list
>> >> > ros-users [..] ...
>> >> > https://code.ros.org/mailman/listinfo/ros-users
>> >> >
>> >> >
>> >> --
>> >> Orocos-Users mailing list
>> >> Orocos-Users [..] ...
>> >> http://lists.mech.kuleuven.be/mailman/listinfo/orocos-users
>> >
>> >
>> > _______________________________________________
>> > ros-users mailing list
>> > ros-users [..] ...
>> > https://code.ros.org/mailman/listinfo/ros-users
>> >
>> >
>> --
>> Orocos-Users mailing list
>> Orocos-Users [..] ...
>> http://lists.mech.kuleuven.be/mailman/listinfo/orocos-users
>
>
> _______________________________________________
> ros-users mailing list
> ros-users [..] ...
> https://code.ros.org/mailman/listinfo/ros-users
>
>

[ros-users] orocos_toolchain_ros for debian

2011/2/8 Steven Bellens <steven [dot] bellens [..] ...>

> 2011/2/7 Willy Lambert <lambert [dot] willy [..] ...>:
> >
> >
> > 2011/2/7 Steven Bellens <steven [dot] bellens [..] ...>
> >>
> >> [...]
> >>
> >> >>
> >> >> I've pushed a fixed for this to the orocos_toolchain_ros_0.2 branch.
> >> >> Other branches will be updated when Ruben triggers a new release.
> >> >
> >> > Ok thanks. I am a bit lost with versionning and compatibility.
> >> > May I have a proper install with cturtle or diamonback with the
> >> > orocos_toolchain_ros_0.2 ? Or should I only wait for next release (if
> >> > so I
> >> > would be glad to have a goal of it, with no guarantee of course, but
> >> > i'll
> >> > help my scheduling)
> >>
> >> Ruben did a new release of the orocos_toolchain_ros packages this
> >> morning. It will take some time before the software is available, as
> >> it needs to pass some tests on the ROS build farm first. It then
> >> should be available for installation when a new release is triggered
> >> at willowgarage (no idea when this will be).
> >>
> >> In the meantime you can of course work on the git repositories. We're
> >> deleting the orocos_toolchain_ros_0.2 branch and continue development
> >> on master (as they both serve the same purpose anyway). This
> >> development is diamondback based. If you work with cturtle - use the
> >> cturtle_next branch.
> >>
> >
> > as diamondback is still not installing properly on my pc I can't test it.
> >
> > In my cturtle installation I used the cturtle_next as you suggested, from
> > scratch (so no git problem), using
> > http://www.ros.org/wiki/orocos_toolchain_ros
> > and "cturtle_next" instead of cturtle
> >
> > but it is still not ok :
> >
> > ard@ard-host-v5:~/ros$ rosdep install orocos_toolchain_ros
> > Invalid manifest
> >
> file[/home/ard/ros/orocos_toolchain_ros/rtt_exercises/rtt-exercises/hello-7-deployment/manifest.xml]:
> > missing required 'license' element
> > ........... and so many others
> > ERROR: QUITTING: due to conflicting rosdep definitions, please resolve
> this
> > conflict.
> > Rules for ruby do not match:
> > ruby [/home/ard/ros/ros/rosdep.yaml]
> > ruby1.8-dev libruby1.8
> [/home/ard/ros/orocos_toolchain_ros/rosdep.yaml]
> > ard@ard-host-v5:~/ros$
> >
> >
> >
> >
> > ard@ard-host-v5:~/ros/orocos_toolchain_ros$ rosmake
> > [ rosmake ] No package specified. Building stack
> > ['orocos_toolchain_ros']
> > [ rosmake ] Packages requested are:
> > ['orocos_toolchain_ros']
> > [ rosmake ] Logging to
> > directory/home/ard/.ros/rosmake/rosmake_output-20110207-210422
> > [ rosmake ] Expanded args ['orocos_toolchain_ros'] to:
> > ['log4cpp', 'rtt_ros_integration_example', 'ocl', 'utilrb', 'typelib',
> > 'rtt', 'hello-7-deployment', 'helloworld', 'hello-2-properties',
> > 'hello-5-services', 'controller-1', 'hello-3-dataports',
> > 'hello-6-scripting', 'hello-1-task-execution', 'hello-4-operations',
> > 'utilmm', 'orogen', 'rtt_ros_integration_nav_msgs',
> 'rtt_ros_integration',
> > 'rtt_ros_param', 'rtt_ros_integration_geometry_msgs',
> > 'rtt_ros_integration_roslib_msgs', 'rtt_ros_integration_std_msgs']
> > [ rosmake ] Checking rosdeps compliance for packages
> orocos_toolchain_ros.
> > This may take a few
> > seconds.
> > Invalid manifest
> >
> file[/home/ard/ros/orocos_toolchain_ros/rtt_exercises/rtt-exercises/hello-7-deployment/manifest.xml]:
> > missing required 'license' element
> > ..................... and so many other
> > QUITTING: due to conflicting rosdep definitions, please resolve this
> > conflict.
> > Rules for ruby do not match:
> > ruby [/home/ard/ros/ros/rosdep.yaml]
> > ruby1.8-dev libruby1.8
> [/home/ard/ros/orocos_toolchain_ros/rosdep.yaml]
>
> We overwrite the ruby dependency in the toolchain stack because we
> need the 1.8 version. You can either update the entry in ($find
> ros)/rosdep.yaml for your platform to match the one in $(find
> orocos_toolchain_ros)/rosdep.yaml or just remove the entry in $(find
> ros)/rosdep.yaml completely. The ruby dependency is actually removed
> in the $(find ros)/rosdep.yaml file in diamondback I see.
>

Ok, thanks, I'll use this in waiting of Diamonback release

>
> regards,
>
> Steven
>
> > [ rosmake ] rosdep check passed all system dependencies in
> > packages
> > [ rosmake ] Starting >>>
> > tools/rospack
> > [ rosmake ] Finished <<<
> > tools/rospack
> > [ rosmake ] Starting >>>
> > 3rdparty/gtest
> > [ rosmake ] Finished <<<
> > 3rdparty/gtest
> > [ rosmake ] Starting >>>
> > core/genmsg_cpp
> > [ rosmake ] Finished <<<
> > core/genmsg_cpp
> > [rosmake-0] Starting >>> log4cpp [ make
> > ]
> > [rosmake-1] Starting >>> roslang [ make
> > ]
> > [rosmake-1] Finished <<< roslang No Makefile in package
> > roslang
> > [rosmake-1] Starting >>> roslib [ make
> > ]
> > [rosmake-1] Finished <<< roslib [PASS] [ 0.91 seconds
> > ]
> > [rosmake-1] Starting >>> xmlrpcpp [ make
> > ]
> > [rosmake-1] Finished <<< xmlrpcpp [PASS] [ 0.37 seconds
> > ]
> > [rosmake-1] Starting >>> rosconsole [ make
> > ]
> > [rosmake-1] Finished <<< rosconsole [PASS] [ 0.69 seconds
> > ]
> > [rosmake-1] Starting >>> roscpp [ make
> > ]
> > [rosmake-1] Finished <<< roscpp [PASS] [ 1.30 seconds
> > ]
> > [rosmake-1] Starting >>> rtt [ make
> > ]
> > [ rosmake ] Output from build of package log4cpp written
> > to:
> > [ 2 Active 7/45 Complete ]
> > [ rosmake ]
> >
> /home/ard/.ros/rosmake/rosmake_output-20110207-210422/log4cpp/build_output.log
> > [rosmake-0] Finished <<< log4cpp [PASS] [ 56.40 seconds ] -- WARNING: 1
> > compiler
> > warnings
> > [rosmake-0] Starting >>> rosbuild [ make
> > ]
> > [rosmake-0] Finished <<< rosbuild No Makefile in package
> > rosbuild
> > [rosmake-0] Starting >>> std_msgs [ make
> > ]
> > [rosmake-0] Finished <<< std_msgs [PASS] [ 5.61 seconds
> > ]
> > [rosmake-0] Starting >>> utilrb [ make
> > ]
> > [ rosmake ] Output from build of package utilrb written
> > to:]
> > [ 2 Active 10/45 Complete ]
> > [ rosmake ]
> >
> /home/ard/.ros/rosmake/rosmake_output-20110207-210422/utilrb/build_output.log
> > [rosmake-0] Finished <<< utilrb [PASS] [ 49.13 seconds ] -- WARNING: 1
> > compiler
> > warnings
> > [rosmake-0] Starting >>> utilmm [ make
> > ]
> > [ rosmake ] Last 40 linest: 110.4 sec ] [ utilmm: 2.5 sec
> > ]
> > [ 2 Active 11/45 Complete ]
> >
> {-------------------------------------------------------------------------------
> > if [ ! -f utilmm.md5sum ]; then echo "Error: Couldn't find md5sum file
> > utilmm.md5sum" && false; fi
> > `rospack find rosbuild`/bin/download_checkmd5.py
> >
> http://people.mech.kuleuven.be/~sbellens/orocos-toolchain/orocos-toolcha...
> > build/v2.1.0 `awk {'print $1'} utilmm.md5sum`
> > [rosbuild] Downloading
> >
> http://people.mech.kuleuven.be/~sbellens/orocos-toolchain/orocos-toolcha...
> > to build/v2.1.0...Done
> > [rosbuild] Checking md5sum on build/v2.1.0
> > touch -c build/v2.1.0
> > rm -rf build/orocos-toolchain-utilmm
> > cd build; tar xzf ../build/v2.1.0
> > cd build/orocos-toolchain-utilmm && patch -p0 < ../../utilmm.patch;
> > patching file CMakeLists.txt
> > touch build/orocos-toolchain-utilmm/unpacked
> > mkdir -p bin
> > cd build && cmake -Wdev -DCMAKE_TOOLCHAIN_FILE=`rospack find
> > rosbuild`/rostoolchain.cmake -DCMAKE_INSTALL_PREFIX=`rospack find
> > utilmm`/install ..
> > -- The C compiler identification is GNU
> > -- The CXX compiler identification is GNU
> > -- Check for working C compiler: /usr/bin/gcc
> > -- Check for working C compiler: /usr/bin/gcc -- works
> > -- Detecting C compiler ABI info
> > -- Detecting C compiler ABI info - done
> > -- Check for working CXX compiler: /usr/bin/c++
> > -- Check for working CXX compiler: /usr/bin/c++ -- works
> > -- Detecting CXX compiler ABI info
> > -- Detecting CXX compiler ABI info - done
> > [rosbuild] Building package utilmm
> > [rosbuild] Cached build flags older than manifests; calling rospack to
> get
> > flags
> > [rosbuild] Including /home/ard/ros/ros/core/roscpp/cmake/roscpp.cmake
> > [rosbuild] Including /home/ard/ros/ros/core/rospy/cmake/rospy.cmake
> > [rosbuild] Including /home/ard/ros/ros/core/roslisp/cmake/roslisp.cmake
> > -- Found The Following Boost Libraries:
> > -- unit_test_framework
> > -- Boost Version: 1.42.0
> > -- cannot find boost/graph
> > CMake Error at build/orocos-toolchain-utilmm/cmake/FindBoost.cmake:367
> > (MESSAGE):
> > Boost and/or some required components not found. Please install the
> > Boost
> > libraries AND development packages
> > Call Stack (most recent call first):
> > build/orocos-toolchain-utilmm/CMakeLists.txt:9 (FIND_PACKAGE)
> >
> >
> > -- Configuring incomplete, errors occurred!
> >
> -------------------------------------------------------------------------------}
> > [ rosmake ] Output from build of package utilmm written to:
> > [ rosmake ]
> >
> /home/ard/.ros/rosmake/rosmake_output-20110207-210422/utilmm/build_output.log
> > [rosmake-0] Finished <<< utilmm [FAIL] [ 2.55 seconds
> > ]
> > [ rosmake ] Halting due to failure in package utilmm.
> > [ rosmake ] Waiting for other threads to
> > complete.
> > [rosmake-1] Finished <<< rtt [PASS] [ 262.82 seconds
> > ]
> > [ rosmake ]
> > Results:
> > [ rosmake ] Built 13 packages with 1
> > failures.
> > [ rosmake ] Summary output to
> > directory
> > [ rosmake ]
> > /home/ard/.ros/rosmake/rosmake_output-20110207-210422
> > ard@ard-host-v5:~/ros/orocos_toolchain_ros$
> >
> >
> >
> >
> >>
> >> regards,
> >>
> >> Steven
> >>
> >> >
> >> >
> >> >>
> >> >> Steven
> >> >>
> >> >> >
> >> >> >
> >> >> >
> >> >> >>
> >> >> >>
> >> >> >>>
> >> >> >>>
> >> >> >>>>>
> >> >> >>>>> regards,
> >> >> >>>>>
> >> >> >>>>> Steven
> >> >> >>>>>
> >> >> >>>>>
> >> >> >>>>> >
> >> >> >>>>> >
> >> >> >>>>> >
> >> >> >>>>> >
> >> >> >>>>> >>
> >> >> >>>>> >> > At the end it seems to have work properly as I have this
> in
> >> >> >>>>> >> > the
> >> >> >>>>> >> > folder
> >> >> >>>>> >> > (and
> >> >> >>>>> >> > succeed a build yesterday) :
> >> >> >>>>> >> >
> >> >> >>>>> >> >
> >> >> >>>>> >> >
> >> >> >>>>> >> > ard@ard-host-v5
> :/media/DD_data/home/ard/ros/orocos_toolchain_ros$
> >> >> >>>>> >> > ls
> >> >> >>>>> >> > CMakeLists.txt env.sh ocl rosdep.yaml
> rtt_exercises
> >> >> >>>>> >> > rtt_ros_integration_example stack.xml utilmm
> >> >> >>>>> >> > env.mk Makefile orogen rtt
> >> >> >>>>> >> > rtt_ros_integration
> >> >> >>>>> >> > rtt_ros_integration_std_msgs typelib utilrb
> >> >> >>>>> >> >
> >> >> >>>>> >> >
> >> >> >>>>> >> > ard@ard-host-v5
> :/media/DD_data/home/ard/ros/orocos_toolchain_ros$
> >> >> >>>>> >> >
> >> >> >>>>> >> >
> >> >> >>>>> >> >
> >> >> >>>>> >> > _______________________________________________
> >> >> >>>>> >> > ros-users mailing list
> >> >> >>>>> >> > ros-users [..] ...
> >> >> >>>>> >> > https://code.ros.org/mailman/listinfo/ros-users
> >> >> >>>>> >> >
> >> >> >>>>> >> >
> >> >> >>>>> >> --
> >> >> >>>>> >> Orocos-Users mailing list
> >> >> >>>>> >> Orocos-Users [..] ...
> >> >> >>>>> >> http://lists.mech.kuleuven.be/mailman/listinfo/orocos-users
> >> >> >>>>> >
> >> >> >>>>> >
> >> >> >>>>> > _______________________________________________
> >> >> >>>>> > ros-users mailing list
> >> >> >>>>> > ros-users [..] ...
> >> >> >>>>> > https://code.ros.org/mailman/listinfo/ros-users
> >> >> >>>>> >
> >> >> >>>>> >
> >> >> >>>>> _______________________________________________
> >> >> >>>>> ros-users mailing list
> >> >> >>>>> ros-users [..] ...
> >> >> >>>>> https://code.ros.org/mailman/listinfo/ros-users
> >> >> >>>>
> >> >> >>>
> >> >> >>
> >> >> >
> >> >> >
> >> >> > _______________________________________________
> >> >> > ros-users mailing list
> >> >> > ros-users [..] ...
> >> >> > https://code.ros.org/mailman/listinfo/ros-users
> >> >> >
> >> >> >
> >> >> --
> >> >> Orocos-Users mailing list
> >> >> Orocos-Users [..] ...
> >> >> http://lists.mech.kuleuven.be/mailman/listinfo/orocos-users
> >> >
> >> >
> >> > _______________________________________________
> >> > ros-users mailing list
> >> > ros-users [..] ...
> >> > https://code.ros.org/mailman/listinfo/ros-users
> >> >
> >> >
> >> --
> >> Orocos-Users mailing list
> >> Orocos-Users [..] ...
> >> http://lists.mech.kuleuven.be/mailman/listinfo/orocos-users
> >
> >
> > _______________________________________________
> > ros-users mailing list
> > ros-users [..] ...
> > https://code.ros.org/mailman/listinfo/ros-users
> >
> >
> --
> Orocos-Users mailing list
> Orocos-Users [..] ...
> http://lists.mech.kuleuven.be/mailman/listinfo/orocos-users
>

[ros-users] orocos_toolchain_ros for debian

2011/2/7 Willy Lambert <lambert [dot] willy [..] ...>:
>
>
> 2011/2/7 Steven Bellens <steven [dot] bellens [..] ...>
>>
>> [...]
>>
>> >>
>> >> I've pushed a fixed for this to the orocos_toolchain_ros_0.2 branch.
>> >> Other branches will be updated when Ruben triggers a new release.
>> >
>> > Ok thanks. I am a bit lost with versionning and compatibility.
>> > May I have a proper install with cturtle or diamonback with the
>> > orocos_toolchain_ros_0.2  ? Or should I only wait for next release (if
>> > so I
>> > would be glad to have a goal of it, with no guarantee of course, but
>> > i'll
>> > help my scheduling)
>>
>> Ruben did a new release of the orocos_toolchain_ros packages this
>> morning. It will take some time before the software is available, as
>> it needs to pass some tests on the ROS build farm first. It then
>> should be available for installation when a new release is triggered
>> at willowgarage (no idea when this will be).
>>
>> In the meantime you can of course work on the git repositories. We're
>> deleting the orocos_toolchain_ros_0.2 branch and continue development
>> on master (as they both serve the same purpose anyway). This
>> development is diamondback based. If you work with cturtle - use the
>> cturtle_next branch.
>>
>
> as diamondback is still not installing properly on my pc I can't test it.
>
> In my cturtle installation I used the cturtle_next as you suggested, from
> scratch (so no git problem), using
> http://www.ros.org/wiki/orocos_toolchain_ros
> and "cturtle_next" instead of cturtle
>
>  but it is still not ok :
>
> ard@ard-host-v5:~/ros$ rosdep install orocos_toolchain_ros
> Invalid manifest
> file[/home/ard/ros/orocos_toolchain_ros/rtt_exercises/rtt-exercises/hello-7-deployment/manifest.xml]:
> missing required 'license' element
> ........... and so many others
> ERROR: QUITTING: due to conflicting rosdep definitions, please resolve this
> conflict.
> Rules for ruby do not match:
>     ruby [/home/ard/ros/ros/rosdep.yaml]
>     ruby1.8-dev libruby1.8 [/home/ard/ros/orocos_toolchain_ros/rosdep.yaml]
> ard@ard-host-v5:~/ros$
>
>
>
>
> ard@ard-host-v5:~/ros/orocos_toolchain_ros$ rosmake
> [ rosmake ] No package specified.  Building stack
> ['orocos_toolchain_ros']
> [ rosmake ] Packages requested are:
> ['orocos_toolchain_ros']
> [ rosmake ] Logging to
> directory/home/ard/.ros/rosmake/rosmake_output-20110207-210422
> [ rosmake ] Expanded args ['orocos_toolchain_ros'] to:
> ['log4cpp', 'rtt_ros_integration_example', 'ocl', 'utilrb', 'typelib',
> 'rtt', 'hello-7-deployment', 'helloworld', 'hello-2-properties',
> 'hello-5-services', 'controller-1', 'hello-3-dataports',
> 'hello-6-scripting', 'hello-1-task-execution', 'hello-4-operations',
> 'utilmm', 'orogen', 'rtt_ros_integration_nav_msgs', 'rtt_ros_integration',
> 'rtt_ros_param', 'rtt_ros_integration_geometry_msgs',
> 'rtt_ros_integration_roslib_msgs', 'rtt_ros_integration_std_msgs']
> [ rosmake ] Checking rosdeps compliance for packages orocos_toolchain_ros.
> This may take a few
> seconds.
> Invalid manifest
> file[/home/ard/ros/orocos_toolchain_ros/rtt_exercises/rtt-exercises/hello-7-deployment/manifest.xml]:
> missing required 'license' element
>  ..................... and so many other
> QUITTING: due to conflicting rosdep definitions, please resolve this
> conflict.
> Rules for ruby do not match:
>     ruby [/home/ard/ros/ros/rosdep.yaml]
>     ruby1.8-dev libruby1.8 [/home/ard/ros/orocos_toolchain_ros/rosdep.yaml]
> [ rosmake ] rosdep check passed all system dependencies in
> packages
> [ rosmake ] Starting >>>
> tools/rospack
> [ rosmake ] Finished <<<
> tools/rospack
> [ rosmake ] Starting >>>
> 3rdparty/gtest
> [ rosmake ] Finished <<<
> 3rdparty/gtest
> [ rosmake ] Starting >>>
> core/genmsg_cpp
> [ rosmake ] Finished <<<
> core/genmsg_cpp
> [rosmake-0] Starting >>> log4cpp [ make
> ]
> [rosmake-1] Starting >>> roslang [ make
> ]
> [rosmake-1] Finished <<< roslang  No Makefile in package
> roslang
> [rosmake-1] Starting >>> roslib [ make
> ]
> [rosmake-1] Finished <<< roslib [PASS] [ 0.91 seconds
> ]
> [rosmake-1] Starting >>> xmlrpcpp [ make
> ]
> [rosmake-1] Finished <<< xmlrpcpp [PASS] [ 0.37 seconds
> ]
> [rosmake-1] Starting >>> rosconsole [ make
> ]
> [rosmake-1] Finished <<< rosconsole [PASS] [ 0.69 seconds
> ]
> [rosmake-1] Starting >>> roscpp [ make
> ]
> [rosmake-1] Finished <<< roscpp [PASS] [ 1.30 seconds
> ]
> [rosmake-1] Starting >>> rtt [ make
> ]
> [ rosmake ] Output from build of package log4cpp written
> to:
> [ 2 Active 7/45 Complete ]
> [ rosmake ]
> /home/ard/.ros/rosmake/rosmake_output-20110207-210422/log4cpp/build_output.log
> [rosmake-0] Finished <<< log4cpp [PASS] [ 56.40 seconds ] -- WARNING: 1
> compiler
> warnings
> [rosmake-0] Starting >>> rosbuild [ make
> ]
> [rosmake-0] Finished <<< rosbuild  No Makefile in package
> rosbuild
> [rosmake-0] Starting >>> std_msgs [ make
> ]
> [rosmake-0] Finished <<< std_msgs [PASS] [ 5.61 seconds
> ]
> [rosmake-0] Starting >>> utilrb [ make
> ]
> [ rosmake ] Output from build of package utilrb written
> to:]
> [ 2 Active 10/45 Complete ]
> [ rosmake ]
> /home/ard/.ros/rosmake/rosmake_output-20110207-210422/utilrb/build_output.log
> [rosmake-0] Finished <<< utilrb [PASS] [ 49.13 seconds ] -- WARNING: 1
> compiler
> warnings
> [rosmake-0] Starting >>> utilmm [ make
> ]
> [ rosmake ] Last 40 linest: 110.4 sec ] [ utilmm: 2.5 sec
> ]
> [ 2 Active 11/45 Complete ]
> {-------------------------------------------------------------------------------
>   if [ ! -f utilmm.md5sum ]; then echo "Error: Couldn't find md5sum file
> utilmm.md5sum" && false; fi
>   `rospack find rosbuild`/bin/download_checkmd5.py
> http://people.mech.kuleuven.be/~sbellens/orocos-toolchain/orocos-toolcha...
> build/v2.1.0 `awk {'print $1'} utilmm.md5sum`
>   [rosbuild] Downloading
> http://people.mech.kuleuven.be/~sbellens/orocos-toolchain/orocos-toolcha...
> to build/v2.1.0...Done
>   [rosbuild] Checking md5sum on build/v2.1.0
>   touch -c build/v2.1.0
>   rm -rf build/orocos-toolchain-utilmm
>   cd build; tar xzf ../build/v2.1.0
>   cd build/orocos-toolchain-utilmm &&  patch -p0 < ../../utilmm.patch;
>   patching file CMakeLists.txt
>   touch build/orocos-toolchain-utilmm/unpacked
>   mkdir -p bin
>   cd build && cmake -Wdev -DCMAKE_TOOLCHAIN_FILE=`rospack find
> rosbuild`/rostoolchain.cmake -DCMAKE_INSTALL_PREFIX=`rospack find
> utilmm`/install ..
>   -- The C compiler identification is GNU
>   -- The CXX compiler identification is GNU
>   -- Check for working C compiler: /usr/bin/gcc
>   -- Check for working C compiler: /usr/bin/gcc -- works
>   -- Detecting C compiler ABI info
>   -- Detecting C compiler ABI info - done
>   -- Check for working CXX compiler: /usr/bin/c++
>   -- Check for working CXX compiler: /usr/bin/c++ -- works
>   -- Detecting CXX compiler ABI info
>   -- Detecting CXX compiler ABI info - done
>   [rosbuild] Building package utilmm
>   [rosbuild] Cached build flags older than manifests; calling rospack to get
> flags
>   [rosbuild] Including /home/ard/ros/ros/core/roscpp/cmake/roscpp.cmake
>   [rosbuild] Including /home/ard/ros/ros/core/rospy/cmake/rospy.cmake
>   [rosbuild] Including /home/ard/ros/ros/core/roslisp/cmake/roslisp.cmake
>   -- Found The Following Boost Libraries:
>   --   unit_test_framework
>   -- Boost Version: 1.42.0
>   -- cannot find boost/graph
>   CMake Error at build/orocos-toolchain-utilmm/cmake/FindBoost.cmake:367
> (MESSAGE):
>     Boost and/or some required components not found.  Please install the
> Boost
>     libraries AND development packages
>   Call Stack (most recent call first):
>     build/orocos-toolchain-utilmm/CMakeLists.txt:9 (FIND_PACKAGE)

And do you actually have these installed? The boost dependency
packages are defined in $(find ros)/rosdep.yaml (you can find out with
'rosdep where_defined boost'). I see there is no boost-graph entry for
the debian platform. You'll have to add something like
'libboost-dev-graph' for your platform most probably. I'll switch to
CTurtle and see if I can get the ruby conflict sorted out.

Steven

>
>
>   -- Configuring incomplete, errors occurred!
> -------------------------------------------------------------------------------}
> [ rosmake ] Output from build of package utilmm written to:
> [ rosmake ]
> /home/ard/.ros/rosmake/rosmake_output-20110207-210422/utilmm/build_output.log
> [rosmake-0] Finished <<< utilmm [FAIL] [ 2.55 seconds
> ]
> [ rosmake ] Halting due to failure in package utilmm.
> [ rosmake ] Waiting for other threads to
> complete.
> [rosmake-1] Finished <<< rtt [PASS] [ 262.82 seconds
> ]
> [ rosmake ]
> Results:
> [ rosmake ] Built 13 packages with 1
> failures.
> [ rosmake ] Summary output to
> directory
> [ rosmake ]
> /home/ard/.ros/rosmake/rosmake_output-20110207-210422
> ard@ard-host-v5:~/ros/orocos_toolchain_ros$
>
>
>
>
>>
>> regards,
>>
>> Steven
>>
>> >
>> >
>> >>
>> >> Steven
>> >>
>> >> >
>> >> >
>> >> >
>> >> >>
>> >> >>
>> >> >>>
>> >> >>>
>> >> >>>>>
>> >> >>>>> regards,
>> >> >>>>>
>> >> >>>>> Steven
>> >> >>>>>
>> >> >>>>>
>> >> >>>>> >
>> >> >>>>> >
>> >> >>>>> >
>> >> >>>>> >
>> >> >>>>> >>
>> >> >>>>> >> > At the end it seems to have work properly as I have this in
>> >> >>>>> >> > the
>> >> >>>>> >> > folder
>> >> >>>>> >> > (and
>> >> >>>>> >> > succeed a build yesterday) :
>> >> >>>>> >> >
>> >> >>>>> >> >
>> >> >>>>> >> >
>> >> >>>>> >> > ard@ard-host-v5:/media/DD_data/home/ard/ros/orocos_toolchain_ros$
>> >> >>>>> >> > ls
>> >> >>>>> >> > CMakeLists.txt  env.sh    ocl     rosdep.yaml  rtt_exercises
>> >> >>>>> >> > rtt_ros_integration_example   stack.xml  utilmm
>> >> >>>>> >> > env.mk          Makefile  orogen  rtt
>> >> >>>>> >> > rtt_ros_integration
>> >> >>>>> >> > rtt_ros_integration_std_msgs  typelib    utilrb
>> >> >>>>> >> >
>> >> >>>>> >> >
>> >> >>>>> >> > ard@ard-host-v5:/media/DD_data/home/ard/ros/orocos_toolchain_ros$
>> >> >>>>> >> >
>> >> >>>>> >> >
>> >> >>>>> >> >
>> >> >>>>> >> > _______________________________________________
>> >> >>>>> >> > ros-users mailing list
>> >> >>>>> >> > ros-users [..] ...
>> >> >>>>> >> > https://code.ros.org/mailman/listinfo/ros-users
>> >> >>>>> >> >
>> >> >>>>> >> >
>> >> >>>>> >> --
>> >> >>>>> >> Orocos-Users mailing list
>> >> >>>>> >> Orocos-Users [..] ...
>> >> >>>>> >> http://lists.mech.kuleuven.be/mailman/listinfo/orocos-users
>> >> >>>>> >
>> >> >>>>> >
>> >> >>>>> > _______________________________________________
>> >> >>>>> > ros-users mailing list
>> >> >>>>> > ros-users [..] ...
>> >> >>>>> > https://code.ros.org/mailman/listinfo/ros-users
>> >> >>>>> >
>> >> >>>>> >
>> >> >>>>> _______________________________________________
>> >> >>>>> ros-users mailing list
>> >> >>>>> ros-users [..] ...
>> >> >>>>> https://code.ros.org/mailman/listinfo/ros-users
>> >> >>>>
>> >> >>>
>> >> >>
>> >> >
>> >> >
>> >> > _______________________________________________
>> >> > ros-users mailing list
>> >> > ros-users [..] ...
>> >> > https://code.ros.org/mailman/listinfo/ros-users
>> >> >
>> >> >
>> >> --
>> >> Orocos-Users mailing list
>> >> Orocos-Users [..] ...
>> >> http://lists.mech.kuleuven.be/mailman/listinfo/orocos-users
>> >
>> >
>> > _______________________________________________
>> > ros-users mailing list
>> > ros-users [..] ...
>> > https://code.ros.org/mailman/listinfo/ros-users
>> >
>> >
>> --
>> Orocos-Users mailing list
>> Orocos-Users [..] ...
>> http://lists.mech.kuleuven.be/mailman/listinfo/orocos-users
>
>
> _______________________________________________
> ros-users mailing list
> ros-users [..] ...
> https://code.ros.org/mailman/listinfo/ros-users
>
>

[ros-users] orocos_toolchain_ros for debian

2011/2/8 Steven Bellens <steven [dot] bellens [..] ...>

> 2011/2/7 Willy Lambert <lambert [dot] willy [..] ...>:
> >
> >
> > 2011/2/7 Steven Bellens <steven [dot] bellens [..] ...>
> >>
> >> [...]
> >>
> >> >>
> >> >> I've pushed a fixed for this to the orocos_toolchain_ros_0.2 branch.
> >> >> Other branches will be updated when Ruben triggers a new release.
> >> >
> >> > Ok thanks. I am a bit lost with versionning and compatibility.
> >> > May I have a proper install with cturtle or diamonback with the
> >> > orocos_toolchain_ros_0.2 ? Or should I only wait for next release (if
> >> > so I
> >> > would be glad to have a goal of it, with no guarantee of course, but
> >> > i'll
> >> > help my scheduling)
> >>
> >> Ruben did a new release of the orocos_toolchain_ros packages this
> >> morning. It will take some time before the software is available, as
> >> it needs to pass some tests on the ROS build farm first. It then
> >> should be available for installation when a new release is triggered
> >> at willowgarage (no idea when this will be).
> >>
> >> In the meantime you can of course work on the git repositories. We're
> >> deleting the orocos_toolchain_ros_0.2 branch and continue development
> >> on master (as they both serve the same purpose anyway). This
> >> development is diamondback based. If you work with cturtle - use the
> >> cturtle_next branch.
> >>
> >
> > as diamondback is still not installing properly on my pc I can't test it.
> >
> > In my cturtle installation I used the cturtle_next as you suggested, from
> > scratch (so no git problem), using
> > http://www.ros.org/wiki/orocos_toolchain_ros
> > and "cturtle_next" instead of cturtle
> >
> > but it is still not ok :
> >
> > ard@ard-host-v5:~/ros$ rosdep install orocos_toolchain_ros
> > Invalid manifest
> >
> file[/home/ard/ros/orocos_toolchain_ros/rtt_exercises/rtt-exercises/hello-7-deployment/manifest.xml]:
> > missing required 'license' element
> > ........... and so many others
> > ERROR: QUITTING: due to conflicting rosdep definitions, please resolve
> this
> > conflict.
> > Rules for ruby do not match:
> > ruby [/home/ard/ros/ros/rosdep.yaml]
> > ruby1.8-dev libruby1.8
> [/home/ard/ros/orocos_toolchain_ros/rosdep.yaml]
> > ard@ard-host-v5:~/ros$
> >
> >
> >
> >
> > ard@ard-host-v5:~/ros/orocos_toolchain_ros$ rosmake
> > [ rosmake ] No package specified. Building stack
> > ['orocos_toolchain_ros']
> > [ rosmake ] Packages requested are:
> > ['orocos_toolchain_ros']
> > [ rosmake ] Logging to
> > directory/home/ard/.ros/rosmake/rosmake_output-20110207-210422
> > [ rosmake ] Expanded args ['orocos_toolchain_ros'] to:
> > ['log4cpp', 'rtt_ros_integration_example', 'ocl', 'utilrb', 'typelib',
> > 'rtt', 'hello-7-deployment', 'helloworld', 'hello-2-properties',
> > 'hello-5-services', 'controller-1', 'hello-3-dataports',
> > 'hello-6-scripting', 'hello-1-task-execution', 'hello-4-operations',
> > 'utilmm', 'orogen', 'rtt_ros_integration_nav_msgs',
> 'rtt_ros_integration',
> > 'rtt_ros_param', 'rtt_ros_integration_geometry_msgs',
> > 'rtt_ros_integration_roslib_msgs', 'rtt_ros_integration_std_msgs']
> > [ rosmake ] Checking rosdeps compliance for packages
> orocos_toolchain_ros.
> > This may take a few
> > seconds.
> > Invalid manifest
> >
> file[/home/ard/ros/orocos_toolchain_ros/rtt_exercises/rtt-exercises/hello-7-deployment/manifest.xml]:
> > missing required 'license' element
> > ..................... and so many other
> > QUITTING: due to conflicting rosdep definitions, please resolve this
> > conflict.
> > Rules for ruby do not match:
> > ruby [/home/ard/ros/ros/rosdep.yaml]
> > ruby1.8-dev libruby1.8
> [/home/ard/ros/orocos_toolchain_ros/rosdep.yaml]
> > [ rosmake ] rosdep check passed all system dependencies in
> > packages
> > [ rosmake ] Starting >>>
> > tools/rospack
> > [ rosmake ] Finished <<<
> > tools/rospack
> > [ rosmake ] Starting >>>
> > 3rdparty/gtest
> > [ rosmake ] Finished <<<
> > 3rdparty/gtest
> > [ rosmake ] Starting >>>
> > core/genmsg_cpp
> > [ rosmake ] Finished <<<
> > core/genmsg_cpp
> > [rosmake-0] Starting >>> log4cpp [ make
> > ]
> > [rosmake-1] Starting >>> roslang [ make
> > ]
> > [rosmake-1] Finished <<< roslang No Makefile in package
> > roslang
> > [rosmake-1] Starting >>> roslib [ make
> > ]
> > [rosmake-1] Finished <<< roslib [PASS] [ 0.91 seconds
> > ]
> > [rosmake-1] Starting >>> xmlrpcpp [ make
> > ]
> > [rosmake-1] Finished <<< xmlrpcpp [PASS] [ 0.37 seconds
> > ]
> > [rosmake-1] Starting >>> rosconsole [ make
> > ]
> > [rosmake-1] Finished <<< rosconsole [PASS] [ 0.69 seconds
> > ]
> > [rosmake-1] Starting >>> roscpp [ make
> > ]
> > [rosmake-1] Finished <<< roscpp [PASS] [ 1.30 seconds
> > ]
> > [rosmake-1] Starting >>> rtt [ make
> > ]
> > [ rosmake ] Output from build of package log4cpp written
> > to:
> > [ 2 Active 7/45 Complete ]
> > [ rosmake ]
> >
> /home/ard/.ros/rosmake/rosmake_output-20110207-210422/log4cpp/build_output.log
> > [rosmake-0] Finished <<< log4cpp [PASS] [ 56.40 seconds ] -- WARNING: 1
> > compiler
> > warnings
> > [rosmake-0] Starting >>> rosbuild [ make
> > ]
> > [rosmake-0] Finished <<< rosbuild No Makefile in package
> > rosbuild
> > [rosmake-0] Starting >>> std_msgs [ make
> > ]
> > [rosmake-0] Finished <<< std_msgs [PASS] [ 5.61 seconds
> > ]
> > [rosmake-0] Starting >>> utilrb [ make
> > ]
> > [ rosmake ] Output from build of package utilrb written
> > to:]
> > [ 2 Active 10/45 Complete ]
> > [ rosmake ]
> >
> /home/ard/.ros/rosmake/rosmake_output-20110207-210422/utilrb/build_output.log
> > [rosmake-0] Finished <<< utilrb [PASS] [ 49.13 seconds ] -- WARNING: 1
> > compiler
> > warnings
> > [rosmake-0] Starting >>> utilmm [ make
> > ]
> > [ rosmake ] Last 40 linest: 110.4 sec ] [ utilmm: 2.5 sec
> > ]
> > [ 2 Active 11/45 Complete ]
> >
> {-------------------------------------------------------------------------------
> > if [ ! -f utilmm.md5sum ]; then echo "Error: Couldn't find md5sum file
> > utilmm.md5sum" && false; fi
> > `rospack find rosbuild`/bin/download_checkmd5.py
> >
> http://people.mech.kuleuven.be/~sbellens/orocos-toolchain/orocos-toolcha...
> > build/v2.1.0 `awk {'print $1'} utilmm.md5sum`
> > [rosbuild] Downloading
> >
> http://people.mech.kuleuven.be/~sbellens/orocos-toolchain/orocos-toolcha...
> > to build/v2.1.0...Done
> > [rosbuild] Checking md5sum on build/v2.1.0
> > touch -c build/v2.1.0
> > rm -rf build/orocos-toolchain-utilmm
> > cd build; tar xzf ../build/v2.1.0
> > cd build/orocos-toolchain-utilmm && patch -p0 < ../../utilmm.patch;
> > patching file CMakeLists.txt
> > touch build/orocos-toolchain-utilmm/unpacked
> > mkdir -p bin
> > cd build && cmake -Wdev -DCMAKE_TOOLCHAIN_FILE=`rospack find
> > rosbuild`/rostoolchain.cmake -DCMAKE_INSTALL_PREFIX=`rospack find
> > utilmm`/install ..
> > -- The C compiler identification is GNU
> > -- The CXX compiler identification is GNU
> > -- Check for working C compiler: /usr/bin/gcc
> > -- Check for working C compiler: /usr/bin/gcc -- works
> > -- Detecting C compiler ABI info
> > -- Detecting C compiler ABI info - done
> > -- Check for working CXX compiler: /usr/bin/c++
> > -- Check for working CXX compiler: /usr/bin/c++ -- works
> > -- Detecting CXX compiler ABI info
> > -- Detecting CXX compiler ABI info - done
> > [rosbuild] Building package utilmm
> > [rosbuild] Cached build flags older than manifests; calling rospack to
> get
> > flags
> > [rosbuild] Including /home/ard/ros/ros/core/roscpp/cmake/roscpp.cmake
> > [rosbuild] Including /home/ard/ros/ros/core/rospy/cmake/rospy.cmake
> > [rosbuild] Including /home/ard/ros/ros/core/roslisp/cmake/roslisp.cmake
> > -- Found The Following Boost Libraries:
> > -- unit_test_framework
> > -- Boost Version: 1.42.0
> > -- cannot find boost/graph
> > CMake Error at build/orocos-toolchain-utilmm/cmake/FindBoost.cmake:367
> > (MESSAGE):
> > Boost and/or some required components not found. Please install the
> > Boost
> > libraries AND development packages
> > Call Stack (most recent call first):
> > build/orocos-toolchain-utilmm/CMakeLists.txt:9 (FIND_PACKAGE)
>
> And do you actually have these installed? The boost dependency
> packages are defined in $(find ros)/rosdep.yaml (you can find out with
> 'rosdep where_defined boost'). I see there is no boost-graph entry for
> the debian platform. You'll have to add something like
> 'libboost-dev-graph' for your platform most probably. I'll switch to
> CTurtle and see if I can get the ruby conflict sorted out.
>

You are rigth, the OS dependencies are different from ubuntu to debian. For
debian it's a list of packages since in debian it's "all" package. So I had
to queue libboost-graph-dev in my ros/rosdep.yaml.

>
> Steven
>
> >
> >
> > -- Configuring incomplete, errors occurred!
> >
> -------------------------------------------------------------------------------}
> > [ rosmake ] Output from build of package utilmm written to:
> > [ rosmake ]
> >
> /home/ard/.ros/rosmake/rosmake_output-20110207-210422/utilmm/build_output.log
> > [rosmake-0] Finished <<< utilmm [FAIL] [ 2.55 seconds
> > ]
> > [ rosmake ] Halting due to failure in package utilmm.
> > [ rosmake ] Waiting for other threads to
> > complete.
> > [rosmake-1] Finished <<< rtt [PASS] [ 262.82 seconds
> > ]
> > [ rosmake ]
> > Results:
> > [ rosmake ] Built 13 packages with 1
> > failures.
> > [ rosmake ] Summary output to
> > directory
> > [ rosmake ]
> > /home/ard/.ros/rosmake/rosmake_output-20110207-210422
> > ard@ard-host-v5:~/ros/orocos_toolchain_ros$
> >
> >
> >
> >
> >>
> >> regards,
> >>
> >> Steven
> >>
> >> >
> >> >
> >> >>
> >> >> Steven
> >> >>
> >> >> >
> >> >> >
> >> >> >
> >> >> >>
> >> >> >>
> >> >> >>>
> >> >> >>>
> >> >> >>>>>
> >> >> >>>>> regards,
> >> >> >>>>>
> >> >> >>>>> Steven
> >> >> >>>>>
> >> >> >>>>>
> >> >> >>>>> >
> >> >> >>>>> >
> >> >> >>>>> >
> >> >> >>>>> >
> >> >> >>>>> >>
> >> >> >>>>> >> > At the end it seems to have work properly as I have this
> in
> >> >> >>>>> >> > the
> >> >> >>>>> >> > folder
> >> >> >>>>> >> > (and
> >> >> >>>>> >> > succeed a build yesterday) :
> >> >> >>>>> >> >
> >> >> >>>>> >> >
> >> >> >>>>> >> >
> >> >> >>>>> >> > ard@ard-host-v5
> :/media/DD_data/home/ard/ros/orocos_toolchain_ros$
> >> >> >>>>> >> > ls
> >> >> >>>>> >> > CMakeLists.txt env.sh ocl rosdep.yaml
> rtt_exercises
> >> >> >>>>> >> > rtt_ros_integration_example stack.xml utilmm
> >> >> >>>>> >> > env.mk Makefile orogen rtt
> >> >> >>>>> >> > rtt_ros_integration
> >> >> >>>>> >> > rtt_ros_integration_std_msgs typelib utilrb
> >> >> >>>>> >> >
> >> >> >>>>> >> >
> >> >> >>>>> >> > ard@ard-host-v5
> :/media/DD_data/home/ard/ros/orocos_toolchain_ros$
> >> >> >>>>> >> >
> >> >> >>>>> >> >
> >> >> >>>>> >> >
> >> >> >>>>> >> > _______________________________________________
> >> >> >>>>> >> > ros-users mailing list
> >> >> >>>>> >> > ros-users [..] ...
> >> >> >>>>> >> > https://code.ros.org/mailman/listinfo/ros-users
> >> >> >>>>> >> >
> >> >> >>>>> >> >
> >> >> >>>>> >> --
> >> >> >>>>> >> Orocos-Users mailing list
> >> >> >>>>> >> Orocos-Users [..] ...
> >> >> >>>>> >> http://lists.mech.kuleuven.be/mailman/listinfo/orocos-users
> >> >> >>>>> >
> >> >> >>>>> >
> >> >> >>>>> > _______________________________________________
> >> >> >>>>> > ros-users mailing list
> >> >> >>>>> > ros-users [..] ...
> >> >> >>>>> > https://code.ros.org/mailman/listinfo/ros-users
> >> >> >>>>> >
> >> >> >>>>> >
> >> >> >>>>> _______________________________________________
> >> >> >>>>> ros-users mailing list
> >> >> >>>>> ros-users [..] ...
> >> >> >>>>> https://code.ros.org/mailman/listinfo/ros-users
> >> >> >>>>
> >> >> >>>
> >> >> >>
> >> >> >
> >> >> >
> >> >> > _______________________________________________
> >> >> > ros-users mailing list
> >> >> > ros-users [..] ...
> >> >> > https://code.ros.org/mailman/listinfo/ros-users
> >> >> >
> >> >> >
> >> >> --
> >> >> Orocos-Users mailing list
> >> >> Orocos-Users [..] ...
> >> >> http://lists.mech.kuleuven.be/mailman/listinfo/orocos-users
> >> >
> >> >
> >> > _______________________________________________
> >> > ros-users mailing list
> >> > ros-users [..] ...
> >> > https://code.ros.org/mailman/listinfo/ros-users
> >> >
> >> >
> >> --
> >> Orocos-Users mailing list
> >> Orocos-Users [..] ...
> >> http://lists.mech.kuleuven.be/mailman/listinfo/orocos-users
> >
> >
> > _______________________________________________
> > ros-users mailing list
> > ros-users [..] ...
> > https://code.ros.org/mailman/listinfo/ros-users
> >
> >
> _______________________________________________
> ros-users mailing list
> ros-users [..] ...
> https://code.ros.org/mailman/listinfo/ros-users
>

[ros-users] orocos_toolchain_ros for debian

2011/2/8 Willy Lambert <lambert [dot] willy [..] ...>

>
>
> 2011/2/8 Steven Bellens <steven [dot] bellens [..] ...>
>
> 2011/2/7 Willy Lambert <lambert [dot] willy [..] ...>:
>> >
>> >
>> > 2011/2/7 Steven Bellens <steven [dot] bellens [..] ...>
>> >>
>> >> [...]
>> >>
>> >> >>
>> >> >> I've pushed a fixed for this to the orocos_toolchain_ros_0.2 branch.
>> >> >> Other branches will be updated when Ruben triggers a new release.
>> >> >
>> >> > Ok thanks. I am a bit lost with versionning and compatibility.
>> >> > May I have a proper install with cturtle or diamonback with the
>> >> > orocos_toolchain_ros_0.2 ? Or should I only wait for next release
>> (if
>> >> > so I
>> >> > would be glad to have a goal of it, with no guarantee of course, but
>> >> > i'll
>> >> > help my scheduling)
>> >>
>> >> Ruben did a new release of the orocos_toolchain_ros packages this
>> >> morning. It will take some time before the software is available, as
>> >> it needs to pass some tests on the ROS build farm first. It then
>> >> should be available for installation when a new release is triggered
>> >> at willowgarage (no idea when this will be).
>> >>
>> >> In the meantime you can of course work on the git repositories. We're
>> >> deleting the orocos_toolchain_ros_0.2 branch and continue development
>> >> on master (as they both serve the same purpose anyway). This
>> >> development is diamondback based. If you work with cturtle - use the
>> >> cturtle_next branch.
>> >>
>> >
>> > as diamondback is still not installing properly on my pc I can't test
>> it.
>> >
>> > In my cturtle installation I used the cturtle_next as you suggested,
>> from
>> > scratch (so no git problem), using
>> > http://www.ros.org/wiki/orocos_toolchain_ros
>> > and "cturtle_next" instead of cturtle
>> >
>> > but it is still not ok :
>> >
>> > ard@ard-host-v5:~/ros$ rosdep install orocos_toolchain_ros
>> > Invalid manifest
>> >
>> file[/home/ard/ros/orocos_toolchain_ros/rtt_exercises/rtt-exercises/hello-7-deployment/manifest.xml]:
>> > missing required 'license' element
>> > ........... and so many others
>> > ERROR: QUITTING: due to conflicting rosdep definitions, please resolve
>> this
>> > conflict.
>> > Rules for ruby do not match:
>> > ruby [/home/ard/ros/ros/rosdep.yaml]
>> > ruby1.8-dev libruby1.8
>> [/home/ard/ros/orocos_toolchain_ros/rosdep.yaml]
>> > ard@ard-host-v5:~/ros$
>> >
>> >
>> >
>> >
>> > ard@ard-host-v5:~/ros/orocos_toolchain_ros$ rosmake
>> > [ rosmake ] No package specified. Building stack
>> > ['orocos_toolchain_ros']
>> > [ rosmake ] Packages requested are:
>> > ['orocos_toolchain_ros']
>> > [ rosmake ] Logging to
>> > directory/home/ard/.ros/rosmake/rosmake_output-20110207-210422
>> > [ rosmake ] Expanded args ['orocos_toolchain_ros'] to:
>> > ['log4cpp', 'rtt_ros_integration_example', 'ocl', 'utilrb', 'typelib',
>> > 'rtt', 'hello-7-deployment', 'helloworld', 'hello-2-properties',
>> > 'hello-5-services', 'controller-1', 'hello-3-dataports',
>> > 'hello-6-scripting', 'hello-1-task-execution', 'hello-4-operations',
>> > 'utilmm', 'orogen', 'rtt_ros_integration_nav_msgs',
>> 'rtt_ros_integration',
>> > 'rtt_ros_param', 'rtt_ros_integration_geometry_msgs',
>> > 'rtt_ros_integration_roslib_msgs', 'rtt_ros_integration_std_msgs']
>> > [ rosmake ] Checking rosdeps compliance for packages
>> orocos_toolchain_ros.
>> > This may take a few
>> > seconds.
>> > Invalid manifest
>> >
>> file[/home/ard/ros/orocos_toolchain_ros/rtt_exercises/rtt-exercises/hello-7-deployment/manifest.xml]:
>> > missing required 'license' element
>> > ..................... and so many other
>> > QUITTING: due to conflicting rosdep definitions, please resolve this
>> > conflict.
>> > Rules for ruby do not match:
>> > ruby [/home/ard/ros/ros/rosdep.yaml]
>> > ruby1.8-dev libruby1.8
>> [/home/ard/ros/orocos_toolchain_ros/rosdep.yaml]
>> > [ rosmake ] rosdep check passed all system dependencies in
>> > packages
>> > [ rosmake ] Starting >>>
>> > tools/rospack
>> > [ rosmake ] Finished <<<
>> > tools/rospack
>> > [ rosmake ] Starting >>>
>> > 3rdparty/gtest
>> > [ rosmake ] Finished <<<
>> > 3rdparty/gtest
>> > [ rosmake ] Starting >>>
>> > core/genmsg_cpp
>> > [ rosmake ] Finished <<<
>> > core/genmsg_cpp
>> > [rosmake-0] Starting >>> log4cpp [ make
>> > ]
>> > [rosmake-1] Starting >>> roslang [ make
>> > ]
>> > [rosmake-1] Finished <<< roslang No Makefile in package
>> > roslang
>> > [rosmake-1] Starting >>> roslib [ make
>> > ]
>> > [rosmake-1] Finished <<< roslib [PASS] [ 0.91 seconds
>> > ]
>> > [rosmake-1] Starting >>> xmlrpcpp [ make
>> > ]
>> > [rosmake-1] Finished <<< xmlrpcpp [PASS] [ 0.37 seconds
>> > ]
>> > [rosmake-1] Starting >>> rosconsole [ make
>> > ]
>> > [rosmake-1] Finished <<< rosconsole [PASS] [ 0.69 seconds
>> > ]
>> > [rosmake-1] Starting >>> roscpp [ make
>> > ]
>> > [rosmake-1] Finished <<< roscpp [PASS] [ 1.30 seconds
>> > ]
>> > [rosmake-1] Starting >>> rtt [ make
>> > ]
>> > [ rosmake ] Output from build of package log4cpp written
>> > to:
>> > [ 2 Active 7/45 Complete ]
>> > [ rosmake ]
>> >
>> /home/ard/.ros/rosmake/rosmake_output-20110207-210422/log4cpp/build_output.log
>> > [rosmake-0] Finished <<< log4cpp [PASS] [ 56.40 seconds ] -- WARNING: 1
>> > compiler
>> > warnings
>> > [rosmake-0] Starting >>> rosbuild [ make
>> > ]
>> > [rosmake-0] Finished <<< rosbuild No Makefile in package
>> > rosbuild
>> > [rosmake-0] Starting >>> std_msgs [ make
>> > ]
>> > [rosmake-0] Finished <<< std_msgs [PASS] [ 5.61 seconds
>> > ]
>> > [rosmake-0] Starting >>> utilrb [ make
>> > ]
>> > [ rosmake ] Output from build of package utilrb written
>> > to:]
>> > [ 2 Active 10/45 Complete ]
>> > [ rosmake ]
>> >
>> /home/ard/.ros/rosmake/rosmake_output-20110207-210422/utilrb/build_output.log
>> > [rosmake-0] Finished <<< utilrb [PASS] [ 49.13 seconds ] -- WARNING: 1
>> > compiler
>> > warnings
>> > [rosmake-0] Starting >>> utilmm [ make
>> > ]
>> > [ rosmake ] Last 40 linest: 110.4 sec ] [ utilmm: 2.5 sec
>> > ]
>> > [ 2 Active 11/45 Complete ]
>> >
>> {-------------------------------------------------------------------------------
>> > if [ ! -f utilmm.md5sum ]; then echo "Error: Couldn't find md5sum file
>> > utilmm.md5sum" && false; fi
>> > `rospack find rosbuild`/bin/download_checkmd5.py
>> >
>> http://people.mech.kuleuven.be/~sbellens/orocos-toolchain/orocos-toolcha...
>> > build/v2.1.0 `awk {'print $1'} utilmm.md5sum`
>> > [rosbuild] Downloading
>> >
>> http://people.mech.kuleuven.be/~sbellens/orocos-toolchain/orocos-toolcha...
>> > to build/v2.1.0...Done
>> > [rosbuild] Checking md5sum on build/v2.1.0
>> > touch -c build/v2.1.0
>> > rm -rf build/orocos-toolchain-utilmm
>> > cd build; tar xzf ../build/v2.1.0
>> > cd build/orocos-toolchain-utilmm && patch -p0 < ../../utilmm.patch;
>> > patching file CMakeLists.txt
>> > touch build/orocos-toolchain-utilmm/unpacked
>> > mkdir -p bin
>> > cd build && cmake -Wdev -DCMAKE_TOOLCHAIN_FILE=`rospack find
>> > rosbuild`/rostoolchain.cmake -DCMAKE_INSTALL_PREFIX=`rospack find
>> > utilmm`/install ..
>> > -- The C compiler identification is GNU
>> > -- The CXX compiler identification is GNU
>> > -- Check for working C compiler: /usr/bin/gcc
>> > -- Check for working C compiler: /usr/bin/gcc -- works
>> > -- Detecting C compiler ABI info
>> > -- Detecting C compiler ABI info - done
>> > -- Check for working CXX compiler: /usr/bin/c++
>> > -- Check for working CXX compiler: /usr/bin/c++ -- works
>> > -- Detecting CXX compiler ABI info
>> > -- Detecting CXX compiler ABI info - done
>> > [rosbuild] Building package utilmm
>> > [rosbuild] Cached build flags older than manifests; calling rospack to
>> get
>> > flags
>> > [rosbuild] Including /home/ard/ros/ros/core/roscpp/cmake/roscpp.cmake
>> > [rosbuild] Including /home/ard/ros/ros/core/rospy/cmake/rospy.cmake
>> > [rosbuild] Including
>> /home/ard/ros/ros/core/roslisp/cmake/roslisp.cmake
>> > -- Found The Following Boost Libraries:
>> > -- unit_test_framework
>> > -- Boost Version: 1.42.0
>> > -- cannot find boost/graph
>> > CMake Error at build/orocos-toolchain-utilmm/cmake/FindBoost.cmake:367
>> > (MESSAGE):
>> > Boost and/or some required components not found. Please install the
>> > Boost
>> > libraries AND development packages
>> > Call Stack (most recent call first):
>> > build/orocos-toolchain-utilmm/CMakeLists.txt:9 (FIND_PACKAGE)
>>
>> And do you actually have these installed? The boost dependency
>> packages are defined in $(find ros)/rosdep.yaml (you can find out with
>> 'rosdep where_defined boost'). I see there is no boost-graph entry for
>> the debian platform. You'll have to add something like
>> 'libboost-dev-graph' for your platform most probably. I'll switch to
>> CTurtle and see if I can get the ruby conflict sorted out.
>>
>
> You are rigth, the OS dependencies are different from ubuntu to debian. For
> debian it's a list of packages since in debian it's "all" package. So I had
> to queue libboost-graph-dev in my ros/rosdep.yaml.
>
>
It works ! Thanks a lot

Here are some compiler warning, mainly from Orocos side I think (maybe you
already know them but anyway) :

utilrb :
/usr/bin/ld: warning: cannot find entry symbol xport-dynamic-module;
defaulting to 0000000000001990
make[1]: quittant le répertoire «
/media/DD_data/home/ard/ros/orocos_toolchain_ros/utilrb/build/orocos-toolchain-utilrb/ext
»
touch installed

typelib
[ 36%] Building CXX object
build/orocos-toolchain-typelib/bindings/ruby/CMakeFiles/typelib_ruby.dir/ext/value.o
/home/ard/ros/orocos_toolchain_ros/typelib/build/orocos-toolchain-typelib/bindings/ruby/ext/value.cc:495:
warning: ‘void type$
...
[ 56%] Building CXX object
build/orocos-toolchain-typelib/lang/cimport/CMakeFiles/typeLang_c.dir/Dictionary.o
/home/ard/ros/orocos_toolchain_ros/typelib/build/orocos-toolchain-typelib/lang/cimport/Dictionary.cc:
In member function ‘virtual int Dictionary::hash(const std::string&)’:
/home/ard/ros/orocos_toolchain_ros/typelib/build/orocos-toolchain-typelib/lang/cimport/Dictionary.cc:161:
warning: array subscript has type ‘char’
/home/ard/ros/orocos_toolchain_ros/typelib/build/orocos-toolchain-typelib/lang/cimport/Dictionary.cc:163:
warning: array subscript has type ‘char’
...
[ 68%] Building CXX object
build/orocos-toolchain-typelib/lang/cimport/CMakeFiles/typeLang_c.dir/CPPParser.o
cparser.g: In member function ‘CPPParser::TypeQualifier
CPPParser::type_qualifier()’:
cparser.g:366: warning: ‘tq’ may be used uninitialized in this function
cparser.g:366: note: ‘tq’ was declared here
cparser.g: In member function ‘CPPParser::StorageClass
CPPParser::storage_class_specifier()’:
cparser.g:359: warning: ‘sc’ may be used uninitialized in this function
cparser.g:359: note: ‘sc’ was declared here
cparser.g: In member function ‘int CPPParser::int_constant()’:
cparser.g:1212: warning: ‘value’ may be used uninitialized in this function
cparser.g:1212: note: ‘value’ was declared here
cparser.g: In member function ‘int
CPPParser::int_constant_unary_expression()’:
cparser.g:1205: warning: ‘sign’ may be used uninitialized in this function
cparser.g:1205: note: ‘sign’ was declared here
cparser.g: In member function ‘int
CPPParser::int_constant_add_expression()’:
cparser.g:1176: warning: ‘sign’ may be used uninitialized in this function
cparser.g:1176: note: ‘sign’ was declared here
cparser.g: In member function ‘void CPPParser::enumerator()’:
cparser.g:512: warning: ‘value’ may be used uninitialized in this function
cparser.g:512: note: ‘value’ was declared here
cparser.g: In member function ‘long int
CPPParser::class_specifier(CPPParser::DeclSpecifier)’:
cparser.g:462: warning: ‘ts’ may be used uninitialized in this function
cparser.g:462: note: ‘ts’ was declared here
cparser.g: In member function ‘long int
CPPParser::type_specifier(CPPParser::DeclSpecifier)’:
cparser.g:371: warning: ‘ts’ may be used uninitialized in this function
cparser.g:371: note: ‘ts’ was declared here

>
>
>
>>
>> Steven
>>
>> >
>> >
>> > -- Configuring incomplete, errors occurred!
>> >
>> -------------------------------------------------------------------------------}
>> > [ rosmake ] Output from build of package utilmm written to:
>> > [ rosmake ]
>> >
>> /home/ard/.ros/rosmake/rosmake_output-20110207-210422/utilmm/build_output.log
>> > [rosmake-0] Finished <<< utilmm [FAIL] [ 2.55 seconds
>> > ]
>> > [ rosmake ] Halting due to failure in package utilmm.
>> > [ rosmake ] Waiting for other threads to
>> > complete.
>> > [rosmake-1] Finished <<< rtt [PASS] [ 262.82 seconds
>> > ]
>> > [ rosmake ]
>> > Results:
>> > [ rosmake ] Built 13 packages with 1
>> > failures.
>> > [ rosmake ] Summary output to
>> > directory
>> > [ rosmake ]
>> > /home/ard/.ros/rosmake/rosmake_output-20110207-210422
>> > ard@ard-host-v5:~/ros/orocos_toolchain_ros$
>> >
>> >
>> >
>> >
>> >>
>> >> regards,
>> >>
>> >> Steven
>> >>
>> >> >
>> >> >
>> >> >>
>> >> >> Steven
>> >> >>
>> >> >> >
>> >> >> >
>> >> >> >
>> >> >> >>
>> >> >> >>
>> >> >> >>>
>> >> >> >>>
>> >> >> >>>>>
>> >> >> >>>>> regards,
>> >> >> >>>>>
>> >> >> >>>>> Steven
>> >> >> >>>>>
>> >> >> >>>>>
>> >> >> >>>>> >
>> >> >> >>>>> >
>> >> >> >>>>> >
>> >> >> >>>>> >
>> >> >> >>>>> >>
>> >> >> >>>>> >> > At the end it seems to have work properly as I have this
>> in
>> >> >> >>>>> >> > the
>> >> >> >>>>> >> > folder
>> >> >> >>>>> >> > (and
>> >> >> >>>>> >> > succeed a build yesterday) :
>> >> >> >>>>> >> >
>> >> >> >>>>> >> >
>> >> >> >>>>> >> >
>> >> >> >>>>> >> > ard@ard-host-v5
>> :/media/DD_data/home/ard/ros/orocos_toolchain_ros$
>> >> >> >>>>> >> > ls
>> >> >> >>>>> >> > CMakeLists.txt env.sh ocl rosdep.yaml
>> rtt_exercises
>> >> >> >>>>> >> > rtt_ros_integration_example stack.xml utilmm
>> >> >> >>>>> >> > env.mk Makefile orogen rtt
>> >> >> >>>>> >> > rtt_ros_integration
>> >> >> >>>>> >> > rtt_ros_integration_std_msgs typelib utilrb
>> >> >> >>>>> >> >
>> >> >> >>>>> >> >
>> >> >> >>>>> >> > ard@ard-host-v5
>> :/media/DD_data/home/ard/ros/orocos_toolchain_ros$
>> >> >> >>>>> >> >
>> >> >> >>>>> >> >
>> >> >> >>>>> >> >
>> >> >> >>>>> >> > _______________________________________________
>> >> >> >>>>> >> > ros-users mailing list
>> >> >> >>>>> >> > ros-users [..] ...
>> >> >> >>>>> >> > https://code.ros.org/mailman/listinfo/ros-users
>> >> >> >>>>> >> >
>> >> >> >>>>> >> >
>> >> >> >>>>> >> --
>> >> >> >>>>> >> Orocos-Users mailing list
>> >> >> >>>>> >> Orocos-Users [..] ...
>> >> >> >>>>> >>
>> http://lists.mech.kuleuven.be/mailman/listinfo/orocos-users
>> >> >> >>>>> >
>> >> >> >>>>> >
>> >> >> >>>>> > _______________________________________________
>> >> >> >>>>> > ros-users mailing list
>> >> >> >>>>> > ros-users [..] ...
>> >> >> >>>>> > https://code.ros.org/mailman/listinfo/ros-users
>> >> >> >>>>> >
>> >> >> >>>>> >
>> >> >> >>>>> _______________________________________________
>> >> >> >>>>> ros-users mailing list
>> >> >> >>>>> ros-users [..] ...
>> >> >> >>>>> https://code.ros.org/mailman/listinfo/ros-users
>> >> >> >>>>
>> >> >> >>>
>> >> >> >>
>> >> >> >
>> >> >> >
>> >> >> > _______________________________________________
>> >> >> > ros-users mailing list
>> >> >> > ros-users [..] ...
>> >> >> > https://code.ros.org/mailman/listinfo/ros-users
>> >> >> >
>> >> >> >
>> >> >> --
>> >> >> Orocos-Users mailing list
>> >> >> Orocos-Users [..] ...
>> >> >> http://lists.mech.kuleuven.be/mailman/listinfo/orocos-users
>> >> >
>> >> >
>> >> > _______________________________________________
>> >> > ros-users mailing list
>> >> > ros-users [..] ...
>> >> > https://code.ros.org/mailman/listinfo/ros-users
>> >> >
>> >> >
>> >> --
>> >> Orocos-Users mailing list
>> >> Orocos-Users [..] ...
>> >> http://lists.mech.kuleuven.be/mailman/listinfo/orocos-users
>> >
>> >
>> > _______________________________________________
>> > ros-users mailing list
>> > ros-users [..] ...
>> > https://code.ros.org/mailman/listinfo/ros-users
>> >
>> >
>> _______________________________________________
>> ros-users mailing list
>> ros-users [..] ...
>> https://code.ros.org/mailman/listinfo/ros-users
>>
>
>

[ros-users] orocos_toolchain_ros for debian

2011/2/8 Willy Lambert <lambert [dot] willy [..] ...>

>
>
> 2011/2/8 Willy Lambert <lambert [dot] willy [..] ...>
>
>
>>
>> 2011/2/8 Steven Bellens <steven [dot] bellens [..] ...>
>>
>> 2011/2/7 Willy Lambert <lambert [dot] willy [..] ...>:
>>> >
>>> >
>>> > 2011/2/7 Steven Bellens <steven [dot] bellens [..] ...>
>>> >>
>>> >> [...]
>>> >>
>>> >> >>
>>> >> >> I've pushed a fixed for this to the orocos_toolchain_ros_0.2
>>> branch.
>>> >> >> Other branches will be updated when Ruben triggers a new release.
>>> >> >
>>> >> > Ok thanks. I am a bit lost with versionning and compatibility.
>>> >> > May I have a proper install with cturtle or diamonback with the
>>> >> > orocos_toolchain_ros_0.2 ? Or should I only wait for next release
>>> (if
>>> >> > so I
>>> >> > would be glad to have a goal of it, with no guarantee of course, but
>>> >> > i'll
>>> >> > help my scheduling)
>>> >>
>>> >> Ruben did a new release of the orocos_toolchain_ros packages this
>>> >> morning. It will take some time before the software is available, as
>>> >> it needs to pass some tests on the ROS build farm first. It then
>>> >> should be available for installation when a new release is triggered
>>> >> at willowgarage (no idea when this will be).
>>> >>
>>> >> In the meantime you can of course work on the git repositories. We're
>>> >> deleting the orocos_toolchain_ros_0.2 branch and continue development
>>> >> on master (as they both serve the same purpose anyway). This
>>> >> development is diamondback based. If you work with cturtle - use the
>>> >> cturtle_next branch.
>>> >>
>>> >
>>> > as diamondback is still not installing properly on my pc I can't test
>>> it.
>>> >
>>> > In my cturtle installation I used the cturtle_next as you suggested,
>>> from
>>> > scratch (so no git problem), using
>>> > http://www.ros.org/wiki/orocos_toolchain_ros
>>> > and "cturtle_next" instead of cturtle
>>> >
>>> > but it is still not ok :
>>> >
>>> > ard@ard-host-v5:~/ros$ rosdep install orocos_toolchain_ros
>>> > Invalid manifest
>>> >
>>> file[/home/ard/ros/orocos_toolchain_ros/rtt_exercises/rtt-exercises/hello-7-deployment/manifest.xml]:
>>> > missing required 'license' element
>>> > ........... and so many others
>>> > ERROR: QUITTING: due to conflicting rosdep definitions, please resolve
>>> this
>>> > conflict.
>>> > Rules for ruby do not match:
>>> > ruby [/home/ard/ros/ros/rosdep.yaml]
>>> > ruby1.8-dev libruby1.8
>>> [/home/ard/ros/orocos_toolchain_ros/rosdep.yaml]
>>> > ard@ard-host-v5:~/ros$
>>> >
>>> >
>>> >
>>> >
>>> > ard@ard-host-v5:~/ros/orocos_toolchain_ros$ rosmake
>>> > [ rosmake ] No package specified. Building stack
>>> > ['orocos_toolchain_ros']
>>> > [ rosmake ] Packages requested are:
>>> > ['orocos_toolchain_ros']
>>> > [ rosmake ] Logging to
>>> > directory/home/ard/.ros/rosmake/rosmake_output-20110207-210422
>>> > [ rosmake ] Expanded args ['orocos_toolchain_ros'] to:
>>> > ['log4cpp', 'rtt_ros_integration_example', 'ocl', 'utilrb', 'typelib',
>>> > 'rtt', 'hello-7-deployment', 'helloworld', 'hello-2-properties',
>>> > 'hello-5-services', 'controller-1', 'hello-3-dataports',
>>> > 'hello-6-scripting', 'hello-1-task-execution', 'hello-4-operations',
>>> > 'utilmm', 'orogen', 'rtt_ros_integration_nav_msgs',
>>> 'rtt_ros_integration',
>>> > 'rtt_ros_param', 'rtt_ros_integration_geometry_msgs',
>>> > 'rtt_ros_integration_roslib_msgs', 'rtt_ros_integration_std_msgs']
>>> > [ rosmake ] Checking rosdeps compliance for packages
>>> orocos_toolchain_ros.
>>> > This may take a few
>>> > seconds.
>>> > Invalid manifest
>>> >
>>> file[/home/ard/ros/orocos_toolchain_ros/rtt_exercises/rtt-exercises/hello-7-deployment/manifest.xml]:
>>> > missing required 'license' element
>>> > ..................... and so many other
>>> > QUITTING: due to conflicting rosdep definitions, please resolve this
>>> > conflict.
>>> > Rules for ruby do not match:
>>> > ruby [/home/ard/ros/ros/rosdep.yaml]
>>> > ruby1.8-dev libruby1.8
>>> [/home/ard/ros/orocos_toolchain_ros/rosdep.yaml]
>>> > [ rosmake ] rosdep check passed all system dependencies in
>>> > packages
>>> > [ rosmake ] Starting >>>
>>> > tools/rospack
>>> > [ rosmake ] Finished <<<
>>> > tools/rospack
>>> > [ rosmake ] Starting >>>
>>> > 3rdparty/gtest
>>> > [ rosmake ] Finished <<<
>>> > 3rdparty/gtest
>>> > [ rosmake ] Starting >>>
>>> > core/genmsg_cpp
>>> > [ rosmake ] Finished <<<
>>> > core/genmsg_cpp
>>> > [rosmake-0] Starting >>> log4cpp [ make
>>> > ]
>>> > [rosmake-1] Starting >>> roslang [ make
>>> > ]
>>> > [rosmake-1] Finished <<< roslang No Makefile in package
>>> > roslang
>>> > [rosmake-1] Starting >>> roslib [ make
>>> > ]
>>> > [rosmake-1] Finished <<< roslib [PASS] [ 0.91 seconds
>>> > ]
>>> > [rosmake-1] Starting >>> xmlrpcpp [ make
>>> > ]
>>> > [rosmake-1] Finished <<< xmlrpcpp [PASS] [ 0.37 seconds
>>> > ]
>>> > [rosmake-1] Starting >>> rosconsole [ make
>>> > ]
>>> > [rosmake-1] Finished <<< rosconsole [PASS] [ 0.69 seconds
>>> > ]
>>> > [rosmake-1] Starting >>> roscpp [ make
>>> > ]
>>> > [rosmake-1] Finished <<< roscpp [PASS] [ 1.30 seconds
>>> > ]
>>> > [rosmake-1] Starting >>> rtt [ make
>>> > ]
>>> > [ rosmake ] Output from build of package log4cpp written
>>> > to:
>>> > [ 2 Active 7/45 Complete ]
>>> > [ rosmake ]
>>> >
>>> /home/ard/.ros/rosmake/rosmake_output-20110207-210422/log4cpp/build_output.log
>>> > [rosmake-0] Finished <<< log4cpp [PASS] [ 56.40 seconds ] -- WARNING: 1
>>> > compiler
>>> > warnings
>>> > [rosmake-0] Starting >>> rosbuild [ make
>>> > ]
>>> > [rosmake-0] Finished <<< rosbuild No Makefile in package
>>> > rosbuild
>>> > [rosmake-0] Starting >>> std_msgs [ make
>>> > ]
>>> > [rosmake-0] Finished <<< std_msgs [PASS] [ 5.61 seconds
>>> > ]
>>> > [rosmake-0] Starting >>> utilrb [ make
>>> > ]
>>> > [ rosmake ] Output from build of package utilrb written
>>> > to:]
>>> > [ 2 Active 10/45 Complete ]
>>> > [ rosmake ]
>>> >
>>> /home/ard/.ros/rosmake/rosmake_output-20110207-210422/utilrb/build_output.log
>>> > [rosmake-0] Finished <<< utilrb [PASS] [ 49.13 seconds ] -- WARNING: 1
>>> > compiler
>>> > warnings
>>> > [rosmake-0] Starting >>> utilmm [ make
>>> > ]
>>> > [ rosmake ] Last 40 linest: 110.4 sec ] [ utilmm: 2.5 sec
>>> > ]
>>> > [ 2 Active 11/45 Complete ]
>>> >
>>> {-------------------------------------------------------------------------------
>>> > if [ ! -f utilmm.md5sum ]; then echo "Error: Couldn't find md5sum
>>> file
>>> > utilmm.md5sum" && false; fi
>>> > `rospack find rosbuild`/bin/download_checkmd5.py
>>> >
>>> http://people.mech.kuleuven.be/~sbellens/orocos-toolchain/orocos-toolcha...
>>> > build/v2.1.0 `awk {'print $1'} utilmm.md5sum`
>>> > [rosbuild] Downloading
>>> >
>>> http://people.mech.kuleuven.be/~sbellens/orocos-toolchain/orocos-toolcha...
>>> > to build/v2.1.0...Done
>>> > [rosbuild] Checking md5sum on build/v2.1.0
>>> > touch -c build/v2.1.0
>>> > rm -rf build/orocos-toolchain-utilmm
>>> > cd build; tar xzf ../build/v2.1.0
>>> > cd build/orocos-toolchain-utilmm && patch -p0 < ../../utilmm.patch;
>>> > patching file CMakeLists.txt
>>> > touch build/orocos-toolchain-utilmm/unpacked
>>> > mkdir -p bin
>>> > cd build && cmake -Wdev -DCMAKE_TOOLCHAIN_FILE=`rospack find
>>> > rosbuild`/rostoolchain.cmake -DCMAKE_INSTALL_PREFIX=`rospack find
>>> > utilmm`/install ..
>>> > -- The C compiler identification is GNU
>>> > -- The CXX compiler identification is GNU
>>> > -- Check for working C compiler: /usr/bin/gcc
>>> > -- Check for working C compiler: /usr/bin/gcc -- works
>>> > -- Detecting C compiler ABI info
>>> > -- Detecting C compiler ABI info - done
>>> > -- Check for working CXX compiler: /usr/bin/c++
>>> > -- Check for working CXX compiler: /usr/bin/c++ -- works
>>> > -- Detecting CXX compiler ABI info
>>> > -- Detecting CXX compiler ABI info - done
>>> > [rosbuild] Building package utilmm
>>> > [rosbuild] Cached build flags older than manifests; calling rospack
>>> to get
>>> > flags
>>> > [rosbuild] Including /home/ard/ros/ros/core/roscpp/cmake/roscpp.cmake
>>> > [rosbuild] Including /home/ard/ros/ros/core/rospy/cmake/rospy.cmake
>>> > [rosbuild] Including
>>> /home/ard/ros/ros/core/roslisp/cmake/roslisp.cmake
>>> > -- Found The Following Boost Libraries:
>>> > -- unit_test_framework
>>> > -- Boost Version: 1.42.0
>>> > -- cannot find boost/graph
>>> > CMake Error at
>>> build/orocos-toolchain-utilmm/cmake/FindBoost.cmake:367
>>> > (MESSAGE):
>>> > Boost and/or some required components not found. Please install
>>> the
>>> > Boost
>>> > libraries AND development packages
>>> > Call Stack (most recent call first):
>>> > build/orocos-toolchain-utilmm/CMakeLists.txt:9 (FIND_PACKAGE)
>>>
>>> And do you actually have these installed? The boost dependency
>>> packages are defined in $(find ros)/rosdep.yaml (you can find out with
>>> 'rosdep where_defined boost'). I see there is no boost-graph entry for
>>> the debian platform. You'll have to add something like
>>> 'libboost-dev-graph' for your platform most probably. I'll switch to
>>> CTurtle and see if I can get the ruby conflict sorted out.
>>>
>>
>> You are rigth, the OS dependencies are different from ubuntu to debian.
>> For debian it's a list of packages since in debian it's "all" package. So I
>> had to queue libboost-graph-dev in my ros/rosdep.yaml.
>>
>>
> It works ! Thanks a lot
>
>
Is it done on purpose that env.sh doesn't contain ocl binary paths (for
accessing deployer for example) ? It is the behavior of the standard Orocos
toolchain

>
> Here are some compiler warning, mainly from Orocos side I think (maybe you
> already know them but anyway) :
>
> utilrb :
> /usr/bin/ld: warning: cannot find entry symbol xport-dynamic-module;
> defaulting to 0000000000001990
> make[1]: quittant le répertoire «
> /media/DD_data/home/ard/ros/orocos_toolchain_ros/utilrb/build/orocos-toolchain-utilrb/ext
> »
> touch installed
>
>
> typelib
> [ 36%] Building CXX object
> build/orocos-toolchain-typelib/bindings/ruby/CMakeFiles/typelib_ruby.dir/ext/value.o
> /home/ard/ros/orocos_toolchain_ros/typelib/build/orocos-toolchain-typelib/bindings/ruby/ext/value.cc:495:
> warning: ‘void type$
> ...
> [ 56%] Building CXX object
> build/orocos-toolchain-typelib/lang/cimport/CMakeFiles/typeLang_c.dir/Dictionary.o
> /home/ard/ros/orocos_toolchain_ros/typelib/build/orocos-toolchain-typelib/lang/cimport/Dictionary.cc:
> In member function ‘virtual int Dictionary::hash(const std::string&)’:
> /home/ard/ros/orocos_toolchain_ros/typelib/build/orocos-toolchain-typelib/lang/cimport/Dictionary.cc:161:
> warning: array subscript has type ‘char’
> /home/ard/ros/orocos_toolchain_ros/typelib/build/orocos-toolchain-typelib/lang/cimport/Dictionary.cc:163:
> warning: array subscript has type ‘char’
> ...
> [ 68%] Building CXX object
> build/orocos-toolchain-typelib/lang/cimport/CMakeFiles/typeLang_c.dir/CPPParser.o
> cparser.g: In member function ‘CPPParser::TypeQualifier
> CPPParser::type_qualifier()’:
> cparser.g:366: warning: ‘tq’ may be used uninitialized in this function
> cparser.g:366: note: ‘tq’ was declared here
> cparser.g: In member function ‘CPPParser::StorageClass
> CPPParser::storage_class_specifier()’:
> cparser.g:359: warning: ‘sc’ may be used uninitialized in this function
> cparser.g:359: note: ‘sc’ was declared here
> cparser.g: In member function ‘int CPPParser::int_constant()’:
> cparser.g:1212: warning: ‘value’ may be used uninitialized in this function
> cparser.g:1212: note: ‘value’ was declared here
> cparser.g: In member function ‘int
> CPPParser::int_constant_unary_expression()’:
> cparser.g:1205: warning: ‘sign’ may be used uninitialized in this function
> cparser.g:1205: note: ‘sign’ was declared here
> cparser.g: In member function ‘int
> CPPParser::int_constant_add_expression()’:
> cparser.g:1176: warning: ‘sign’ may be used uninitialized in this function
> cparser.g:1176: note: ‘sign’ was declared here
> cparser.g: In member function ‘void CPPParser::enumerator()’:
> cparser.g:512: warning: ‘value’ may be used uninitialized in this function
> cparser.g:512: note: ‘value’ was declared here
> cparser.g: In member function ‘long int
> CPPParser::class_specifier(CPPParser::DeclSpecifier)’:
> cparser.g:462: warning: ‘ts’ may be used uninitialized in this function
> cparser.g:462: note: ‘ts’ was declared here
> cparser.g: In member function ‘long int
> CPPParser::type_specifier(CPPParser::DeclSpecifier)’:
> cparser.g:371: warning: ‘ts’ may be used uninitialized in this function
> cparser.g:371: note: ‘ts’ was declared here
>
>
>
>
>
>
>
>
>>
>>
>>
>>>
>>> Steven
>>>
>>> >
>>> >
>>> > -- Configuring incomplete, errors occurred!
>>> >
>>> -------------------------------------------------------------------------------}
>>> > [ rosmake ] Output from build of package utilmm written to:
>>> > [ rosmake ]
>>> >
>>> /home/ard/.ros/rosmake/rosmake_output-20110207-210422/utilmm/build_output.log
>>> > [rosmake-0] Finished <<< utilmm [FAIL] [ 2.55 seconds
>>> > ]
>>> > [ rosmake ] Halting due to failure in package utilmm.
>>> > [ rosmake ] Waiting for other threads to
>>> > complete.
>>> > [rosmake-1] Finished <<< rtt [PASS] [ 262.82 seconds
>>> > ]
>>> > [ rosmake ]
>>> > Results:
>>> > [ rosmake ] Built 13 packages with 1
>>> > failures.
>>> > [ rosmake ] Summary output to
>>> > directory
>>> > [ rosmake ]
>>> > /home/ard/.ros/rosmake/rosmake_output-20110207-210422
>>> > ard@ard-host-v5:~/ros/orocos_toolchain_ros$
>>> >
>>> >
>>> >
>>> >
>>> >>
>>> >> regards,
>>> >>
>>> >> Steven
>>> >>
>>> >> >
>>> >> >
>>> >> >>
>>> >> >> Steven
>>> >> >>
>>> >> >> >
>>> >> >> >
>>> >> >> >
>>> >> >> >>
>>> >> >> >>
>>> >> >> >>>
>>> >> >> >>>
>>> >> >> >>>>>
>>> >> >> >>>>> regards,
>>> >> >> >>>>>
>>> >> >> >>>>> Steven
>>> >> >> >>>>>
>>> >> >> >>>>>
>>> >> >> >>>>> >
>>> >> >> >>>>> >
>>> >> >> >>>>> >
>>> >> >> >>>>> >
>>> >> >> >>>>> >>
>>> >> >> >>>>> >> > At the end it seems to have work properly as I have this
>>> in
>>> >> >> >>>>> >> > the
>>> >> >> >>>>> >> > folder
>>> >> >> >>>>> >> > (and
>>> >> >> >>>>> >> > succeed a build yesterday) :
>>> >> >> >>>>> >> >
>>> >> >> >>>>> >> >
>>> >> >> >>>>> >> >
>>> >> >> >>>>> >> > ard@ard-host-v5
>>> :/media/DD_data/home/ard/ros/orocos_toolchain_ros$
>>> >> >> >>>>> >> > ls
>>> >> >> >>>>> >> > CMakeLists.txt env.sh ocl rosdep.yaml
>>> rtt_exercises
>>> >> >> >>>>> >> > rtt_ros_integration_example stack.xml utilmm
>>> >> >> >>>>> >> > env.mk Makefile orogen rtt
>>> >> >> >>>>> >> > rtt_ros_integration
>>> >> >> >>>>> >> > rtt_ros_integration_std_msgs typelib utilrb
>>> >> >> >>>>> >> >
>>> >> >> >>>>> >> >
>>> >> >> >>>>> >> > ard@ard-host-v5
>>> :/media/DD_data/home/ard/ros/orocos_toolchain_ros$
>>> >> >> >>>>> >> >
>>> >> >> >>>>> >> >
>>> >> >> >>>>> >> >
>>> >> >> >>>>> >> > _______________________________________________
>>> >> >> >>>>> >> > ros-users mailing list
>>> >> >> >>>>> >> > ros-users [..] ...
>>> >> >> >>>>> >> > https://code.ros.org/mailman/listinfo/ros-users
>>> >> >> >>>>> >> >
>>> >> >> >>>>> >> >
>>> >> >> >>>>> >> --
>>> >> >> >>>>> >> Orocos-Users mailing list
>>> >> >> >>>>> >> Orocos-Users [..] ...
>>> >> >> >>>>> >>
>>> http://lists.mech.kuleuven.be/mailman/listinfo/orocos-users
>>> >> >> >>>>> >
>>> >> >> >>>>> >
>>> >> >> >>>>> > _______________________________________________
>>> >> >> >>>>> > ros-users mailing list
>>> >> >> >>>>> > ros-users [..] ...
>>> >> >> >>>>> > https://code.ros.org/mailman/listinfo/ros-users
>>> >> >> >>>>> >
>>> >> >> >>>>> >
>>> >> >> >>>>> _______________________________________________
>>> >> >> >>>>> ros-users mailing list
>>> >> >> >>>>> ros-users [..] ...
>>> >> >> >>>>> https://code.ros.org/mailman/listinfo/ros-users
>>> >> >> >>>>
>>> >> >> >>>
>>> >> >> >>
>>> >> >> >
>>> >> >> >
>>> >> >> > _______________________________________________
>>> >> >> > ros-users mailing list
>>> >> >> > ros-users [..] ...
>>> >> >> > https://code.ros.org/mailman/listinfo/ros-users
>>> >> >> >
>>> >> >> >
>>> >> >> --
>>> >> >> Orocos-Users mailing list
>>> >> >> Orocos-Users [..] ...
>>> >> >> http://lists.mech.kuleuven.be/mailman/listinfo/orocos-users
>>> >> >
>>> >> >
>>> >> > _______________________________________________
>>> >> > ros-users mailing list
>>> >> > ros-users [..] ...
>>> >> > https://code.ros.org/mailman/listinfo/ros-users
>>> >> >
>>> >> >
>>> >> --
>>> >> Orocos-Users mailing list
>>> >> Orocos-Users [..] ...
>>> >> http://lists.mech.kuleuven.be/mailman/listinfo/orocos-users
>>> >
>>> >
>>> > _______________________________________________
>>> > ros-users mailing list
>>> > ros-users [..] ...
>>> > https://code.ros.org/mailman/listinfo/ros-users
>>> >
>>> >
>>> _______________________________________________
>>> ros-users mailing list
>>> ros-users [..] ...
>>> https://code.ros.org/mailman/listinfo/ros-users
>>>
>>
>>
>

[ros-users] orocos_toolchain_ros for debian

2011/2/8 Willy Lambert <lambert [dot] willy [..] ...>:
>
>
> 2011/2/8 Willy Lambert <lambert [dot] willy [..] ...>
>>
>>
>> 2011/2/8 Willy Lambert <lambert [dot] willy [..] ...>
>>>
>>>
>>> 2011/2/8 Steven Bellens <steven [dot] bellens [..] ...>
>>>>
>>>> 2011/2/7 Willy Lambert <lambert [dot] willy [..] ...>:
>>>> >
>>>> >
>>>> > 2011/2/7 Steven Bellens <steven [dot] bellens [..] ...>
>>>> >>
>>>> >> [...]
>>>> >>
>>>> >> >>
>>>> >> >> I've pushed a fixed for this to the orocos_toolchain_ros_0.2
>>>> >> >> branch.
>>>> >> >> Other branches will be updated when Ruben triggers a new release.
>>>> >> >
>>>> >> > Ok thanks. I am a bit lost with versionning and compatibility.
>>>> >> > May I have a proper install with cturtle or diamonback with the
>>>> >> > orocos_toolchain_ros_0.2  ? Or should I only wait for next release
>>>> >> > (if
>>>> >> > so I
>>>> >> > would be glad to have a goal of it, with no guarantee of course,
>>>> >> > but
>>>> >> > i'll
>>>> >> > help my scheduling)
>>>> >>
>>>> >> Ruben did a new release of the orocos_toolchain_ros packages this
>>>> >> morning. It will take some time before the software is available, as
>>>> >> it needs to pass some tests on the ROS build farm first. It then
>>>> >> should be available for installation when a new release is triggered
>>>> >> at willowgarage (no idea when this will be).
>>>> >>
>>>> >> In the meantime you can of course work on the git repositories. We're
>>>> >> deleting the orocos_toolchain_ros_0.2 branch and continue development
>>>> >> on master (as they both serve the same purpose anyway). This
>>>> >> development is diamondback based. If you work with cturtle - use the
>>>> >> cturtle_next branch.
>>>> >>
>>>> >
>>>> > as diamondback is still not installing properly on my pc I can't test
>>>> > it.
>>>> >
>>>> > In my cturtle installation I used the cturtle_next as you suggested,
>>>> > from
>>>> > scratch (so no git problem), using
>>>> > http://www.ros.org/wiki/orocos_toolchain_ros
>>>> > and "cturtle_next" instead of cturtle
>>>> >
>>>> >  but it is still not ok :
>>>> >
>>>> > ard@ard-host-v5:~/ros$ rosdep install orocos_toolchain_ros
>>>> > Invalid manifest
>>>> >
>>>> > file[/home/ard/ros/orocos_toolchain_ros/rtt_exercises/rtt-exercises/hello-7-deployment/manifest.xml]:
>>>> > missing required 'license' element
>>>> > ........... and so many others
>>>> > ERROR: QUITTING: due to conflicting rosdep definitions, please resolve
>>>> > this
>>>> > conflict.
>>>> > Rules for ruby do not match:
>>>> >     ruby [/home/ard/ros/ros/rosdep.yaml]
>>>> >     ruby1.8-dev libruby1.8
>>>> > [/home/ard/ros/orocos_toolchain_ros/rosdep.yaml]
>>>> > ard@ard-host-v5:~/ros$
>>>> >
>>>> >
>>>> >
>>>> >
>>>> > ard@ard-host-v5:~/ros/orocos_toolchain_ros$ rosmake
>>>> > [ rosmake ] No package specified.  Building stack
>>>> > ['orocos_toolchain_ros']
>>>> > [ rosmake ] Packages requested are:
>>>> > ['orocos_toolchain_ros']
>>>> > [ rosmake ] Logging to
>>>> > directory/home/ard/.ros/rosmake/rosmake_output-20110207-210422
>>>> > [ rosmake ] Expanded args ['orocos_toolchain_ros'] to:
>>>> > ['log4cpp', 'rtt_ros_integration_example', 'ocl', 'utilrb', 'typelib',
>>>> > 'rtt', 'hello-7-deployment', 'helloworld', 'hello-2-properties',
>>>> > 'hello-5-services', 'controller-1', 'hello-3-dataports',
>>>> > 'hello-6-scripting', 'hello-1-task-execution', 'hello-4-operations',
>>>> > 'utilmm', 'orogen', 'rtt_ros_integration_nav_msgs',
>>>> > 'rtt_ros_integration',
>>>> > 'rtt_ros_param', 'rtt_ros_integration_geometry_msgs',
>>>> > 'rtt_ros_integration_roslib_msgs', 'rtt_ros_integration_std_msgs']
>>>> > [ rosmake ] Checking rosdeps compliance for packages
>>>> > orocos_toolchain_ros.
>>>> > This may take a few
>>>> > seconds.
>>>> > Invalid manifest
>>>> >
>>>> > file[/home/ard/ros/orocos_toolchain_ros/rtt_exercises/rtt-exercises/hello-7-deployment/manifest.xml]:
>>>> > missing required 'license' element
>>>> >  ..................... and so many other
>>>> > QUITTING: due to conflicting rosdep definitions, please resolve this
>>>> > conflict.
>>>> > Rules for ruby do not match:
>>>> >     ruby [/home/ard/ros/ros/rosdep.yaml]
>>>> >     ruby1.8-dev libruby1.8
>>>> > [/home/ard/ros/orocos_toolchain_ros/rosdep.yaml]
>>>> > [ rosmake ] rosdep check passed all system dependencies in
>>>> > packages
>>>> > [ rosmake ] Starting >>>
>>>> > tools/rospack
>>>> > [ rosmake ] Finished <<<
>>>> > tools/rospack
>>>> > [ rosmake ] Starting >>>
>>>> > 3rdparty/gtest
>>>> > [ rosmake ] Finished <<<
>>>> > 3rdparty/gtest
>>>> > [ rosmake ] Starting >>>
>>>> > core/genmsg_cpp
>>>> > [ rosmake ] Finished <<<
>>>> > core/genmsg_cpp
>>>> > [rosmake-0] Starting >>> log4cpp [ make
>>>> > ]
>>>> > [rosmake-1] Starting >>> roslang [ make
>>>> > ]
>>>> > [rosmake-1] Finished <<< roslang  No Makefile in package
>>>> > roslang
>>>> > [rosmake-1] Starting >>> roslib [ make
>>>> > ]
>>>> > [rosmake-1] Finished <<< roslib [PASS] [ 0.91 seconds
>>>> > ]
>>>> > [rosmake-1] Starting >>> xmlrpcpp [ make
>>>> > ]
>>>> > [rosmake-1] Finished <<< xmlrpcpp [PASS] [ 0.37 seconds
>>>> > ]
>>>> > [rosmake-1] Starting >>> rosconsole [ make
>>>> > ]
>>>> > [rosmake-1] Finished <<< rosconsole [PASS] [ 0.69 seconds
>>>> > ]
>>>> > [rosmake-1] Starting >>> roscpp [ make
>>>> > ]
>>>> > [rosmake-1] Finished <<< roscpp [PASS] [ 1.30 seconds
>>>> > ]
>>>> > [rosmake-1] Starting >>> rtt [ make
>>>> > ]
>>>> > [ rosmake ] Output from build of package log4cpp written
>>>> > to:
>>>> > [ 2 Active 7/45 Complete ]
>>>> > [ rosmake ]
>>>> >
>>>> > /home/ard/.ros/rosmake/rosmake_output-20110207-210422/log4cpp/build_output.log
>>>> > [rosmake-0] Finished <<< log4cpp [PASS] [ 56.40 seconds ] -- WARNING:
>>>> > 1
>>>> > compiler
>>>> > warnings
>>>> > [rosmake-0] Starting >>> rosbuild [ make
>>>> > ]
>>>> > [rosmake-0] Finished <<< rosbuild  No Makefile in package
>>>> > rosbuild
>>>> > [rosmake-0] Starting >>> std_msgs [ make
>>>> > ]
>>>> > [rosmake-0] Finished <<< std_msgs [PASS] [ 5.61 seconds
>>>> > ]
>>>> > [rosmake-0] Starting >>> utilrb [ make
>>>> > ]
>>>> > [ rosmake ] Output from build of package utilrb written
>>>> > to:]
>>>> > [ 2 Active 10/45 Complete ]
>>>> > [ rosmake ]
>>>> >
>>>> > /home/ard/.ros/rosmake/rosmake_output-20110207-210422/utilrb/build_output.log
>>>> > [rosmake-0] Finished <<< utilrb [PASS] [ 49.13 seconds ] -- WARNING: 1
>>>> > compiler
>>>> > warnings
>>>> > [rosmake-0] Starting >>> utilmm [ make
>>>> > ]
>>>> > [ rosmake ] Last 40 linest: 110.4 sec ] [ utilmm: 2.5 sec
>>>> > ]
>>>> > [ 2 Active 11/45 Complete ]
>>>> >
>>>> > {-------------------------------------------------------------------------------
>>>> >   if [ ! -f utilmm.md5sum ]; then echo "Error: Couldn't find md5sum
>>>> > file
>>>> > utilmm.md5sum" && false; fi
>>>> >   `rospack find rosbuild`/bin/download_checkmd5.py
>>>> >
>>>> > http://people.mech.kuleuven.be/~sbellens/orocos-toolchain/orocos-toolcha...
>>>> > build/v2.1.0 `awk {'print $1'} utilmm.md5sum`
>>>> >   [rosbuild] Downloading
>>>> >
>>>> > http://people.mech.kuleuven.be/~sbellens/orocos-toolchain/orocos-toolcha...
>>>> > to build/v2.1.0...Done
>>>> >   [rosbuild] Checking md5sum on build/v2.1.0
>>>> >   touch -c build/v2.1.0
>>>> >   rm -rf build/orocos-toolchain-utilmm
>>>> >   cd build; tar xzf ../build/v2.1.0
>>>> >   cd build/orocos-toolchain-utilmm &&  patch -p0 < ../../utilmm.patch;
>>>> >   patching file CMakeLists.txt
>>>> >   touch build/orocos-toolchain-utilmm/unpacked
>>>> >   mkdir -p bin
>>>> >   cd build && cmake -Wdev -DCMAKE_TOOLCHAIN_FILE=`rospack find
>>>> > rosbuild`/rostoolchain.cmake -DCMAKE_INSTALL_PREFIX=`rospack find
>>>> > utilmm`/install ..
>>>> >   -- The C compiler identification is GNU
>>>> >   -- The CXX compiler identification is GNU
>>>> >   -- Check for working C compiler: /usr/bin/gcc
>>>> >   -- Check for working C compiler: /usr/bin/gcc -- works
>>>> >   -- Detecting C compiler ABI info
>>>> >   -- Detecting C compiler ABI info - done
>>>> >   -- Check for working CXX compiler: /usr/bin/c++
>>>> >   -- Check for working CXX compiler: /usr/bin/c++ -- works
>>>> >   -- Detecting CXX compiler ABI info
>>>> >   -- Detecting CXX compiler ABI info - done
>>>> >   [rosbuild] Building package utilmm
>>>> >   [rosbuild] Cached build flags older than manifests; calling rospack
>>>> > to get
>>>> > flags
>>>> >   [rosbuild] Including
>>>> > /home/ard/ros/ros/core/roscpp/cmake/roscpp.cmake
>>>> >   [rosbuild] Including /home/ard/ros/ros/core/rospy/cmake/rospy.cmake
>>>> >   [rosbuild] Including
>>>> > /home/ard/ros/ros/core/roslisp/cmake/roslisp.cmake
>>>> >   -- Found The Following Boost Libraries:
>>>> >   --   unit_test_framework
>>>> >   -- Boost Version: 1.42.0
>>>> >   -- cannot find boost/graph
>>>> >   CMake Error at
>>>> > build/orocos-toolchain-utilmm/cmake/FindBoost.cmake:367
>>>> > (MESSAGE):
>>>> >     Boost and/or some required components not found.  Please install
>>>> > the
>>>> > Boost
>>>> >     libraries AND development packages
>>>> >   Call Stack (most recent call first):
>>>> >     build/orocos-toolchain-utilmm/CMakeLists.txt:9 (FIND_PACKAGE)
>>>>
>>>> And do you actually have these installed? The boost dependency
>>>> packages are defined in $(find ros)/rosdep.yaml (you can find out with
>>>> 'rosdep where_defined boost'). I see there is no boost-graph entry for
>>>> the debian platform. You'll have to add something like
>>>> 'libboost-dev-graph' for your platform most probably. I'll switch to
>>>> CTurtle and see if I can get the ruby conflict sorted out.
>>>
>>> You are rigth, the OS dependencies are different from ubuntu to debian.
>>> For debian it's a list of packages since in debian it's "all" package. So I
>>> had to queue libboost-graph-dev in my ros/rosdep.yaml.
>>>
>>
>> It works ! Thanks a lot
>>
>
> Is it done on purpose that env.sh doesn't contain ocl binary paths (for
> accessing deployer for example) ? It is the behavior of the standard Orocos
> toolchain

The standard way to run executables in ROS packages is with rosrun, e.g;

rosrun ocl deployer-gnulinux

Steven

>
>
>
>>
>> Here are some compiler warning, mainly from Orocos side I think (maybe you
>> already know them but anyway) :
>>
>> utilrb :
>> /usr/bin/ld: warning: cannot find entry symbol xport-dynamic-module;
>> defaulting to 0000000000001990
>> make[1]: quittant le répertoire «
>> /media/DD_data/home/ard/ros/orocos_toolchain_ros/utilrb/build/orocos-toolchain-utilrb/ext
>> »
>> touch installed
>>
>>
>> typelib
>> [ 36%] Building CXX object
>> build/orocos-toolchain-typelib/bindings/ruby/CMakeFiles/typelib_ruby.dir/ext/value.o
>>
>> /home/ard/ros/orocos_toolchain_ros/typelib/build/orocos-toolchain-typelib/bindings/ruby/ext/value.cc:495:
>> warning: ‘void type$
>> ...
>> [ 56%] Building CXX object
>> build/orocos-toolchain-typelib/lang/cimport/CMakeFiles/typeLang_c.dir/Dictionary.o
>>
>> /home/ard/ros/orocos_toolchain_ros/typelib/build/orocos-toolchain-typelib/lang/cimport/Dictionary.cc:
>> In member function ‘virtual int Dictionary::hash(const std::string&)’:
>>
>> /home/ard/ros/orocos_toolchain_ros/typelib/build/orocos-toolchain-typelib/lang/cimport/Dictionary.cc:161:
>> warning: array subscript has type ‘char’
>>
>> /home/ard/ros/orocos_toolchain_ros/typelib/build/orocos-toolchain-typelib/lang/cimport/Dictionary.cc:163:
>> warning: array subscript has type ‘char’
>> ...
>> [ 68%] Building CXX object
>> build/orocos-toolchain-typelib/lang/cimport/CMakeFiles/typeLang_c.dir/CPPParser.o
>> cparser.g: In member function ‘CPPParser::TypeQualifier
>> CPPParser::type_qualifier()’:
>> cparser.g:366: warning: ‘tq’ may be used uninitialized in this function
>> cparser.g:366: note: ‘tq’ was declared here
>> cparser.g: In member function ‘CPPParser::StorageClass
>> CPPParser::storage_class_specifier()’:
>> cparser.g:359: warning: ‘sc’ may be used uninitialized in this function
>> cparser.g:359: note: ‘sc’ was declared here
>> cparser.g: In member function ‘int CPPParser::int_constant()’:
>> cparser.g:1212: warning: ‘value’ may be used uninitialized in this
>> function
>> cparser.g:1212: note: ‘value’ was declared here
>> cparser.g: In member function ‘int
>> CPPParser::int_constant_unary_expression()’:
>> cparser.g:1205: warning: ‘sign’ may be used uninitialized in this function
>> cparser.g:1205: note: ‘sign’ was declared here
>> cparser.g: In member function ‘int
>> CPPParser::int_constant_add_expression()’:
>> cparser.g:1176: warning: ‘sign’ may be used uninitialized in this function
>> cparser.g:1176: note: ‘sign’ was declared here
>> cparser.g: In member function ‘void CPPParser::enumerator()’:
>> cparser.g:512: warning: ‘value’ may be used uninitialized in this function
>> cparser.g:512: note: ‘value’ was declared here
>> cparser.g: In member function ‘long int
>> CPPParser::class_specifier(CPPParser::DeclSpecifier)’:
>> cparser.g:462: warning: ‘ts’ may be used uninitialized in this function
>> cparser.g:462: note: ‘ts’ was declared here
>> cparser.g: In member function ‘long int
>> CPPParser::type_specifier(CPPParser::DeclSpecifier)’:
>> cparser.g:371: warning: ‘ts’ may be used uninitialized in this function
>> cparser.g:371: note: ‘ts’ was declared here
>>
>>
>>
>>
>>
>>
>>
>>>
>>>
>>>>
>>>> Steven
>>>>
>>>> >
>>>> >
>>>> >   -- Configuring incomplete, errors occurred!
>>>> >
>>>> > -------------------------------------------------------------------------------}
>>>> > [ rosmake ] Output from build of package utilmm written to:
>>>> > [ rosmake ]
>>>> >
>>>> > /home/ard/.ros/rosmake/rosmake_output-20110207-210422/utilmm/build_output.log
>>>> > [rosmake-0] Finished <<< utilmm [FAIL] [ 2.55 seconds
>>>> > ]
>>>> > [ rosmake ] Halting due to failure in package utilmm.
>>>> > [ rosmake ] Waiting for other threads to
>>>> > complete.
>>>> > [rosmake-1] Finished <<< rtt [PASS] [ 262.82 seconds
>>>> > ]
>>>> > [ rosmake ]
>>>> > Results:
>>>> > [ rosmake ] Built 13 packages with 1
>>>> > failures.
>>>> > [ rosmake ] Summary output to
>>>> > directory
>>>> > [ rosmake ]
>>>> > /home/ard/.ros/rosmake/rosmake_output-20110207-210422
>>>> > ard@ard-host-v5:~/ros/orocos_toolchain_ros$
>>>> >
>>>> >
>>>> >
>>>> >
>>>> >>
>>>> >> regards,
>>>> >>
>>>> >> Steven
>>>> >>
>>>> >> >
>>>> >> >
>>>> >> >>
>>>> >> >> Steven
>>>> >> >>
>>>> >> >> >
>>>> >> >> >
>>>> >> >> >
>>>> >> >> >>
>>>> >> >> >>
>>>> >> >> >>>
>>>> >> >> >>>
>>>> >> >> >>>>>
>>>> >> >> >>>>> regards,
>>>> >> >> >>>>>
>>>> >> >> >>>>> Steven
>>>> >> >> >>>>>
>>>> >> >> >>>>>
>>>> >> >> >>>>> >
>>>> >> >> >>>>> >
>>>> >> >> >>>>> >
>>>> >> >> >>>>> >
>>>> >> >> >>>>> >>
>>>> >> >> >>>>> >> > At the end it seems to have work properly as I have
>>>> >> >> >>>>> >> > this in
>>>> >> >> >>>>> >> > the
>>>> >> >> >>>>> >> > folder
>>>> >> >> >>>>> >> > (and
>>>> >> >> >>>>> >> > succeed a build yesterday) :
>>>> >> >> >>>>> >> >
>>>> >> >> >>>>> >> >
>>>> >> >> >>>>> >> >
>>>> >> >> >>>>> >> >
>>>> >> >> >>>>> >> > ard@ard-host-v5:/media/DD_data/home/ard/ros/orocos_toolchain_ros$
>>>> >> >> >>>>> >> > ls
>>>> >> >> >>>>> >> > CMakeLists.txt  env.sh    ocl     rosdep.yaml
>>>> >> >> >>>>> >> > rtt_exercises
>>>> >> >> >>>>> >> > rtt_ros_integration_example   stack.xml  utilmm
>>>> >> >> >>>>> >> > env.mk          Makefile  orogen  rtt
>>>> >> >> >>>>> >> > rtt_ros_integration
>>>> >> >> >>>>> >> > rtt_ros_integration_std_msgs  typelib    utilrb
>>>> >> >> >>>>> >> >
>>>> >> >> >>>>> >> >
>>>> >> >> >>>>> >> >
>>>> >> >> >>>>> >> > ard@ard-host-v5:/media/DD_data/home/ard/ros/orocos_toolchain_ros$
>>>> >> >> >>>>> >> >
>>>> >> >> >>>>> >> >
>>>> >> >> >>>>> >> >
>>>> >> >> >>>>> >> > _______________________________________________
>>>> >> >> >>>>> >> > ros-users mailing list
>>>> >> >> >>>>> >> > ros-users [..] ...
>>>> >> >> >>>>> >> > https://code.ros.org/mailman/listinfo/ros-users
>>>> >> >> >>>>> >> >
>>>> >> >> >>>>> >> >
>>>> >> >> >>>>> >> --
>>>> >> >> >>>>> >> Orocos-Users mailing list
>>>> >> >> >>>>> >> Orocos-Users [..] ...
>>>> >> >> >>>>> >>
>>>> >> >> >>>>> >> http://lists.mech.kuleuven.be/mailman/listinfo/orocos-users
>>>> >> >> >>>>> >
>>>> >> >> >>>>> >
>>>> >> >> >>>>> > _______________________________________________
>>>> >> >> >>>>> > ros-users mailing list
>>>> >> >> >>>>> > ros-users [..] ...
>>>> >> >> >>>>> > https://code.ros.org/mailman/listinfo/ros-users
>>>> >> >> >>>>> >
>>>> >> >> >>>>> >
>>>> >> >> >>>>> _______________________________________________
>>>> >> >> >>>>> ros-users mailing list
>>>> >> >> >>>>> ros-users [..] ...
>>>> >> >> >>>>> https://code.ros.org/mailman/listinfo/ros-users
>>>> >> >> >>>>
>>>> >> >> >>>
>>>> >> >> >>
>>>> >> >> >
>>>> >> >> >
>>>> >> >> > _______________________________________________
>>>> >> >> > ros-users mailing list
>>>> >> >> > ros-users [..] ...
>>>> >> >> > https://code.ros.org/mailman/listinfo/ros-users
>>>> >> >> >
>>>> >> >> >
>>>> >> >> --
>>>> >> >> Orocos-Users mailing list
>>>> >> >> Orocos-Users [..] ...
>>>> >> >> http://lists.mech.kuleuven.be/mailman/listinfo/orocos-users
>>>> >> >
>>>> >> >
>>>> >> > _______________________________________________
>>>> >> > ros-users mailing list
>>>> >> > ros-users [..] ...
>>>> >> > https://code.ros.org/mailman/listinfo/ros-users
>>>> >> >
>>>> >> >
>>>> >> --
>>>> >> Orocos-Users mailing list
>>>> >> Orocos-Users [..] ...
>>>> >> http://lists.mech.kuleuven.be/mailman/listinfo/orocos-users
>>>> >
>>>> >
>>>> > _______________________________________________
>>>> > ros-users mailing list
>>>> > ros-users [..] ...
>>>> > https://code.ros.org/mailman/listinfo/ros-users
>>>> >
>>>> >
>>>> _______________________________________________
>>>> ros-users mailing list
>>>> ros-users [..] ...
>>>> https://code.ros.org/mailman/listinfo/ros-users
>>>
>>
>
>
> _______________________________________________
> ros-users mailing list
> ros-users [..] ...
> https://code.ros.org/mailman/listinfo/ros-users
>
>

[ros-users] orocos_toolchain_ros for debian

2011/2/8 Steven Bellens <steven [dot] bellens [..] ...>

> 2011/2/8 Willy Lambert <lambert [dot] willy [..] ...>:
> >
> >
> > 2011/2/8 Willy Lambert <lambert [dot] willy [..] ...>
> >>
> >>
> >> 2011/2/8 Willy Lambert <lambert [dot] willy [..] ...>
> >>>
> >>>
> >>> 2011/2/8 Steven Bellens <steven [dot] bellens [..] ...>
> >>>>
> >>>> 2011/2/7 Willy Lambert <lambert [dot] willy [..] ...>:
> >>>> >
> >>>> >
> >>>> > 2011/2/7 Steven Bellens <steven [dot] bellens [..] ...>
> >>>> >>
> >>>> >> [...]
> >>>> >>
> >>>> >> >>
> >>>> >> >> I've pushed a fixed for this to the orocos_toolchain_ros_0.2
> >>>> >> >> branch.
> >>>> >> >> Other branches will be updated when Ruben triggers a new
> release.
> >>>> >> >
> >>>> >> > Ok thanks. I am a bit lost with versionning and compatibility.
> >>>> >> > May I have a proper install with cturtle or diamonback with the
> >>>> >> > orocos_toolchain_ros_0.2 ? Or should I only wait for next
> release
> >>>> >> > (if
> >>>> >> > so I
> >>>> >> > would be glad to have a goal of it, with no guarantee of course,
> >>>> >> > but
> >>>> >> > i'll
> >>>> >> > help my scheduling)
> >>>> >>
> >>>> >> Ruben did a new release of the orocos_toolchain_ros packages this
> >>>> >> morning. It will take some time before the software is available,
> as
> >>>> >> it needs to pass some tests on the ROS build farm first. It then
> >>>> >> should be available for installation when a new release is
> triggered
> >>>> >> at willowgarage (no idea when this will be).
> >>>> >>
> >>>> >> In the meantime you can of course work on the git repositories.
> We're
> >>>> >> deleting the orocos_toolchain_ros_0.2 branch and continue
> development
> >>>> >> on master (as they both serve the same purpose anyway). This
> >>>> >> development is diamondback based. If you work with cturtle - use
> the
> >>>> >> cturtle_next branch.
> >>>> >>
> >>>> >
> >>>> > as diamondback is still not installing properly on my pc I can't
> test
> >>>> > it.
> >>>> >
> >>>> > In my cturtle installation I used the cturtle_next as you suggested,
> >>>> > from
> >>>> > scratch (so no git problem), using
> >>>> > http://www.ros.org/wiki/orocos_toolchain_ros
> >>>> > and "cturtle_next" instead of cturtle
> >>>> >
> >>>> > but it is still not ok :
> >>>> >
> >>>> > ard@ard-host-v5:~/ros$ rosdep install orocos_toolchain_ros
> >>>> > Invalid manifest
> >>>> >
> >>>> >
> file[/home/ard/ros/orocos_toolchain_ros/rtt_exercises/rtt-exercises/hello-7-deployment/manifest.xml]:
> >>>> > missing required 'license' element
> >>>> > ........... and so many others
> >>>> > ERROR: QUITTING: due to conflicting rosdep definitions, please
> resolve
> >>>> > this
> >>>> > conflict.
> >>>> > Rules for ruby do not match:
> >>>> > ruby [/home/ard/ros/ros/rosdep.yaml]
> >>>> > ruby1.8-dev libruby1.8
> >>>> > [/home/ard/ros/orocos_toolchain_ros/rosdep.yaml]
> >>>> > ard@ard-host-v5:~/ros$
> >>>> >
> >>>> >
> >>>> >
> >>>> >
> >>>> > ard@ard-host-v5:~/ros/orocos_toolchain_ros$ rosmake
> >>>> > [ rosmake ] No package specified. Building stack
> >>>> > ['orocos_toolchain_ros']
> >>>> > [ rosmake ] Packages requested are:
> >>>> > ['orocos_toolchain_ros']
> >>>> > [ rosmake ] Logging to
> >>>> > directory/home/ard/.ros/rosmake/rosmake_output-20110207-210422
> >>>> > [ rosmake ] Expanded args ['orocos_toolchain_ros'] to:
> >>>> > ['log4cpp', 'rtt_ros_integration_example', 'ocl', 'utilrb',
> 'typelib',
> >>>> > 'rtt', 'hello-7-deployment', 'helloworld', 'hello-2-properties',
> >>>> > 'hello-5-services', 'controller-1', 'hello-3-dataports',
> >>>> > 'hello-6-scripting', 'hello-1-task-execution', 'hello-4-operations',
> >>>> > 'utilmm', 'orogen', 'rtt_ros_integration_nav_msgs',
> >>>> > 'rtt_ros_integration',
> >>>> > 'rtt_ros_param', 'rtt_ros_integration_geometry_msgs',
> >>>> > 'rtt_ros_integration_roslib_msgs', 'rtt_ros_integration_std_msgs']
> >>>> > [ rosmake ] Checking rosdeps compliance for packages
> >>>> > orocos_toolchain_ros.
> >>>> > This may take a few
> >>>> > seconds.
> >>>> > Invalid manifest
> >>>> >
> >>>> >
> file[/home/ard/ros/orocos_toolchain_ros/rtt_exercises/rtt-exercises/hello-7-deployment/manifest.xml]:
> >>>> > missing required 'license' element
> >>>> > ..................... and so many other
> >>>> > QUITTING: due to conflicting rosdep definitions, please resolve this
> >>>> > conflict.
> >>>> > Rules for ruby do not match:
> >>>> > ruby [/home/ard/ros/ros/rosdep.yaml]
> >>>> > ruby1.8-dev libruby1.8
> >>>> > [/home/ard/ros/orocos_toolchain_ros/rosdep.yaml]
> >>>> > [ rosmake ] rosdep check passed all system dependencies in
> >>>> > packages
> >>>> > [ rosmake ] Starting >>>
> >>>> > tools/rospack
> >>>> > [ rosmake ] Finished <<<
> >>>> > tools/rospack
> >>>> > [ rosmake ] Starting >>>
> >>>> > 3rdparty/gtest
> >>>> > [ rosmake ] Finished <<<
> >>>> > 3rdparty/gtest
> >>>> > [ rosmake ] Starting >>>
> >>>> > core/genmsg_cpp
> >>>> > [ rosmake ] Finished <<<
> >>>> > core/genmsg_cpp
> >>>> > [rosmake-0] Starting >>> log4cpp [ make
> >>>> > ]
> >>>> > [rosmake-1] Starting >>> roslang [ make
> >>>> > ]
> >>>> > [rosmake-1] Finished <<< roslang No Makefile in package
> >>>> > roslang
> >>>> > [rosmake-1] Starting >>> roslib [ make
> >>>> > ]
> >>>> > [rosmake-1] Finished <<< roslib [PASS] [ 0.91 seconds
> >>>> > ]
> >>>> > [rosmake-1] Starting >>> xmlrpcpp [ make
> >>>> > ]
> >>>> > [rosmake-1] Finished <<< xmlrpcpp [PASS] [ 0.37 seconds
> >>>> > ]
> >>>> > [rosmake-1] Starting >>> rosconsole [ make
> >>>> > ]
> >>>> > [rosmake-1] Finished <<< rosconsole [PASS] [ 0.69 seconds
> >>>> > ]
> >>>> > [rosmake-1] Starting >>> roscpp [ make
> >>>> > ]
> >>>> > [rosmake-1] Finished <<< roscpp [PASS] [ 1.30 seconds
> >>>> > ]
> >>>> > [rosmake-1] Starting >>> rtt [ make
> >>>> > ]
> >>>> > [ rosmake ] Output from build of package log4cpp written
> >>>> > to:
> >>>> > [ 2 Active 7/45 Complete ]
> >>>> > [ rosmake ]
> >>>> >
> >>>> >
> /home/ard/.ros/rosmake/rosmake_output-20110207-210422/log4cpp/build_output.log
> >>>> > [rosmake-0] Finished <<< log4cpp [PASS] [ 56.40 seconds ] --
> WARNING:
> >>>> > 1
> >>>> > compiler
> >>>> > warnings
> >>>> > [rosmake-0] Starting >>> rosbuild [ make
> >>>> > ]
> >>>> > [rosmake-0] Finished <<< rosbuild No Makefile in package
> >>>> > rosbuild
> >>>> > [rosmake-0] Starting >>> std_msgs [ make
> >>>> > ]
> >>>> > [rosmake-0] Finished <<< std_msgs [PASS] [ 5.61 seconds
> >>>> > ]
> >>>> > [rosmake-0] Starting >>> utilrb [ make
> >>>> > ]
> >>>> > [ rosmake ] Output from build of package utilrb written
> >>>> > to:]
> >>>> > [ 2 Active 10/45 Complete ]
> >>>> > [ rosmake ]
> >>>> >
> >>>> >
> /home/ard/.ros/rosmake/rosmake_output-20110207-210422/utilrb/build_output.log
> >>>> > [rosmake-0] Finished <<< utilrb [PASS] [ 49.13 seconds ] -- WARNING:
> 1
> >>>> > compiler
> >>>> > warnings
> >>>> > [rosmake-0] Starting >>> utilmm [ make
> >>>> > ]
> >>>> > [ rosmake ] Last 40 linest: 110.4 sec ] [ utilmm: 2.5 sec
> >>>> > ]
> >>>> > [ 2 Active 11/45 Complete ]
> >>>> >
> >>>> >
> {-------------------------------------------------------------------------------
> >>>> > if [ ! -f utilmm.md5sum ]; then echo "Error: Couldn't find md5sum
> >>>> > file
> >>>> > utilmm.md5sum" && false; fi
> >>>> > `rospack find rosbuild`/bin/download_checkmd5.py
> >>>> >
> >>>> >
> http://people.mech.kuleuven.be/~sbellens/orocos-toolchain/orocos-toolcha...
> >>>> > build/v2.1.0 `awk {'print $1'} utilmm.md5sum`
> >>>> > [rosbuild] Downloading
> >>>> >
> >>>> >
> http://people.mech.kuleuven.be/~sbellens/orocos-toolchain/orocos-toolcha...
> >>>> > to build/v2.1.0...Done
> >>>> > [rosbuild] Checking md5sum on build/v2.1.0
> >>>> > touch -c build/v2.1.0
> >>>> > rm -rf build/orocos-toolchain-utilmm
> >>>> > cd build; tar xzf ../build/v2.1.0
> >>>> > cd build/orocos-toolchain-utilmm && patch -p0 <
> ../../utilmm.patch;
> >>>> > patching file CMakeLists.txt
> >>>> > touch build/orocos-toolchain-utilmm/unpacked
> >>>> > mkdir -p bin
> >>>> > cd build && cmake -Wdev -DCMAKE_TOOLCHAIN_FILE=`rospack find
> >>>> > rosbuild`/rostoolchain.cmake -DCMAKE_INSTALL_PREFIX=`rospack find
> >>>> > utilmm`/install ..
> >>>> > -- The C compiler identification is GNU
> >>>> > -- The CXX compiler identification is GNU
> >>>> > -- Check for working C compiler: /usr/bin/gcc
> >>>> > -- Check for working C compiler: /usr/bin/gcc -- works
> >>>> > -- Detecting C compiler ABI info
> >>>> > -- Detecting C compiler ABI info - done
> >>>> > -- Check for working CXX compiler: /usr/bin/c++
> >>>> > -- Check for working CXX compiler: /usr/bin/c++ -- works
> >>>> > -- Detecting CXX compiler ABI info
> >>>> > -- Detecting CXX compiler ABI info - done
> >>>> > [rosbuild] Building package utilmm
> >>>> > [rosbuild] Cached build flags older than manifests; calling
> rospack
> >>>> > to get
> >>>> > flags
> >>>> > [rosbuild] Including
> >>>> > /home/ard/ros/ros/core/roscpp/cmake/roscpp.cmake
> >>>> > [rosbuild] Including
> /home/ard/ros/ros/core/rospy/cmake/rospy.cmake
> >>>> > [rosbuild] Including
> >>>> > /home/ard/ros/ros/core/roslisp/cmake/roslisp.cmake
> >>>> > -- Found The Following Boost Libraries:
> >>>> > -- unit_test_framework
> >>>> > -- Boost Version: 1.42.0
> >>>> > -- cannot find boost/graph
> >>>> > CMake Error at
> >>>> > build/orocos-toolchain-utilmm/cmake/FindBoost.cmake:367
> >>>> > (MESSAGE):
> >>>> > Boost and/or some required components not found. Please install
> >>>> > the
> >>>> > Boost
> >>>> > libraries AND development packages
> >>>> > Call Stack (most recent call first):
> >>>> > build/orocos-toolchain-utilmm/CMakeLists.txt:9 (FIND_PACKAGE)
> >>>>
> >>>> And do you actually have these installed? The boost dependency
> >>>> packages are defined in $(find ros)/rosdep.yaml (you can find out with
> >>>> 'rosdep where_defined boost'). I see there is no boost-graph entry for
> >>>> the debian platform. You'll have to add something like
> >>>> 'libboost-dev-graph' for your platform most probably. I'll switch to
> >>>> CTurtle and see if I can get the ruby conflict sorted out.
> >>>
> >>> You are rigth, the OS dependencies are different from ubuntu to debian.
> >>> For debian it's a list of packages since in debian it's "all" package.
> So I
> >>> had to queue libboost-graph-dev in my ros/rosdep.yaml.
> >>>
> >>
> >> It works ! Thanks a lot
> >>
> >
> > Is it done on purpose that env.sh doesn't contain ocl binary paths (for
> > accessing deployer for example) ? It is the behavior of the standard
> Orocos
> > toolchain
>
> The standard way to run executables in ROS packages is with rosrun, e.g;
>
> rosrun ocl deployer-gnulinux
>

Oh yes ! I still don't have the ROS reflexes :)

>
> Steven
>
> >
> >
> >
> >>
> >> Here are some compiler warning, mainly from Orocos side I think (maybe
> you
> >> already know them but anyway) :
> >>
> >> utilrb :
> >> /usr/bin/ld: warning: cannot find entry symbol xport-dynamic-module;
> >> defaulting to 0000000000001990
> >> make[1]: quittant le répertoire «
> >>
> /media/DD_data/home/ard/ros/orocos_toolchain_ros/utilrb/build/orocos-toolchain-utilrb/ext
> >> »
> >> touch installed
> >>
> >>
> >> typelib
> >> [ 36%] Building CXX object
> >>
> build/orocos-toolchain-typelib/bindings/ruby/CMakeFiles/typelib_ruby.dir/ext/value.o
> >>
> >>
> /home/ard/ros/orocos_toolchain_ros/typelib/build/orocos-toolchain-typelib/bindings/ruby/ext/value.cc:495:
> >> warning: ‘void type$
> >> ...
> >> [ 56%] Building CXX object
> >>
> build/orocos-toolchain-typelib/lang/cimport/CMakeFiles/typeLang_c.dir/Dictionary.o
> >>
> >>
> /home/ard/ros/orocos_toolchain_ros/typelib/build/orocos-toolchain-typelib/lang/cimport/Dictionary.cc:
> >> In member function ‘virtual int Dictionary::hash(const std::string&)’:
> >>
> >>
> /home/ard/ros/orocos_toolchain_ros/typelib/build/orocos-toolchain-typelib/lang/cimport/Dictionary.cc:161:
> >> warning: array subscript has type ‘char’
> >>
> >>
> /home/ard/ros/orocos_toolchain_ros/typelib/build/orocos-toolchain-typelib/lang/cimport/Dictionary.cc:163:
> >> warning: array subscript has type ‘char’
> >> ...
> >> [ 68%] Building CXX object
> >>
> build/orocos-toolchain-typelib/lang/cimport/CMakeFiles/typeLang_c.dir/CPPParser.o
> >> cparser.g: In member function ‘CPPParser::TypeQualifier
> >> CPPParser::type_qualifier()’:
> >> cparser.g:366: warning: ‘tq’ may be used uninitialized in this function
> >> cparser.g:366: note: ‘tq’ was declared here
> >> cparser.g: In member function ‘CPPParser::StorageClass
> >> CPPParser::storage_class_specifier()’:
> >> cparser.g:359: warning: ‘sc’ may be used uninitialized in this function
> >> cparser.g:359: note: ‘sc’ was declared here
> >> cparser.g: In member function ‘int CPPParser::int_constant()’:
> >> cparser.g:1212: warning: ‘value’ may be used uninitialized in this
> >> function
> >> cparser.g:1212: note: ‘value’ was declared here
> >> cparser.g: In member function ‘int
> >> CPPParser::int_constant_unary_expression()’:
> >> cparser.g:1205: warning: ‘sign’ may be used uninitialized in this
> function
> >> cparser.g:1205: note: ‘sign’ was declared here
> >> cparser.g: In member function ‘int
> >> CPPParser::int_constant_add_expression()’:
> >> cparser.g:1176: warning: ‘sign’ may be used uninitialized in this
> function
> >> cparser.g:1176: note: ‘sign’ was declared here
> >> cparser.g: In member function ‘void CPPParser::enumerator()’:
> >> cparser.g:512: warning: ‘value’ may be used uninitialized in this
> function
> >> cparser.g:512: note: ‘value’ was declared here
> >> cparser.g: In member function ‘long int
> >> CPPParser::class_specifier(CPPParser::DeclSpecifier)’:
> >> cparser.g:462: warning: ‘ts’ may be used uninitialized in this function
> >> cparser.g:462: note: ‘ts’ was declared here
> >> cparser.g: In member function ‘long int
> >> CPPParser::type_specifier(CPPParser::DeclSpecifier)’:
> >> cparser.g:371: warning: ‘ts’ may be used uninitialized in this function
> >> cparser.g:371: note: ‘ts’ was declared here
> >>
> >>
> >>
> >>
> >>
> >>
> >>
> >>>
> >>>
> >>>>
> >>>> Steven
> >>>>
> >>>> >
> >>>> >
> >>>> > -- Configuring incomplete, errors occurred!
> >>>> >
> >>>> >
> -------------------------------------------------------------------------------}
> >>>> > [ rosmake ] Output from build of package utilmm written to:
> >>>> > [ rosmake ]
> >>>> >
> >>>> >
> /home/ard/.ros/rosmake/rosmake_output-20110207-210422/utilmm/build_output.log
> >>>> > [rosmake-0] Finished <<< utilmm [FAIL] [ 2.55 seconds
> >>>> > ]
> >>>> > [ rosmake ] Halting due to failure in package utilmm.
> >>>> > [ rosmake ] Waiting for other threads to
> >>>> > complete.
> >>>> > [rosmake-1] Finished <<< rtt [PASS] [ 262.82 seconds
> >>>> > ]
> >>>> > [ rosmake ]
> >>>> > Results:
> >>>> > [ rosmake ] Built 13 packages with 1
> >>>> > failures.
> >>>> > [ rosmake ] Summary output to
> >>>> > directory
> >>>> > [ rosmake ]
> >>>> > /home/ard/.ros/rosmake/rosmake_output-20110207-210422
> >>>> > ard@ard-host-v5:~/ros/orocos_toolchain_ros$
> >>>> >
> >>>> >
> >>>> >
> >>>> >
> >>>> >>
> >>>> >> regards,
> >>>> >>
> >>>> >> Steven
> >>>> >>
> >>>> >> >
> >>>> >> >
> >>>> >> >>
> >>>> >> >> Steven
> >>>> >> >>
> >>>> >> >> >
> >>>> >> >> >
> >>>> >> >> >
> >>>> >> >> >>
> >>>> >> >> >>
> >>>> >> >> >>>
> >>>> >> >> >>>
> >>>> >> >> >>>>>
> >>>> >> >> >>>>> regards,
> >>>> >> >> >>>>>
> >>>> >> >> >>>>> Steven
> >>>> >> >> >>>>>
> >>>> >> >> >>>>>
> >>>> >> >> >>>>> >
> >>>> >> >> >>>>> >
> >>>> >> >> >>>>> >
> >>>> >> >> >>>>> >
> >>>> >> >> >>>>> >>
> >>>> >> >> >>>>> >> > At the end it seems to have work properly as I have
> >>>> >> >> >>>>> >> > this in
> >>>> >> >> >>>>> >> > the
> >>>> >> >> >>>>> >> > folder
> >>>> >> >> >>>>> >> > (and
> >>>> >> >> >>>>> >> > succeed a build yesterday) :
> >>>> >> >> >>>>> >> >
> >>>> >> >> >>>>> >> >
> >>>> >> >> >>>>> >> >
> >>>> >> >> >>>>> >> >
> >>>> >> >> >>>>> >> > ard@ard-host-v5
> :/media/DD_data/home/ard/ros/orocos_toolchain_ros$
> >>>> >> >> >>>>> >> > ls
> >>>> >> >> >>>>> >> > CMakeLists.txt env.sh ocl rosdep.yaml
> >>>> >> >> >>>>> >> > rtt_exercises
> >>>> >> >> >>>>> >> > rtt_ros_integration_example stack.xml utilmm
> >>>> >> >> >>>>> >> > env.mk Makefile orogen rtt
> >>>> >> >> >>>>> >> > rtt_ros_integration
> >>>> >> >> >>>>> >> > rtt_ros_integration_std_msgs typelib utilrb
> >>>> >> >> >>>>> >> >
> >>>> >> >> >>>>> >> >
> >>>> >> >> >>>>> >> >
> >>>> >> >> >>>>> >> > ard@ard-host-v5
> :/media/DD_data/home/ard/ros/orocos_toolchain_ros$
> >>>> >> >> >>>>> >> >
> >>>> >> >> >>>>> >> >
> >>>> >> >> >>>>> >> >
> >>>> >> >> >>>>> >> > _______________________________________________
> >>>> >> >> >>>>> >> > ros-users mailing list
> >>>> >> >> >>>>> >> > ros-users [..] ...
> >>>> >> >> >>>>> >> > https://code.ros.org/mailman/listinfo/ros-users
> >>>> >> >> >>>>> >> >
> >>>> >> >> >>>>> >> >
> >>>> >> >> >>>>> >> --
> >>>> >> >> >>>>> >> Orocos-Users mailing list
> >>>> >> >> >>>>> >> Orocos-Users [..] ...
> >>>> >> >> >>>>> >>
> >>>> >> >> >>>>> >>
> http://lists.mech.kuleuven.be/mailman/listinfo/orocos-users
> >>>> >> >> >>>>> >
> >>>> >> >> >>>>> >
> >>>> >> >> >>>>> > _______________________________________________
> >>>> >> >> >>>>> > ros-users mailing list
> >>>> >> >> >>>>> > ros-users [..] ...
> >>>> >> >> >>>>> > https://code.ros.org/mailman/listinfo/ros-users
> >>>> >> >> >>>>> >
> >>>> >> >> >>>>> >
> >>>> >> >> >>>>> _______________________________________________
> >>>> >> >> >>>>> ros-users mailing list
> >>>> >> >> >>>>> ros-users [..] ...
> >>>> >> >> >>>>> https://code.ros.org/mailman/listinfo/ros-users
> >>>> >> >> >>>>
> >>>> >> >> >>>
> >>>> >> >> >>
> >>>> >> >> >
> >>>> >> >> >
> >>>> >> >> > _______________________________________________
> >>>> >> >> > ros-users mailing list
> >>>> >> >> > ros-users [..] ...
> >>>> >> >> > https://code.ros.org/mailman/listinfo/ros-users
> >>>> >> >> >
> >>>> >> >> >
> >>>> >> >> --
> >>>> >> >> Orocos-Users mailing list
> >>>> >> >> Orocos-Users [..] ...
> >>>> >> >> http://lists.mech.kuleuven.be/mailman/listinfo/orocos-users
> >>>> >> >
> >>>> >> >
> >>>> >> > _______________________________________________
> >>>> >> > ros-users mailing list
> >>>> >> > ros-users [..] ...
> >>>> >> > https://code.ros.org/mailman/listinfo/ros-users
> >>>> >> >
> >>>> >> >
> >>>> >> --
> >>>> >> Orocos-Users mailing list
> >>>> >> Orocos-Users [..] ...
> >>>> >> http://lists.mech.kuleuven.be/mailman/listinfo/orocos-users
> >>>> >
> >>>> >
> >>>> > _______________________________________________
> >>>> > ros-users mailing list
> >>>> > ros-users [..] ...
> >>>> > https://code.ros.org/mailman/listinfo/ros-users
> >>>> >
> >>>> >
> >>>> _______________________________________________
> >>>> ros-users mailing list
> >>>> ros-users [..] ...
> >>>> https://code.ros.org/mailman/listinfo/ros-users
> >>>
> >>
> >
> >
> > _______________________________________________
> > ros-users mailing list
> > ros-users [..] ...
> > https://code.ros.org/mailman/listinfo/ros-users
> >
> >
> _______________________________________________
> ros-users mailing list
> ros-users [..] ...
> https://code.ros.org/mailman/listinfo/ros-users
>

[ros-users] orocos_toolchain_ros for debian

2011/2/8 Willy Lambert <lambert [dot] willy [..] ...>

>
>
> 2011/2/8 Steven Bellens <steven [dot] bellens [..] ...>
>
>> 2011/2/8 Willy Lambert <lambert [dot] willy [..] ...>:
>> >
>> >
>> > 2011/2/8 Willy Lambert <lambert [dot] willy [..] ...>
>> >>
>> >>
>> >> 2011/2/8 Willy Lambert <lambert [dot] willy [..] ...>
>> >>>
>> >>>
>> >>> 2011/2/8 Steven Bellens <steven [dot] bellens [..] ...>
>> >>>>
>> >>>> 2011/2/7 Willy Lambert <lambert [dot] willy [..] ...>:
>> >>>> >
>> >>>> >
>> >>>> > 2011/2/7 Steven Bellens <steven [dot] bellens [..] ...>
>> >>>> >>
>> >>>> >> [...]
>> >>>> >>
>> >>>> >> >>
>> >>>> >> >> I've pushed a fixed for this to the orocos_toolchain_ros_0.2
>> >>>> >> >> branch.
>> >>>> >> >> Other branches will be updated when Ruben triggers a new
>> release.
>> >>>> >> >
>> >>>> >> > Ok thanks. I am a bit lost with versionning and compatibility.
>> >>>> >> > May I have a proper install with cturtle or diamonback with the
>> >>>> >> > orocos_toolchain_ros_0.2 ? Or should I only wait for next
>> release
>> >>>> >> > (if
>> >>>> >> > so I
>> >>>> >> > would be glad to have a goal of it, with no guarantee of course,
>> >>>> >> > but
>> >>>> >> > i'll
>> >>>> >> > help my scheduling)
>> >>>> >>
>> >>>> >> Ruben did a new release of the orocos_toolchain_ros packages this
>> >>>> >> morning. It will take some time before the software is available,
>> as
>> >>>> >> it needs to pass some tests on the ROS build farm first. It then
>> >>>> >> should be available for installation when a new release is
>> triggered
>> >>>> >> at willowgarage (no idea when this will be).
>> >>>> >>
>> >>>> >> In the meantime you can of course work on the git repositories.
>> We're
>> >>>> >> deleting the orocos_toolchain_ros_0.2 branch and continue
>> development
>> >>>> >> on master (as they both serve the same purpose anyway). This
>> >>>> >> development is diamondback based. If you work with cturtle - use
>> the
>> >>>> >> cturtle_next branch.
>> >>>> >>
>> >>>> >
>> >>>> > as diamondback is still not installing properly on my pc I can't
>> test
>> >>>> > it.
>> >>>> >
>> >>>> > In my cturtle installation I used the cturtle_next as you
>> suggested,
>> >>>> > from
>> >>>> > scratch (so no git problem), using
>> >>>> > http://www.ros.org/wiki/orocos_toolchain_ros
>> >>>> > and "cturtle_next" instead of cturtle
>> >>>> >
>> >>>> > but it is still not ok :
>> >>>> >
>> >>>> > ard@ard-host-v5:~/ros$ rosdep install orocos_toolchain_ros
>> >>>> > Invalid manifest
>> >>>> >
>> >>>> >
>> file[/home/ard/ros/orocos_toolchain_ros/rtt_exercises/rtt-exercises/hello-7-deployment/manifest.xml]:
>> >>>> > missing required 'license' element
>> >>>> > ........... and so many others
>> >>>> > ERROR: QUITTING: due to conflicting rosdep definitions, please
>> resolve
>> >>>> > this
>> >>>> > conflict.
>> >>>> > Rules for ruby do not match:
>> >>>> > ruby [/home/ard/ros/ros/rosdep.yaml]
>> >>>> > ruby1.8-dev libruby1.8
>> >>>> > [/home/ard/ros/orocos_toolchain_ros/rosdep.yaml]
>> >>>> > ard@ard-host-v5:~/ros$
>> >>>> >
>> >>>> >
>> >>>> >
>> >>>> >
>> >>>> > ard@ard-host-v5:~/ros/orocos_toolchain_ros$ rosmake
>> >>>> > [ rosmake ] No package specified. Building stack
>> >>>> > ['orocos_toolchain_ros']
>> >>>> > [ rosmake ] Packages requested are:
>> >>>> > ['orocos_toolchain_ros']
>> >>>> > [ rosmake ] Logging to
>> >>>> > directory/home/ard/.ros/rosmake/rosmake_output-20110207-210422
>> >>>> > [ rosmake ] Expanded args ['orocos_toolchain_ros'] to:
>> >>>> > ['log4cpp', 'rtt_ros_integration_example', 'ocl', 'utilrb',
>> 'typelib',
>> >>>> > 'rtt', 'hello-7-deployment', 'helloworld', 'hello-2-properties',
>> >>>> > 'hello-5-services', 'controller-1', 'hello-3-dataports',
>> >>>> > 'hello-6-scripting', 'hello-1-task-execution',
>> 'hello-4-operations',
>> >>>> > 'utilmm', 'orogen', 'rtt_ros_integration_nav_msgs',
>> >>>> > 'rtt_ros_integration',
>> >>>> > 'rtt_ros_param', 'rtt_ros_integration_geometry_msgs',
>> >>>> > 'rtt_ros_integration_roslib_msgs', 'rtt_ros_integration_std_msgs']
>> >>>> > [ rosmake ] Checking rosdeps compliance for packages
>> >>>> > orocos_toolchain_ros.
>> >>>> > This may take a few
>> >>>> > seconds.
>> >>>> > Invalid manifest
>> >>>> >
>> >>>> >
>> file[/home/ard/ros/orocos_toolchain_ros/rtt_exercises/rtt-exercises/hello-7-deployment/manifest.xml]:
>> >>>> > missing required 'license' element
>> >>>> > ..................... and so many other
>> >>>> > QUITTING: due to conflicting rosdep definitions, please resolve
>> this
>> >>>> > conflict.
>> >>>> > Rules for ruby do not match:
>> >>>> > ruby [/home/ard/ros/ros/rosdep.yaml]
>> >>>> > ruby1.8-dev libruby1.8
>> >>>> > [/home/ard/ros/orocos_toolchain_ros/rosdep.yaml]
>> >>>> > [ rosmake ] rosdep check passed all system dependencies in
>> >>>> > packages
>> >>>> > [ rosmake ] Starting >>>
>> >>>> > tools/rospack
>> >>>> > [ rosmake ] Finished <<<
>> >>>> > tools/rospack
>> >>>> > [ rosmake ] Starting >>>
>> >>>> > 3rdparty/gtest
>> >>>> > [ rosmake ] Finished <<<
>> >>>> > 3rdparty/gtest
>> >>>> > [ rosmake ] Starting >>>
>> >>>> > core/genmsg_cpp
>> >>>> > [ rosmake ] Finished <<<
>> >>>> > core/genmsg_cpp
>> >>>> > [rosmake-0] Starting >>> log4cpp [ make
>> >>>> > ]
>> >>>> > [rosmake-1] Starting >>> roslang [ make
>> >>>> > ]
>> >>>> > [rosmake-1] Finished <<< roslang No Makefile in package
>> >>>> > roslang
>> >>>> > [rosmake-1] Starting >>> roslib [ make
>> >>>> > ]
>> >>>> > [rosmake-1] Finished <<< roslib [PASS] [ 0.91 seconds
>> >>>> > ]
>> >>>> > [rosmake-1] Starting >>> xmlrpcpp [ make
>> >>>> > ]
>> >>>> > [rosmake-1] Finished <<< xmlrpcpp [PASS] [ 0.37 seconds
>> >>>> > ]
>> >>>> > [rosmake-1] Starting >>> rosconsole [ make
>> >>>> > ]
>> >>>> > [rosmake-1] Finished <<< rosconsole [PASS] [ 0.69 seconds
>> >>>> > ]
>> >>>> > [rosmake-1] Starting >>> roscpp [ make
>> >>>> > ]
>> >>>> > [rosmake-1] Finished <<< roscpp [PASS] [ 1.30 seconds
>> >>>> > ]
>> >>>> > [rosmake-1] Starting >>> rtt [ make
>> >>>> > ]
>> >>>> > [ rosmake ] Output from build of package log4cpp written
>> >>>> > to:
>> >>>> > [ 2 Active 7/45 Complete ]
>> >>>> > [ rosmake ]
>> >>>> >
>> >>>> >
>> /home/ard/.ros/rosmake/rosmake_output-20110207-210422/log4cpp/build_output.log
>> >>>> > [rosmake-0] Finished <<< log4cpp [PASS] [ 56.40 seconds ] --
>> WARNING:
>> >>>> > 1
>> >>>> > compiler
>> >>>> > warnings
>> >>>> > [rosmake-0] Starting >>> rosbuild [ make
>> >>>> > ]
>> >>>> > [rosmake-0] Finished <<< rosbuild No Makefile in package
>> >>>> > rosbuild
>> >>>> > [rosmake-0] Starting >>> std_msgs [ make
>> >>>> > ]
>> >>>> > [rosmake-0] Finished <<< std_msgs [PASS] [ 5.61 seconds
>> >>>> > ]
>> >>>> > [rosmake-0] Starting >>> utilrb [ make
>> >>>> > ]
>> >>>> > [ rosmake ] Output from build of package utilrb written
>> >>>> > to:]
>> >>>> > [ 2 Active 10/45 Complete ]
>> >>>> > [ rosmake ]
>> >>>> >
>> >>>> >
>> /home/ard/.ros/rosmake/rosmake_output-20110207-210422/utilrb/build_output.log
>> >>>> > [rosmake-0] Finished <<< utilrb [PASS] [ 49.13 seconds ] --
>> WARNING: 1
>> >>>> > compiler
>> >>>> > warnings
>> >>>> > [rosmake-0] Starting >>> utilmm [ make
>> >>>> > ]
>> >>>> > [ rosmake ] Last 40 linest: 110.4 sec ] [ utilmm: 2.5 sec
>> >>>> > ]
>> >>>> > [ 2 Active 11/45 Complete ]
>> >>>> >
>> >>>> >
>> {-------------------------------------------------------------------------------
>> >>>> > if [ ! -f utilmm.md5sum ]; then echo "Error: Couldn't find md5sum
>> >>>> > file
>> >>>> > utilmm.md5sum" && false; fi
>> >>>> > `rospack find rosbuild`/bin/download_checkmd5.py
>> >>>> >
>> >>>> >
>> http://people.mech.kuleuven.be/~sbellens/orocos-toolchain/orocos-toolcha...
>> >>>> > build/v2.1.0 `awk {'print $1'} utilmm.md5sum`
>> >>>> > [rosbuild] Downloading
>> >>>> >
>> >>>> >
>> http://people.mech.kuleuven.be/~sbellens/orocos-toolchain/orocos-toolcha...
>> >>>> > to build/v2.1.0...Done
>> >>>> > [rosbuild] Checking md5sum on build/v2.1.0
>> >>>> > touch -c build/v2.1.0
>> >>>> > rm -rf build/orocos-toolchain-utilmm
>> >>>> > cd build; tar xzf ../build/v2.1.0
>> >>>> > cd build/orocos-toolchain-utilmm && patch -p0 <
>> ../../utilmm.patch;
>> >>>> > patching file CMakeLists.txt
>> >>>> > touch build/orocos-toolchain-utilmm/unpacked
>> >>>> > mkdir -p bin
>> >>>> > cd build && cmake -Wdev -DCMAKE_TOOLCHAIN_FILE=`rospack find
>> >>>> > rosbuild`/rostoolchain.cmake -DCMAKE_INSTALL_PREFIX=`rospack find
>> >>>> > utilmm`/install ..
>> >>>> > -- The C compiler identification is GNU
>> >>>> > -- The CXX compiler identification is GNU
>> >>>> > -- Check for working C compiler: /usr/bin/gcc
>> >>>> > -- Check for working C compiler: /usr/bin/gcc -- works
>> >>>> > -- Detecting C compiler ABI info
>> >>>> > -- Detecting C compiler ABI info - done
>> >>>> > -- Check for working CXX compiler: /usr/bin/c++
>> >>>> > -- Check for working CXX compiler: /usr/bin/c++ -- works
>> >>>> > -- Detecting CXX compiler ABI info
>> >>>> > -- Detecting CXX compiler ABI info - done
>> >>>> > [rosbuild] Building package utilmm
>> >>>> > [rosbuild] Cached build flags older than manifests; calling
>> rospack
>> >>>> > to get
>> >>>> > flags
>> >>>> > [rosbuild] Including
>> >>>> > /home/ard/ros/ros/core/roscpp/cmake/roscpp.cmake
>> >>>> > [rosbuild] Including
>> /home/ard/ros/ros/core/rospy/cmake/rospy.cmake
>> >>>> > [rosbuild] Including
>> >>>> > /home/ard/ros/ros/core/roslisp/cmake/roslisp.cmake
>> >>>> > -- Found The Following Boost Libraries:
>> >>>> > -- unit_test_framework
>> >>>> > -- Boost Version: 1.42.0
>> >>>> > -- cannot find boost/graph
>> >>>> > CMake Error at
>> >>>> > build/orocos-toolchain-utilmm/cmake/FindBoost.cmake:367
>> >>>> > (MESSAGE):
>> >>>> > Boost and/or some required components not found. Please
>> install
>> >>>> > the
>> >>>> > Boost
>> >>>> > libraries AND development packages
>> >>>> > Call Stack (most recent call first):
>> >>>> > build/orocos-toolchain-utilmm/CMakeLists.txt:9 (FIND_PACKAGE)
>> >>>>
>> >>>> And do you actually have these installed? The boost dependency
>> >>>> packages are defined in $(find ros)/rosdep.yaml (you can find out
>> with
>> >>>> 'rosdep where_defined boost'). I see there is no boost-graph entry
>> for
>> >>>> the debian platform. You'll have to add something like
>> >>>> 'libboost-dev-graph' for your platform most probably. I'll switch to
>> >>>> CTurtle and see if I can get the ruby conflict sorted out.
>> >>>
>> >>> You are rigth, the OS dependencies are different from ubuntu to
>> debian.
>> >>> For debian it's a list of packages since in debian it's "all" package.
>> So I
>> >>> had to queue libboost-graph-dev in my ros/rosdep.yaml.
>> >>>
>> >>
>> >> It works ! Thanks a lot
>> >>
>> >
>> > Is it done on purpose that env.sh doesn't contain ocl binary paths (for
>> > accessing deployer for example) ? It is the behavior of the standard
>> Orocos
>> > toolchain
>>
>> The standard way to run executables in ROS packages is with rosrun, e.g;
>>
>> rosrun ocl deployer-gnulinux
>>
>
> Oh yes ! I still don't have the ROS reflexes :)
>
>
it answers :
ard@ard-host-v5:/media/DD_data/home/ard$ rosrun ocl deployer-gnulinux
[rosrun] You have chosen a non-unique executable, please pick one of the
following:
1) /home/ard/ros/orocos_toolchain_ros/ocl/bin/deployer-gnulinux
2) /home/ard/ros/orocos_toolchain_ros/ocl/install/bin/deployer-gnulinux
#?

I know there are egal because one is the "make installed" version of the
other, by I find it is strange and prevent from starting it automatically
after boot (of course I have solutions to avoid this, but the rosway should
work no ?)

I makes me thinking about folder size and orocos_toolchain_ros is 1,7Gb on
my computer x-( I know there is some hard work on code size reduction on
the Orocos side but nearly 2gb is quite huge.

Does it exist a "rosmake clean" instruction ?

>
>
>>
>> Steven
>>
>> >
>> >
>> >
>> >>
>> >> Here are some compiler warning, mainly from Orocos side I think (maybe
>> you
>> >> already know them but anyway) :
>> >>
>> >> utilrb :
>> >> /usr/bin/ld: warning: cannot find entry symbol xport-dynamic-module;
>> >> defaulting to 0000000000001990
>> >> make[1]: quittant le répertoire «
>> >>
>> /media/DD_data/home/ard/ros/orocos_toolchain_ros/utilrb/build/orocos-toolchain-utilrb/ext
>> >> »
>> >> touch installed
>> >>
>> >>
>> >> typelib
>> >> [ 36%] Building CXX object
>> >>
>> build/orocos-toolchain-typelib/bindings/ruby/CMakeFiles/typelib_ruby.dir/ext/value.o
>> >>
>> >>
>> /home/ard/ros/orocos_toolchain_ros/typelib/build/orocos-toolchain-typelib/bindings/ruby/ext/value.cc:495:
>> >> warning: ‘void type$
>> >> ...
>> >> [ 56%] Building CXX object
>> >>
>> build/orocos-toolchain-typelib/lang/cimport/CMakeFiles/typeLang_c.dir/Dictionary.o
>> >>
>> >>
>> /home/ard/ros/orocos_toolchain_ros/typelib/build/orocos-toolchain-typelib/lang/cimport/Dictionary.cc:
>> >> In member function ‘virtual int Dictionary::hash(const std::string&)’:
>> >>
>> >>
>> /home/ard/ros/orocos_toolchain_ros/typelib/build/orocos-toolchain-typelib/lang/cimport/Dictionary.cc:161:
>> >> warning: array subscript has type ‘char’
>> >>
>> >>
>> /home/ard/ros/orocos_toolchain_ros/typelib/build/orocos-toolchain-typelib/lang/cimport/Dictionary.cc:163:
>> >> warning: array subscript has type ‘char’
>> >> ...
>> >> [ 68%] Building CXX object
>> >>
>> build/orocos-toolchain-typelib/lang/cimport/CMakeFiles/typeLang_c.dir/CPPParser.o
>> >> cparser.g: In member function ‘CPPParser::TypeQualifier
>> >> CPPParser::type_qualifier()’:
>> >> cparser.g:366: warning: ‘tq’ may be used uninitialized in this function
>> >> cparser.g:366: note: ‘tq’ was declared here
>> >> cparser.g: In member function ‘CPPParser::StorageClass
>> >> CPPParser::storage_class_specifier()’:
>> >> cparser.g:359: warning: ‘sc’ may be used uninitialized in this function
>> >> cparser.g:359: note: ‘sc’ was declared here
>> >> cparser.g: In member function ‘int CPPParser::int_constant()’:
>> >> cparser.g:1212: warning: ‘value’ may be used uninitialized in this
>> >> function
>> >> cparser.g:1212: note: ‘value’ was declared here
>> >> cparser.g: In member function ‘int
>> >> CPPParser::int_constant_unary_expression()’:
>> >> cparser.g:1205: warning: ‘sign’ may be used uninitialized in this
>> function
>> >> cparser.g:1205: note: ‘sign’ was declared here
>> >> cparser.g: In member function ‘int
>> >> CPPParser::int_constant_add_expression()’:
>> >> cparser.g:1176: warning: ‘sign’ may be used uninitialized in this
>> function
>> >> cparser.g:1176: note: ‘sign’ was declared here
>> >> cparser.g: In member function ‘void CPPParser::enumerator()’:
>> >> cparser.g:512: warning: ‘value’ may be used uninitialized in this
>> function
>> >> cparser.g:512: note: ‘value’ was declared here
>> >> cparser.g: In member function ‘long int
>> >> CPPParser::class_specifier(CPPParser::DeclSpecifier)’:
>> >> cparser.g:462: warning: ‘ts’ may be used uninitialized in this function
>> >> cparser.g:462: note: ‘ts’ was declared here
>> >> cparser.g: In member function ‘long int
>> >> CPPParser::type_specifier(CPPParser::DeclSpecifier)’:
>> >> cparser.g:371: warning: ‘ts’ may be used uninitialized in this function
>> >> cparser.g:371: note: ‘ts’ was declared here
>> >>
>> >>
>> >>
>> >>
>> >>
>> >>
>> >>
>> >>>
>> >>>
>> >>>>
>> >>>> Steven
>> >>>>
>> >>>> >
>> >>>> >
>> >>>> > -- Configuring incomplete, errors occurred!
>> >>>> >
>> >>>> >
>> -------------------------------------------------------------------------------}
>> >>>> > [ rosmake ] Output from build of package utilmm written to:
>> >>>> > [ rosmake ]
>> >>>> >
>> >>>> >
>> /home/ard/.ros/rosmake/rosmake_output-20110207-210422/utilmm/build_output.log
>> >>>> > [rosmake-0] Finished <<< utilmm [FAIL] [ 2.55 seconds
>> >>>> > ]
>> >>>> > [ rosmake ] Halting due to failure in package utilmm.
>> >>>> > [ rosmake ] Waiting for other threads to
>> >>>> > complete.
>> >>>> > [rosmake-1] Finished <<< rtt [PASS] [ 262.82 seconds
>> >>>> > ]
>> >>>> > [ rosmake ]
>> >>>> > Results:
>> >>>> > [ rosmake ] Built 13 packages with 1
>> >>>> > failures.
>> >>>> > [ rosmake ] Summary output to
>> >>>> > directory
>> >>>> > [ rosmake ]
>> >>>> > /home/ard/.ros/rosmake/rosmake_output-20110207-210422
>> >>>> > ard@ard-host-v5:~/ros/orocos_toolchain_ros$
>> >>>> >
>> >>>> >
>> >>>> >
>> >>>> >
>> >>>> >>
>> >>>> >> regards,
>> >>>> >>
>> >>>> >> Steven
>> >>>> >>
>> >>>> >> >
>> >>>> >> >
>> >>>> >> >>
>> >>>> >> >> Steven
>> >>>> >> >>
>> >>>> >> >> >
>> >>>> >> >> >
>> >>>> >> >> >
>> >>>> >> >> >>
>> >>>> >> >> >>
>> >>>> >> >> >>>
>> >>>> >> >> >>>
>> >>>> >> >> >>>>>
>> >>>> >> >> >>>>> regards,
>> >>>> >> >> >>>>>
>> >>>> >> >> >>>>> Steven
>> >>>> >> >> >>>>>
>> >>>> >> >> >>>>>
>> >>>> >> >> >>>>> >
>> >>>> >> >> >>>>> >
>> >>>> >> >> >>>>> >
>> >>>> >> >> >>>>> >
>> >>>> >> >> >>>>> >>
>> >>>> >> >> >>>>> >> > At the end it seems to have work properly as I have
>> >>>> >> >> >>>>> >> > this in
>> >>>> >> >> >>>>> >> > the
>> >>>> >> >> >>>>> >> > folder
>> >>>> >> >> >>>>> >> > (and
>> >>>> >> >> >>>>> >> > succeed a build yesterday) :
>> >>>> >> >> >>>>> >> >
>> >>>> >> >> >>>>> >> >
>> >>>> >> >> >>>>> >> >
>> >>>> >> >> >>>>> >> >
>> >>>> >> >> >>>>> >> > ard@ard-host-v5
>> :/media/DD_data/home/ard/ros/orocos_toolchain_ros$
>> >>>> >> >> >>>>> >> > ls
>> >>>> >> >> >>>>> >> > CMakeLists.txt env.sh ocl rosdep.yaml
>> >>>> >> >> >>>>> >> > rtt_exercises
>> >>>> >> >> >>>>> >> > rtt_ros_integration_example stack.xml utilmm
>> >>>> >> >> >>>>> >> > env.mk Makefile orogen rtt
>> >>>> >> >> >>>>> >> > rtt_ros_integration
>> >>>> >> >> >>>>> >> > rtt_ros_integration_std_msgs typelib utilrb
>> >>>> >> >> >>>>> >> >
>> >>>> >> >> >>>>> >> >
>> >>>> >> >> >>>>> >> >
>> >>>> >> >> >>>>> >> > ard@ard-host-v5
>> :/media/DD_data/home/ard/ros/orocos_toolchain_ros$
>> >>>> >> >> >>>>> >> >
>> >>>> >> >> >>>>> >> >
>> >>>> >> >> >>>>> >> >
>> >>>> >> >> >>>>> >> > _______________________________________________
>> >>>> >> >> >>>>> >> > ros-users mailing list
>> >>>> >> >> >>>>> >> > ros-users [..] ...
>> >>>> >> >> >>>>> >> > https://code.ros.org/mailman/listinfo/ros-users
>> >>>> >> >> >>>>> >> >
>> >>>> >> >> >>>>> >> >
>> >>>> >> >> >>>>> >> --
>> >>>> >> >> >>>>> >> Orocos-Users mailing list
>> >>>> >> >> >>>>> >> Orocos-Users [..] ...
>> >>>> >> >> >>>>> >>
>> >>>> >> >> >>>>> >>
>> http://lists.mech.kuleuven.be/mailman/listinfo/orocos-users
>> >>>> >> >> >>>>> >
>> >>>> >> >> >>>>> >
>> >>>> >> >> >>>>> > _______________________________________________
>> >>>> >> >> >>>>> > ros-users mailing list
>> >>>> >> >> >>>>> > ros-users [..] ...
>> >>>> >> >> >>>>> > https://code.ros.org/mailman/listinfo/ros-users
>> >>>> >> >> >>>>> >
>> >>>> >> >> >>>>> >
>> >>>> >> >> >>>>> _______________________________________________
>> >>>> >> >> >>>>> ros-users mailing list
>> >>>> >> >> >>>>> ros-users [..] ...
>> >>>> >> >> >>>>> https://code.ros.org/mailman/listinfo/ros-users
>> >>>> >> >> >>>>
>> >>>> >> >> >>>
>> >>>> >> >> >>
>> >>>> >> >> >
>> >>>> >> >> >
>> >>>> >> >> > _______________________________________________
>> >>>> >> >> > ros-users mailing list
>> >>>> >> >> > ros-users [..] ...
>> >>>> >> >> > https://code.ros.org/mailman/listinfo/ros-users
>> >>>> >> >> >
>> >>>> >> >> >
>> >>>> >> >> --
>> >>>> >> >> Orocos-Users mailing list
>> >>>> >> >> Orocos-Users [..] ...
>> >>>> >> >> http://lists.mech.kuleuven.be/mailman/listinfo/orocos-users
>> >>>> >> >
>> >>>> >> >
>> >>>> >> > _______________________________________________
>> >>>> >> > ros-users mailing list
>> >>>> >> > ros-users [..] ...
>> >>>> >> > https://code.ros.org/mailman/listinfo/ros-users
>> >>>> >> >
>> >>>> >> >
>> >>>> >> --
>> >>>> >> Orocos-Users mailing list
>> >>>> >> Orocos-Users [..] ...
>> >>>> >> http://lists.mech.kuleuven.be/mailman/listinfo/orocos-users
>> >>>> >
>> >>>> >
>> >>>> > _______________________________________________
>> >>>> > ros-users mailing list
>> >>>> > ros-users [..] ...
>> >>>> > https://code.ros.org/mailman/listinfo/ros-users
>> >>>> >
>> >>>> >
>> >>>> _______________________________________________
>> >>>> ros-users mailing list
>> >>>> ros-users [..] ...
>> >>>> https://code.ros.org/mailman/listinfo/ros-users
>> >>>
>> >>
>> >
>> >
>> > _______________________________________________
>> > ros-users mailing list
>> > ros-users [..] ...
>> > https://code.ros.org/mailman/listinfo/ros-users
>> >
>> >
>> _______________________________________________
>> ros-users mailing list
>> ros-users [..] ...
>> https://code.ros.org/mailman/listinfo/ros-users
>>
>
>

[ros-users] orocos_toolchain_ros for debian

2011/2/8 Willy Lambert <lambert [dot] willy [..] ...>

>
>
>>> The standard way to run executables in ROS packages is with rosrun, e.g;
>>>
>>> rosrun ocl deployer-gnulinux
>>>
>>
>> Oh yes ! I still don't have the ROS reflexes :)
>>
>>
> it answers :
> ard@ard-host-v5:/media/DD_data/home/ard$ rosrun ocl deployer-gnulinux
> [rosrun] You have chosen a non-unique executable, please pick one of the
> following:
> 1) /home/ard/ros/orocos_toolchain_ros/ocl/bin/deployer-gnulinux
> 2) /home/ard/ros/orocos_toolchain_ros/ocl/install/bin/deployer-gnulinux
> #?
>
> I know there are egal because one is the "make installed" version of the
> other, by I find it is strange and prevent from starting it automatically
> after boot (of course I have solutions to avoid this, but the rosway should
> work no ?)
>
> I makes me thinking about folder size and orocos_toolchain_ros is 1,7Gb on
> my computer x-( I know there is some hard work on code size reduction on
> the Orocos side but nearly 2gb is quite huge.
>
> Does it exist a "rosmake clean" instruction ?
>

Let me up this subject,
after having built the orocos_toolchain_ros it seems it's a bit messy with
build and installed files. Firstly, rosrun find 2 executables for
deployer-gnulinux and can't choose. Secondly after having used "make clean"
in all the packages of orocos_toolchain_ros stack, it reduced from nearly
2gb to 350Mb with is by far more acceptable. Is it any "ros" tool to do this
? Would it be possible to add a global "make clean" at the root of
orocos_toolchain_ros ?

[ros-users] orocos_toolchain_ros for debian

On Monday 21 February 2011 00:32:05 Willy Lambert wrote:
> 2011/2/8 Willy Lambert <lambert [dot] willy [..] ...>
>
> >>> The standard way to run executables in ROS packages is with rosrun,
> >>> e.g;
> >>>
> >>> rosrun ocl deployer-gnulinux
> >>
> >> Oh yes ! I still don't have the ROS reflexes :)
> >
> > it answers :
> > ard@ard-host-v5:/media/DD_data/home/ard$ rosrun ocl deployer-gnulinux
> > [rosrun] You have chosen a non-unique executable, please pick one of the
> > following:
> > 1) /home/ard/ros/orocos_toolchain_ros/ocl/bin/deployer-gnulinux
> > 2) /home/ard/ros/orocos_toolchain_ros/ocl/install/bin/deployer-gnulinux
> > #?
> >
> > I know there are egal because one is the "make installed" version of the
> >
> > other, by I find it is strange and prevent from starting it automatically
> > after boot (of course I have solutions to avoid this, but the rosway
> > should work no ?)
> >
> > I makes me thinking about folder size and orocos_toolchain_ros is 1,7Gb
> > on my computer x-( I know there is some hard work on code size
> > reduction on the Orocos side but nearly 2gb is quite huge.
> >
> > Does it exist a "rosmake clean" instruction ?
>
> Let me up this subject,
> after having built the orocos_toolchain_ros it seems it's a bit messy with
> build and installed files. Firstly, rosrun find 2 executables for
> deployer-gnulinux and can't choose.

We're still looking on how to solve this. The problem is that we require a
'make install' in ocl because the headers are included using 'ocl/Header.hpp'
by user code, while they are in the sources in 'subproject/Header.hpp'. We
discussed moving all headers to the ocl/ directory, but this somewhat beats
the purpose of the modularisation we did. An alternative would be to create
symlinks from ocl/Header.hpp to subproject/Header.hpp in ROS_ROOT
environments. This might be the least intrusive step for now.

> Secondly after having used "make clean"
> in all the packages of orocos_toolchain_ros stack, it reduced from nearly
> 2gb to 350Mb with is by far more acceptable. Is it any "ros" tool to do
> this ? Would it be possible to add a global "make clean" at the root of
> orocos_toolchain_ros ?

Did you compile with MinSizeRel ? The make clean is not what you want, since
it will also remove the libraries of the normal 'ros' packages, which don't
have an install step (so it only makes sense for RTT and OCL right now).

People are looking at how to reduce code size, but for a development system,
it's always handy to have the .o files still there....

Peter

[ros-users] orocos_toolchain_ros for debian

2011/2/22 Peter Soetens <peter [..] ...>

> On Monday 21 February 2011 00:32:05 Willy Lambert wrote:
> > 2011/2/8 Willy Lambert <lambert [dot] willy [..] ...>
> >
> > >>> The standard way to run executables in ROS packages is with rosrun,
> > >>> e.g;
> > >>>
> > >>> rosrun ocl deployer-gnulinux
> > >>
> > >> Oh yes ! I still don't have the ROS reflexes :)
> > >
> > > it answers :
> > > ard@ard-host-v5:/media/DD_data/home/ard$ rosrun ocl deployer-gnulinux
> > > [rosrun] You have chosen a non-unique executable, please pick one of
> the
> > > following:
> > > 1) /home/ard/ros/orocos_toolchain_ros/ocl/bin/deployer-gnulinux
> > > 2) /home/ard/ros/orocos_toolchain_ros/ocl/install/bin/deployer-gnulinux
> > > #?
> > >
> > > I know there are egal because one is the "make installed" version of
> the
> > >
> > > other, by I find it is strange and prevent from starting it
> automatically
> > > after boot (of course I have solutions to avoid this, but the rosway
> > > should work no ?)
> > >
> > > I makes me thinking about folder size and orocos_toolchain_ros is 1,7Gb
> > > on my computer x-( I know there is some hard work on code size
> > > reduction on the Orocos side but nearly 2gb is quite huge.
> > >
> > > Does it exist a "rosmake clean" instruction ?
> >
> > Let me up this subject,
> > after having built the orocos_toolchain_ros it seems it's a bit messy
> with
> > build and installed files. Firstly, rosrun find 2 executables for
> > deployer-gnulinux and can't choose.
>
> We're still looking on how to solve this. The problem is that we require a
> 'make install' in ocl because the headers are included using
> 'ocl/Header.hpp'
> by user code, while they are in the sources in 'subproject/Header.hpp'. We
> discussed moving all headers to the ocl/ directory, but this somewhat beats
> the purpose of the modularisation we did. An alternative would be to create
> symlinks from ocl/Header.hpp to subproject/Header.hpp in ROS_ROOT
> environments. This might be the least intrusive step for now.
>

Ok, but here it's about a binary

>
>
> > Secondly after having used "make clean"
> > in all the packages of orocos_toolchain_ros stack, it reduced from nearly
> > 2gb to 350Mb with is by far more acceptable. Is it any "ros" tool to do
> > this ? Would it be possible to add a global "make clean" at the root of
> > orocos_toolchain_ros ?
>
> Did you compile with MinSizeRel ?

I used the default configuration and didn't thougth about this.
How may I change this with rosmake ?

> The make clean is not what you want, since
> it will also remove the libraries of the normal 'ros' packages, which don't
> have an install step (so it only makes sense for RTT and OCL right now).
>
> People are looking at how to reduce code size, but for a development
> system,
> it's always handy to have the .o files still there....
>

of course it is. But it is also handy to have a clean function before
copying on the robot (and not to embed the sources).

In the "classic" orocos toolchain installation I used to copy the install
folder onto my target with the same path as on the building machine. If I
could create my_orocos_toolchain.deb easily I would install then on my robot
instead of copying.

As there is no "install" step yet in ROS, I just copy the complete ros_root
folder containing all the stacks (including orocos_toolchain_ros) onto the
target. So the .o goes with it. Maybe I could do better, but I don't know
how to do it

>
> Peter
>
>
>

Ruben Smits's picture

[ros-users] orocos_toolchain_ros for debian

On Tuesday 22 February 2011 23:55:26 Willy Lambert wrote:
> 2011/2/22 Peter Soetens
> <peter [..] ...<mailto:peter [..] ...>>
>
> On Monday 21 February 2011 00:32:05 Willy Lambert wrote:
> > 2011/2/8 Willy Lambert
> > <lambert [dot] willy [..] ...<mailto:lambert [dot] willy [..] ...>>
> >
> > >>> The standard way to run executables in ROS packages is with
> > >>> rosrun,
> > >>> e.g;
> > >>>
> > >>> rosrun ocl deployer-gnulinux
> > >>
> > >> Oh yes ! I still don't have the ROS reflexes :)
> > >
> > > it answers :
> > > ard@ard-host-v5:/media/DD_data/home/ard$ rosrun ocl
> > > deployer-gnulinux
> > > [rosrun] You have chosen a non-unique executable, please pick one of
> > > the following:
> > > 1) /home/ard/ros/orocos_toolchain_ros/ocl/bin/deployer-gnulinux
> > > 2)
> > > /home/ard/ros/orocos_toolchain_ros/ocl/install/bin/deployer-gnulinu
> > > x
> > > #?
> > >
> > > I know there are egal because one is the "make installed" version
> > > of the
> > >
> > > other, by I find it is strange and prevent from starting it
> > > automatically after boot (of course I have solutions to avoid this,
> > > but the rosway should work no ?)
> > >
> > > I makes me thinking about folder size and orocos_toolchain_ros is
> > > 1,7Gb
> > > on my computer x-( I know there is some hard work on code size
> > > reduction on the Orocos side but nearly 2gb is quite huge.
> > >
> > > Does it exist a "rosmake clean" instruction ?
> >
> > Let me up this subject,
> > after having built the orocos_toolchain_ros it seems it's a bit messy
> > with build and installed files. Firstly, rosrun find 2 executables for
> > deployer-gnulinux and can't choose.
>
> We're still looking on how to solve this. The problem is that we require a
> 'make install' in ocl because the headers are included using
> 'ocl/Header.hpp' by user code, while they are in the sources in
> 'subproject/Header.hpp'. We discussed moving all headers to the ocl/
> directory, but this somewhat beats the purpose of the modularisation we
> did. An alternative would be to create symlinks from ocl/Header.hpp to
> subproject/Header.hpp in ROS_ROOT
> environments. This might be the least intrusive step for now.
>
> Ok, but here it's about a binary
>
> > Secondly after having used "make clean"
> > in all the packages of orocos_toolchain_ros stack, it reduced from
> > nearly
> > 2gb to 350Mb with is by far more acceptable. Is it any "ros" tool to do
> > this ? Would it be possible to add a global "make clean" at the root of
> > orocos_toolchain_ros ?
>
> Did you compile with MinSizeRel ?
>
> I used the default configuration and didn't thougth about this.
> How may I change this with rosmake ?
>

There are different things you can use: I suggest you just edit the orocos-
rtt.default.cmake file.

>
> The make clean is not what you want, since
> it will also remove the libraries of the normal 'ros' packages, which don't
> have an install step (so it only makes sense for RTT and OCL right now).
>
> People are looking at how to reduce code size, but for a development system,
> it's always handy to have the .o files still there....
>
> of course it is. But it is also handy to have a clean function before
> copying on the robot (and not to embed the sources).
>
> In the "classic" orocos toolchain installation I used to copy the install
> folder onto my target with the same path as on the building machine. If I
> could create my_orocos_toolchain.deb easily I would install then on my
> robot instead of copying.

You could strip the orocos_toolchain_ros rtt and ocl packages after building
and before copying it. AFAIK you can entirely remove the build directory.

> As there is no "install" step yet in ROS, I just copy the complete ros_root
> folder containing all the stacks (including orocos_toolchain_ros) onto the
> target. So the .o goes with it. Maybe I could do better, but I don't know
> how to do it
>
>
>
>
> Peter

-- Ruben

[ros-users] orocos_toolchain_ros for debian

2011/2/23 Ruben Smits <ruben [dot] smits [..] ...>

> On Tuesday 22 February 2011 23:55:26 Willy Lambert wrote:
> > 2011/2/22 Peter Soetens
> > <peter [..] ...<mailto:peter [..] ...>>
> >
> > On Monday 21 February 2011 00:32:05 Willy Lambert wrote:
> > > 2011/2/8 Willy Lambert
> > > <lambert [dot] willy [..] ...<mailto:lambert [dot] willy [..] ...>>
> > >
> > > >>> The standard way to run executables in ROS packages is with
> > > >>> rosrun,
> > > >>> e.g;
> > > >>>
> > > >>> rosrun ocl deployer-gnulinux
> > > >>
> > > >> Oh yes ! I still don't have the ROS reflexes :)
> > > >
> > > > it answers :
> > > > ard@ard-host-v5:/media/DD_data/home/ard$ rosrun ocl
> > > > deployer-gnulinux
> > > > [rosrun] You have chosen a non-unique executable, please pick one of
> > > > the following:
> > > > 1) /home/ard/ros/orocos_toolchain_ros/ocl/bin/deployer-gnulinux
> > > > 2)
> > > > /home/ard/ros/orocos_toolchain_ros/ocl/install/bin/deployer-gnulinu
> > > > x
> > > > #?
> > > >
> > > > I know there are egal because one is the "make installed" version
> > > > of the
> > > >
> > > > other, by I find it is strange and prevent from starting it
> > > > automatically after boot (of course I have solutions to avoid this,
> > > > but the rosway should work no ?)
> > > >
> > > > I makes me thinking about folder size and orocos_toolchain_ros is
> > > > 1,7Gb
> > > > on my computer x-( I know there is some hard work on code size
> > > > reduction on the Orocos side but nearly 2gb is quite huge.
> > > >
> > > > Does it exist a "rosmake clean" instruction ?
> > >
> > > Let me up this subject,
> > > after having built the orocos_toolchain_ros it seems it's a bit messy
> > > with build and installed files. Firstly, rosrun find 2 executables for
> > > deployer-gnulinux and can't choose.
> >
> > We're still looking on how to solve this. The problem is that we require
> a
> > 'make install' in ocl because the headers are included using
> > 'ocl/Header.hpp' by user code, while they are in the sources in
> > 'subproject/Header.hpp'. We discussed moving all headers to the ocl/
> > directory, but this somewhat beats the purpose of the modularisation we
> > did. An alternative would be to create symlinks from ocl/Header.hpp to
> > subproject/Header.hpp in ROS_ROOT
> > environments. This might be the least intrusive step for now.
> >
> > Ok, but here it's about a binary
> >
> > > Secondly after having used "make clean"
> > > in all the packages of orocos_toolchain_ros stack, it reduced from
> > > nearly
> > > 2gb to 350Mb with is by far more acceptable. Is it any "ros" tool to do
> > > this ? Would it be possible to add a global "make clean" at the root of
> > > orocos_toolchain_ros ?
> >
> > Did you compile with MinSizeRel ?
> >
> > I used the default configuration and didn't thougth about this.
> > How may I change this with rosmake ?
> >
>
> There are different things you can use: I suggest you just edit the orocos-
> rtt.default.cmake file.
>
>
Does I only have to change the rtt config ? What about ocl ?
rtt_ros_integration ?

> >
> > The make clean is not what you want, since
> > it will also remove the libraries of the normal 'ros' packages, which
> don't
> > have an install step (so it only makes sense for RTT and OCL right now).
> >
> > People are looking at how to reduce code size, but for a development
> system,
> > it's always handy to have the .o files still there....
> >
> > of course it is. But it is also handy to have a clean function before
> > copying on the robot (and not to embed the sources).
> >
> > In the "classic" orocos toolchain installation I used to copy the install
> > folder onto my target with the same path as on the building machine. If I
> > could create my_orocos_toolchain.deb easily I would install then on my
> > robot instead of copying.
>
> You could strip the orocos_toolchain_ros rtt and ocl packages after
> building
> and before copying it. AFAIK you can entirely remove the build directory.
>

I'll try stripping and let you know about resulting size
"remove the build directory" : This is what "make clean" does no ?

>
> > As there is no "install" step yet in ROS, I just copy the complete
> ros_root
> > folder containing all the stacks (including orocos_toolchain_ros) onto
> the
> > target. So the .o goes with it. Maybe I could do better, but I don't know
> > how to do it
> >
> >
> >
> >
> > Peter
>
> -- Ruben
>

[ros-users] orocos_toolchain_ros for debian

On Wednesday 23 February 2011 14:18:34 Willy Lambert wrote:
> 2011/2/23 Ruben Smits <ruben [dot] smits [..] ...>
>
> > On Tuesday 22 February 2011 23:55:26 Willy Lambert wrote:
> > > 2011/2/22 Peter Soetens
> > > <peter [..] ...<mailto:peter [..] ...>>
> > >
> > > On Monday 21 February 2011 00:32:05 Willy Lambert wrote:
> > > > 2011/2/8 Willy Lambert
> > > > <lambert [dot] willy [..] ...<mailto:lambert [dot] willy [..] ...>>
> > > >
> > > > >>> The standard way to run executables in ROS packages is with
> > > > >>> rosrun,
> > > > >>> e.g;
> > > > >>>
> > > > >>> rosrun ocl deployer-gnulinux
> > > > >>
> > > > >> Oh yes ! I still don't have the ROS reflexes :)
> > > > >
> > > > > it answers :
> > > > > ard@ard-host-v5:/media/DD_data/home/ard$ rosrun ocl
> > > > > deployer-gnulinux
> > > > > [rosrun] You have chosen a non-unique executable, please pick one
> > > > > of the following:
> > > > > 1) /home/ard/ros/orocos_toolchain_ros/ocl/bin/deployer-gnulinux
> > > > > 2)
> > > > > /home/ard/ros/orocos_toolchain_ros/ocl/install/bin/deployer-gnulinu
> > > > > x
> > > > > #?
> > > > >
> > > > > I know there are egal because one is the "make installed" version
> > > > > of the
> > > > >
> > > > > other, by I find it is strange and prevent from starting it
> > > > > automatically after boot (of course I have solutions to avoid this,
> > > > > but the rosway should work no ?)
> > > > >
> > > > > I makes me thinking about folder size and orocos_toolchain_ros is
> > > > > 1,7Gb
> > > > > on my computer x-( I know there is some hard work on code size
> > > > > reduction on the Orocos side but nearly 2gb is quite huge.
> > > > >
> > > > > Does it exist a "rosmake clean" instruction ?
> > > >
> > > > Let me up this subject,
> > > > after having built the orocos_toolchain_ros it seems it's a bit messy
> > > > with build and installed files. Firstly, rosrun find 2 executables
> > > > for deployer-gnulinux and can't choose.
> > >
> > > We're still looking on how to solve this. The problem is that we
> > > require
> >
> > a
> >
> > > 'make install' in ocl because the headers are included using
> > > 'ocl/Header.hpp' by user code, while they are in the sources in
> > > 'subproject/Header.hpp'. We discussed moving all headers to the ocl/
> > > directory, but this somewhat beats the purpose of the modularisation we
> > > did. An alternative would be to create symlinks from ocl/Header.hpp to
> > > subproject/Header.hpp in ROS_ROOT
> > > environments. This might be the least intrusive step for now.
> > >
> > > Ok, but here it's about a binary
> > >
> > > > Secondly after having used "make clean"
> > > > in all the packages of orocos_toolchain_ros stack, it reduced from
> > > > nearly
> > > > 2gb to 350Mb with is by far more acceptable. Is it any "ros" tool to
> > > > do this ? Would it be possible to add a global "make clean" at the
> > > > root of orocos_toolchain_ros ?
> > >
> > > Did you compile with MinSizeRel ?
> > >
> > > I used the default configuration and didn't thougth about this.
> > > How may I change this with rosmake ?
> >
> > There are different things you can use: I suggest you just edit the
> > orocos- rtt.default.cmake file.
>
> Does I only have to change the rtt config ? What about ocl ?
> rtt_ros_integration ?

Changing orocos-rtt.default.cmake is not recommended, since the file itself
says that you must copy it to orocos-rtt.cmake and edit that file. It will only
influence the RTT itself.

For setting it for all other packages (including OCL), create a rosconfig.cmake
file in the ROS_ROOT directory, and set the build type there, see the
documentation here:

https://code.ros.org/trac/ros/browser/stacks/ros/trunk/core/rosbuild/ros...

>
> > > The make clean is not what you want, since
> > > it will also remove the libraries of the normal 'ros' packages, which
> >
> > don't
> >
> > > have an install step (so it only makes sense for RTT and OCL right
> > > now).
> > >
> > > People are looking at how to reduce code size, but for a development
> >
> > system,
> >
> > > it's always handy to have the .o files still there....
> > >
> > > of course it is. But it is also handy to have a clean function before
> > > copying on the robot (and not to embed the sources).
> > >
> > > In the "classic" orocos toolchain installation I used to copy the
> > > install folder onto my target with the same path as on the building
> > > machine. If I could create my_orocos_toolchain.deb easily I would
> > > install then on my robot instead of copying.
> >
> > You could strip the orocos_toolchain_ros rtt and ocl packages after
> > building
> > and before copying it. AFAIK you can entirely remove the build directory.
>
> I'll try stripping and let you know about resulting size
> "remove the build directory" : This is what "make clean" does no ?

In ROS builds, a make clean will wipe your build dir, and the files in lib/ and
bin/, while doing a rm -rf build, will leave the files in lib/ and bin/
untouched. So you want the latter.

Peter

[ros-users] orocos_toolchain_ros for debian

2011/2/24 Peter Soetens <peter [..] ...>

> On Wednesday 23 February 2011 14:18:34 Willy Lambert wrote:
> > 2011/2/23 Ruben Smits <ruben [dot] smits [..] ...>
> >
> > > On Tuesday 22 February 2011 23:55:26 Willy Lambert wrote:
> > > > 2011/2/22 Peter Soetens
> > > > <peter [..] ...<mailto:peter [..] ...>>
> > > >
> > > > On Monday 21 February 2011 00:32:05 Willy Lambert wrote:
> > > > > 2011/2/8 Willy Lambert
> > > > > <lambert [dot] willy [..] ...<mailto:lambert [dot] willy [..] ...>>
> > > > >
> > > > > >>> The standard way to run executables in ROS packages is with
> > > > > >>> rosrun,
> > > > > >>> e.g;
> > > > > >>>
> > > > > >>> rosrun ocl deployer-gnulinux
> > > > > >>
> > > > > >> Oh yes ! I still don't have the ROS reflexes :)
> > > > > >
> > > > > > it answers :
> > > > > > ard@ard-host-v5:/media/DD_data/home/ard$ rosrun ocl
> > > > > > deployer-gnulinux
> > > > > > [rosrun] You have chosen a non-unique executable, please pick one
> > > > > > of the following:
> > > > > > 1) /home/ard/ros/orocos_toolchain_ros/ocl/bin/deployer-gnulinux
> > > > > > 2)
> > > > > >
> /home/ard/ros/orocos_toolchain_ros/ocl/install/bin/deployer-gnulinu
> > > > > > x
> > > > > > #?
> > > > > >
> > > > > > I know there are egal because one is the "make installed"
> version
> > > > > > of the
> > > > > >
> > > > > > other, by I find it is strange and prevent from starting it
> > > > > > automatically after boot (of course I have solutions to avoid
> this,
> > > > > > but the rosway should work no ?)
> > > > > >
> > > > > > I makes me thinking about folder size and orocos_toolchain_ros is
> > > > > > 1,7Gb
> > > > > > on my computer x-( I know there is some hard work on code size
> > > > > > reduction on the Orocos side but nearly 2gb is quite huge.
> > > > > >
> > > > > > Does it exist a "rosmake clean" instruction ?
> > > > >
> > > > > Let me up this subject,
> > > > > after having built the orocos_toolchain_ros it seems it's a bit
> messy
> > > > > with build and installed files. Firstly, rosrun find 2 executables
> > > > > for deployer-gnulinux and can't choose.
> > > >
> > > > We're still looking on how to solve this. The problem is that we
> > > > require
> > >
> > > a
> > >
> > > > 'make install' in ocl because the headers are included using
> > > > 'ocl/Header.hpp' by user code, while they are in the sources in
> > > > 'subproject/Header.hpp'. We discussed moving all headers to the ocl/
> > > > directory, but this somewhat beats the purpose of the modularisation
> we
> > > > did. An alternative would be to create symlinks from ocl/Header.hpp
> to
> > > > subproject/Header.hpp in ROS_ROOT
> > > > environments. This might be the least intrusive step for now.
> > > >
> > > > Ok, but here it's about a binary
> > > >
> > > > > Secondly after having used "make clean"
> > > > > in all the packages of orocos_toolchain_ros stack, it reduced from
> > > > > nearly
> > > > > 2gb to 350Mb with is by far more acceptable. Is it any "ros" tool
> to
> > > > > do this ? Would it be possible to add a global "make clean" at the
> > > > > root of orocos_toolchain_ros ?
> > > >
> > > > Did you compile with MinSizeRel ?
> > > >
> > > > I used the default configuration and didn't thougth about this.
> > > > How may I change this with rosmake ?
> > >
> > > There are different things you can use: I suggest you just edit the
> > > orocos- rtt.default.cmake file.
> >
> > Does I only have to change the rtt config ? What about ocl ?
> > rtt_ros_integration ?
>
> Changing orocos-rtt.default.cmake is not recommended, since the file itself
> says that you must copy it to orocos-rtt.cmake and edit that file. It will
> only
> influence the RTT itself.
>
> For setting it for all other packages (including OCL), create a
> rosconfig.cmake
> file in the ROS_ROOT directory, and set the build type there, see the
> documentation here:
>
>
> https://code.ros.org/trac/ros/browser/stacks/ros/trunk/core/rosbuild/ros...
>
> >
> > > > The make clean is not what you want, since
> > > > it will also remove the libraries of the normal 'ros' packages, which
> > >
> > > don't
> > >
> > > > have an install step (so it only makes sense for RTT and OCL right
> > > > now).
> > > >
> > > > People are looking at how to reduce code size, but for a development
> > >
> > > system,
> > >
> > > > it's always handy to have the .o files still there....
> > > >
> > > > of course it is. But it is also handy to have a clean function before
> > > > copying on the robot (and not to embed the sources).
> > > >
> > > > In the "classic" orocos toolchain installation I used to copy the
> > > > install folder onto my target with the same path as on the building
> > > > machine. If I could create my_orocos_toolchain.deb easily I would
> > > > install then on my robot instead of copying.
> > >
> > > You could strip the orocos_toolchain_ros rtt and ocl packages after
> > > building
> > > and before copying it. AFAIK you can entirely remove the build
> directory.
> >
> > I'll try stripping and let you know about resulting size
> > "remove the build directory" : This is what "make clean" does no ?
>
> In ROS builds, a make clean will wipe your build dir, and the files in lib/
> and
> bin/, while doing a rm -rf build, will leave the files in lib/ and bin/
> untouched. So you want the latter.
>

This help orocos_toolchain directory is now 1,1Gb with build stuff
if I call
rm `find . -name "build"` -rf
(which is a better solution in front of make clean if I understood what you
said)
It downs to 427 Mb which is more acceptable.

How may I be sure the MinSizeRel has been taken into account ?

>
> Peter
>

Ruben Smits's picture

[ros-users] orocos_toolchain_ros for debian

On Wednesday 23 February 2011 14:18:34 Willy Lambert wrote:
> 2011/2/23 Ruben Smits
> <ruben [dot] smits [..] ...<mailto:ruben [dot] smits [..] ...>>
>
> On Tuesday 22 February 2011 23:55:26 Willy Lambert wrote:
> > 2011/2/22 Peter Soetens
> > <peter [..] ...<mailto:peter [..] ...><mailto:peter@
> > thesourceworks.com<mailto:peter [..] ...>>>
> >
> > On Monday 21 February 2011 00:32:05 Willy Lambert wrote:
> > > 2011/2/8 Willy Lambert
> > > <lambert [dot] willy [..] ...<mailto:lambert [dot] willy [..] ...><mailto:lamb
> > > ert [dot] willy [..] ...<mailto:lambert [dot] willy [..] ...>>>
> > >
> > > >>> The standard way to run executables in ROS packages is with
> > > >>> rosrun,
> > > >>> e.g;
> > > >>>
> > > >>> rosrun ocl deployer-gnulinux
> > > >>
> > > >> Oh yes ! I still don't have the ROS reflexes :)
> > > >
> > > > it answers :
> > > > ard@ard-host-v5:/media/DD_data/home/ard$ rosrun ocl
> > > > deployer-gnulinux
> > > > [rosrun] You have chosen a non-unique executable, please pick
> > > > one of
> > > > the following:
> > > > 1) /home/ard/ros/orocos_toolchain_ros/ocl/bin/deployer-gnulinux
> > > > 2)
> > > > /home/ard/ros/orocos_toolchain_ros/ocl/install/bin/deployer-gnul
> > > > inu
> > > > x
> > > > #?
> > > >
> > > > I know there are egal because one is the "make installed"
> > > > version
> > > > of the
> > > >
> > > > other, by I find it is strange and prevent from starting it
> > > > automatically after boot (of course I have solutions to avoid
> > > > this,
> > > > but the rosway should work no ?)
> > > >
> > > > I makes me thinking about folder size and orocos_toolchain_ros
> > > > is
> > > > 1,7Gb
> > > > on my computer x-( I know there is some hard work on code size
> > > > reduction on the Orocos side but nearly 2gb is quite huge.
> > > >
> > > > Does it exist a "rosmake clean" instruction ?
> > >
> > > Let me up this subject,
> > > after having built the orocos_toolchain_ros it seems it's a bit
> > > messy
> > > with build and installed files. Firstly, rosrun find 2 executables
> > > for
> > > deployer-gnulinux and can't choose.
> >
> > We're still looking on how to solve this. The problem is that we require
> > a 'make install' in ocl because the headers are included using
> > 'ocl/Header.hpp' by user code, while they are in the sources in
> > 'subproject/Header.hpp'. We discussed moving all headers to the ocl/
> > directory, but this somewhat beats the purpose of the modularisation we
> > did. An alternative would be to create symlinks from ocl/Header.hpp to
> > subproject/Header.hpp in ROS_ROOT
> > environments. This might be the least intrusive step for now.
> >
> > Ok, but here it's about a binary
> >
> > > Secondly after having used "make clean"
> > > in all the packages of orocos_toolchain_ros stack, it reduced from
> > > nearly
> > > 2gb to 350Mb with is by far more acceptable. Is it any "ros" tool to
> > > do
> > > this ? Would it be possible to add a global "make clean" at the root
> > > of
> > > orocos_toolchain_ros ?
> >
> > Did you compile with MinSizeRel ?
> >
> > I used the default configuration and didn't thougth about this.
> > How may I change this with rosmake ?
>
> There are different things you can use: I suggest you just edit the orocos-
> rtt.default.cmake file.
>
>
> Does I only have to change the rtt config ? What about ocl ?
> rtt_ros_integration ?
>
> > The make clean is not what you want, since
> > it will also remove the libraries of the normal 'ros' packages, which
> > don't have an install step (so it only makes sense for RTT and OCL
> > right now).
> >
> > People are looking at how to reduce code size, but for a development
> > system, it's always handy to have the .o files still there....
> >
> > of course it is. But it is also handy to have a clean function before
> > copying on the robot (and not to embed the sources).
> >
> > In the "classic" orocos toolchain installation I used to copy the
> > install
> > folder onto my target with the same path as on the building machine. If
> > I
> > could create my_orocos_toolchain.deb easily I would install then on my
> > robot instead of copying.
>
> You could strip the orocos_toolchain_ros rtt and ocl packages after building
> and before copying it. AFAIK you can entirely remove the build directory.
>
> I'll try stripping and let you know about resulting size
> "remove the build directory" : This is what "make clean" does no ?

AFAIR it does, yes.

--Ruben

> > As there is no "install" step yet in ROS, I just copy the complete
> > ros_root folder containing all the stacks (including
> > orocos_toolchain_ros) onto the target. So the .o goes with it. Maybe I
> > could do better, but I don't know how to do it
> >
> >
> >
> >
> > Peter
>
> -- Ruben

[ros-users] orocos_toolchain_ros for debian

2011/2/4 Willy Lambert <lambert [dot] willy [..] ...>

>
>
> 2011/2/3 Steven Bellens <steven [dot] bellens [..] ...>
>
> 2011/2/3 Willy Lambert <lambert [dot] willy [..] ...>:
>> >
>> >
>> > 2011/2/3 Ruben Smits <ruben [dot] smits [..] ...>
>> >>
>> >> On Wednesday 02 February 2011 18:47:48 Willy Lambert wrote:
>> >> > Hi,
>> >> >
>> >> > I am a "standard" orocos user and trying to become a "ros" orocos
>> user.
>> >> > Therefore I built all from git but I had some problems with
>> dependencies
>> >> > since I am on a Debian system. Here is my rosdep.yml :
>> >> >
>> >> > libreadline:
>> >> > ubuntu: libreadline-dev
>> >> > fedora: readline-devel
>> >> > debian: libreadline-dev
>> >> > omniorb:
>> >> > ubuntu: omniorb4 omniidl4 omniorb4-nameserver libomniorb4-1
>> >> > libomniorb4-dev libomnithread3-dev libomnithread3c2 debian: omniorb4
>> >> > omniidl4 omniorb4-nameserver libomniorb4-1 libomniorb4-dev
>> >> > libomnithread3-dev libomnithread3c2 gccxml:
>> >> > ubuntu: gccxml
>> >> > fedora: gccxml
>> >> > debian: gccxml
>> >> > antlr:
>> >> > fedora: antlr3-C antlr-C++
>> >> > ubuntu: antlr libantlr-dev
>> >> > debian: antlr libantlr-dev
>> >> > rubygems:
>> >> > fedora: rubygems
>> >> > ubuntu: rubygems1.8
>> >> > debian: rubygems1.8
>> >> > libxslt:
>> >> > fedora: libxslt-devel
>> >> > ubuntu: libxslt1-dev
>> >> > debian: libxslt1-dev
>> >> > ruby1.8-dev:
>> >> > ubuntu:
>> >> > '10.10': ruby1.8-dev libruby1.8
>> >> > '10.04': ruby1.8-dev libopenssl-ruby1.8
>> >> > '9.10': ruby1.8-dev libopenssl-ruby1.8
>> >> > '9.04': ruby1.8-dev libopenssl-ruby1.8
>> >> > '8.10': ruby1.8-dev libopenssl-ruby1.8
>> >> > '8.04': ruby1.8-dev libopenssl-ruby1.8
>> >> > fedora: ruby ruby-devel openssl-devel
>> >> > debian: ruby1.8-dev libruby1.8
>> >> >
>> >> >
>> >> > I would rather have send a patch but I do not really know how to do
>> this
>> >> > (I
>> >> > am not used to open source processes)
>> >>
>> >> If you used git you can easily create a patch with the 'git
>> format-patch'
>> >> command.
>> >>
>> >> >
>> >> > I don't know where to post this between Orocos or ROS mailing list.
>> What
>> >> > would you suggest ?
>> >>
>> >> Both are fine.
>> >
>> > We using the command lines from
>> http://www.ros.org/wiki/orocos_toolchain_ros
>> > I have an error when cloning the repository :
>> >
>> > ard@ard-host-v5:/media/DD_data/home/ard/ros$ git clone
>> > http://git.mech.kuleuven.be/robotics/orocos_toolchain_ros.git
>> > Cloning into orocos_toolchain_ros...
>> > error: inflate: data stream error (incorrect header check)
>> >
>> > Is this normal ?
>>
>> I get the same error, but AFAIK it doesn't cause any further
>> disfunctioning.
>>
>> Steven
>>
>>
> it seems to miss the lua-dev dependency in the rosdem.yaml. Do you know
> this Ruben ?
>
>
It may not be the only one, here is the outpu of my rosinstall command :

ard@ard-host-v5:~/ros/orocos_toolchain_ros$ rosmake
[ rosmake ] No package specified. Building stack
['orocos_toolchain_ros']

[ rosmake ] Packages requested are:
['orocos_toolchain_ros']

[ rosmake ] Logging to
directory/home/ard/.ros/rosmake/rosmake_output-20110204-004245

[ rosmake ] Expanded args ['orocos_toolchain_ros'] to:
['log4cpp', 'rtt_ros_integration_example', 'ocl', 'utilrb', 'typelib',
'rtt', 'hello-7-deployment', 'helloworld', 'hello-2-properties',
'hello-5-services', 'controller-1', 'hello-3-dataports',
'hello-6-scripting', 'hello-1-task-execution', 'hello-4-operations',
'utilmm', 'orogen', 'rtt_ros_integration_nav_msgs', 'rtt_ros_integration',
'rtt_ros_param', 'rtt_ros_integration_geometry_msgs',
'rtt_ros_integration_roslib_msgs', 'rtt_ros_integration_std_msgs']
[ rosmake ] Checking rosdeps compliance for packages orocos_toolchain_ros.
This may take a few seconds.
Invalid manifest
file[/home/ard/ros/orocos_toolchain_ros/rtt_exercises/rtt-exercises/hello-7-deployment/manifest.xml]:
missing required 'license' element
Invalid manifest
file[/home/ard/ros/orocos_toolchain_ros/rtt_exercises/rtt-exercises/hello-7-deployment/manifest.xml]:
missing required 'author' element
Invalid manifest
file[/home/ard/ros/orocos_toolchain_ros/rtt_exercises/rtt-exercises/helloworld/manifest.xml]:
missing required 'license' element
Invalid manifest
file[/home/ard/ros/orocos_toolchain_ros/rtt_exercises/rtt-exercises/helloworld/manifest.xml]:
missing required 'author' element
Invalid manifest
file[/home/ard/ros/orocos_toolchain_ros/rtt_exercises/rtt-exercises/hello-2-properties/manifest.xml]:
missing required 'license' element
Invalid manifest
file[/home/ard/ros/orocos_toolchain_ros/rtt_exercises/rtt-exercises/hello-2-properties/manifest.xml]:
missing required 'author' element
Invalid manifest
file[/home/ard/ros/orocos_toolchain_ros/rtt_exercises/rtt-exercises/hello-5-services/manifest.xml]:
missing required 'license' element
Invalid manifest
file[/home/ard/ros/orocos_toolchain_ros/rtt_exercises/rtt-exercises/hello-5-services/manifest.xml]:
missing required 'author' element
Invalid manifest
file[/home/ard/ros/orocos_toolchain_ros/rtt_exercises/rtt-exercises/controller-1/manifest.xml]:
missing required 'license' element
Invalid manifest
file[/home/ard/ros/orocos_toolchain_ros/rtt_exercises/rtt-exercises/controller-1/manifest.xml]:
missing required 'author' element
Invalid manifest
file[/home/ard/ros/orocos_toolchain_ros/rtt_exercises/rtt-exercises/hello-3-dataports/manifest.xml]:
missing required 'license' element
Invalid manifest
file[/home/ard/ros/orocos_toolchain_ros/rtt_exercises/rtt-exercises/hello-3-dataports/manifest.xml]:
missing required 'author' element
Invalid manifest
file[/home/ard/ros/orocos_toolchain_ros/rtt_exercises/rtt-exercises/hello-6-scripting/manifest.xml]:
missing required 'license' element
Invalid manifest
file[/home/ard/ros/orocos_toolchain_ros/rtt_exercises/rtt-exercises/hello-6-scripting/manifest.xml]:
missing required 'author' element
Invalid manifest
file[/home/ard/ros/orocos_toolchain_ros/rtt_exercises/rtt-exercises/hello-1-task-execution/manifest.xml]:
missing required 'license' element
Invalid manifest
file[/home/ard/ros/orocos_toolchain_ros/rtt_exercises/rtt-exercises/hello-1-task-execution/manifest.xml]:
missing required 'author' element
Invalid manifest
file[/home/ard/ros/orocos_toolchain_ros/rtt_exercises/rtt-exercises/hello-4-operations/manifest.xml]:
missing required 'license' element
Invalid manifest
file[/home/ard/ros/orocos_toolchain_ros/rtt_exercises/rtt-exercises/hello-4-operations/manifest.xml]:
missing required 'author' element
Invalid manifest
file[/home/ard/ros/orocos_toolchain_ros/rtt_exercises/rtt-exercises/hello-7-deployment/manifest.xml]:
missing required 'license' element
Invalid manifest
file[/home/ard/ros/orocos_toolchain_ros/rtt_exercises/rtt-exercises/hello-7-deployment/manifest.xml]:
missing required 'author' element
Invalid manifest
file[/home/ard/ros/orocos_toolchain_ros/rtt_exercises/rtt-exercises/helloworld/manifest.xml]:
missing required 'license' element
Invalid manifest
file[/home/ard/ros/orocos_toolchain_ros/rtt_exercises/rtt-exercises/helloworld/manifest.xml]:
missing required 'author' element
Invalid manifest
file[/home/ard/ros/orocos_toolchain_ros/rtt_exercises/rtt-exercises/hello-2-properties/manifest.xml]:
missing required 'license' element
Invalid manifest
file[/home/ard/ros/orocos_toolchain_ros/rtt_exercises/rtt-exercises/hello-2-properties/manifest.xml]:
missing required 'author' element
Invalid manifest
file[/home/ard/ros/orocos_toolchain_ros/rtt_exercises/rtt-exercises/hello-5-services/manifest.xml]:
missing required 'license' element
Invalid manifest
file[/home/ard/ros/orocos_toolchain_ros/rtt_exercises/rtt-exercises/hello-5-services/manifest.xml]:
missing required 'author' element
Invalid manifest
file[/home/ard/ros/orocos_toolchain_ros/rtt_exercises/rtt-exercises/controller-1/manifest.xml]:
missing required 'license' element
Invalid manifest
file[/home/ard/ros/orocos_toolchain_ros/rtt_exercises/rtt-exercises/controller-1/manifest.xml]:
missing required 'author' element
Invalid manifest
file[/home/ard/ros/orocos_toolchain_ros/rtt_exercises/rtt-exercises/hello-3-dataports/manifest.xml]:
missing required 'license' element
Invalid manifest
file[/home/ard/ros/orocos_toolchain_ros/rtt_exercises/rtt-exercises/hello-3-dataports/manifest.xml]:
missing required 'author' element
Invalid manifest
file[/home/ard/ros/orocos_toolchain_ros/rtt_exercises/rtt-exercises/hello-6-scripting/manifest.xml]:
missing required 'license' element
Invalid manifest
file[/home/ard/ros/orocos_toolchain_ros/rtt_exercises/rtt-exercises/hello-6-scripting/manifest.xml]:
missing required 'author' element
Invalid manifest
file[/home/ard/ros/orocos_toolchain_ros/rtt_exercises/rtt-exercises/hello-1-task-execution/manifest.xml]:
missing required 'license' element
Invalid manifest
file[/home/ard/ros/orocos_toolchain_ros/rtt_exercises/rtt-exercises/hello-1-task-execution/manifest.xml]:
missing required 'author' element
Invalid manifest
file[/home/ard/ros/orocos_toolchain_ros/rtt_exercises/rtt-exercises/hello-4-operations/manifest.xml]:
missing required 'license' element
Invalid manifest
file[/home/ard/ros/orocos_toolchain_ros/rtt_exercises/rtt-exercises/hello-4-operations/manifest.xml]:
missing required 'author' element
Invalid manifest
file[/home/ard/ros/orocos_toolchain_ros/rtt_exercises/rtt-exercises/hello-7-deployment/manifest.xml]:
missing required 'license' element
Invalid manifest
file[/home/ard/ros/orocos_toolchain_ros/rtt_exercises/rtt-exercises/hello-7-deployment/manifest.xml]:
missing required 'author' element
Invalid manifest
file[/home/ard/ros/orocos_toolchain_ros/rtt_exercises/rtt-exercises/helloworld/manifest.xml]:
missing required 'license' element
Invalid manifest
file[/home/ard/ros/orocos_toolchain_ros/rtt_exercises/rtt-exercises/helloworld/manifest.xml]:
missing required 'author' element
Invalid manifest
file[/home/ard/ros/orocos_toolchain_ros/rtt_exercises/rtt-exercises/hello-2-properties/manifest.xml]:
missing required 'license' element
Invalid manifest
file[/home/ard/ros/orocos_toolchain_ros/rtt_exercises/rtt-exercises/hello-2-properties/manifest.xml]:
missing required 'author' element
Invalid manifest
file[/home/ard/ros/orocos_toolchain_ros/rtt_exercises/rtt-exercises/hello-5-services/manifest.xml]:
missing required 'license' element
Invalid manifest
file[/home/ard/ros/orocos_toolchain_ros/rtt_exercises/rtt-exercises/hello-5-services/manifest.xml]:
missing required 'author' element
Invalid manifest
file[/home/ard/ros/orocos_toolchain_ros/rtt_exercises/rtt-exercises/controller-1/manifest.xml]:
missing required 'license' element
Invalid manifest
file[/home/ard/ros/orocos_toolchain_ros/rtt_exercises/rtt-exercises/controller-1/manifest.xml]:
missing required 'author' element
Invalid manifest
file[/home/ard/ros/orocos_toolchain_ros/rtt_exercises/rtt-exercises/hello-3-dataports/manifest.xml]:
missing required 'license' element
Invalid manifest
file[/home/ard/ros/orocos_toolchain_ros/rtt_exercises/rtt-exercises/hello-3-dataports/manifest.xml]:
missing required 'author' element
Invalid manifest
file[/home/ard/ros/orocos_toolchain_ros/rtt_exercises/rtt-exercises/hello-6-scripting/manifest.xml]:
missing required 'license' element
Invalid manifest
file[/home/ard/ros/orocos_toolchain_ros/rtt_exercises/rtt-exercises/hello-6-scripting/manifest.xml]:
missing required 'author' element
Invalid manifest
file[/home/ard/ros/orocos_toolchain_ros/rtt_exercises/rtt-exercises/hello-1-task-execution/manifest.xml]:
missing required 'license' element
Invalid manifest
file[/home/ard/ros/orocos_toolchain_ros/rtt_exercises/rtt-exercises/hello-1-task-execution/manifest.xml]:
missing required 'author' element
Invalid manifest
file[/home/ard/ros/orocos_toolchain_ros/rtt_exercises/rtt-exercises/hello-4-operations/manifest.xml]:
missing required 'license' element
Invalid manifest
file[/home/ard/ros/orocos_toolchain_ros/rtt_exercises/rtt-exercises/hello-4-operations/manifest.xml]:
missing required 'author' element
[ rosmake ] rosdep check passed all system dependencies in
packages

[ rosmake ] Starting >>>
tools/rospack

[ rosmake ] Finished <<<
tools/rospack

[ rosmake ] Starting >>>
3rdparty/gtest

[ rosmake ] Finished <<<
3rdparty/gtest

[ rosmake ] Starting >>>
core/genmsg_cpp

[ rosmake ] Finished <<<
core/genmsg_cpp

[rosmake-0] Starting >>> log4cpp [ make
]

[rosmake-1] Starting >>> roslang [ make
]

[rosmake-1] Finished <<< roslang No Makefile in package
roslang

[rosmake-2] Starting >>> roslib [ make
]

[rosmake-3] Starting >>> xmlrpcpp [ make
]

[rosmake-1] Starting >>> rtt [ make
]

[rosmake-3] Finished <<< xmlrpcpp [PASS] [ 0.44 seconds
]

[rosmake-3] Starting >>> rosbuild [ make
]

[rosmake-3] Finished <<< rosbuild No Makefile in package
rosbuild

[rosmake-3] Starting >>> utilrb [ make
]

[rosmake-0] Finished <<< log4cpp [PASS] [ 0.93 seconds
]

[rosmake-0] Starting >>> utilmm [ make
]

[rosmake-2] Finished <<< roslib [PASS] [ 1.08 seconds
]

[rosmake-2] Starting >>> rosconsole [ make
]

[rosmake-1] Finished <<< rtt [PASS] [ 1.28 seconds
]

[rosmake-1] Starting >>> ocl [ make
]

[ rosmake ] All 19 lines
{-------------------------------------------------------------------------------
mkdir -p bin
cd build && cmake -Wdev -DCMAKE_TOOLCHAIN_FILE=`rospack find
rosbuild`/rostoolchain.cmake -DCMAKE_INSTALL_PREFIX=`rospack find
utilmm`/install ..
[rosbuild] Building package utilmm
[rosbuild] Including /home/ard/ros/ros/core/roscpp/cmake/roscpp.cmake
[rosbuild] Including /home/ard/ros/ros/core/rospy/cmake/rospy.cmake
[rosbuild] Including /home/ard/ros/ros/core/roslisp/cmake/roslisp.cmake
-- Found The Following Boost Libraries:
-- unit_test_framework
-- Boost Version: ..
-- cannot find boost/graph
CMake Error at build/orocos-toolchain-utilmm/cmake/FindBoost.cmake:367
(MESSAGE):
Boost and/or some required components not found. Please install the
Boost
libraries AND development packages
Call Stack (most recent call first):
build/orocos-toolchain-utilmm/CMakeLists.txt:9 (FIND_PACKAGE)

-- Configuring incomplete, errors occurred!
-------------------------------------------------------------------------------}
[ rosmake ] Output from build of package utilmm written to:
[ rosmake ]
/home/ard/.ros/rosmake/rosmake_output-20110204-004245/utilmm/build_output.log
[rosmake-0] Finished <<< utilmm [FAIL] [ 0.41 seconds
]

[ rosmake ] Halting due to failure in package utilmm.
[ rosmake ] Waiting for other threads to
complete.
[rosmake-2] Finished <<< rosconsole [PASS] [ 0.70 seconds
]

[ rosmake ] All 18 linestilrb: 19.5 sec ] [ ocl: 18.7 sec
] [ 2 Active
9/45 Complete ]
{-------------------------------------------------------------------------------
gem install rake hoe rubyforge flexmock
ERROR: Error installing hoe:
hoe requires RubyGems version >= 1.4. Try 'gem update --system' to
update RubyGems itself.
Could not find main page README
Could not find main page README
Could not find main page README
Could not find main page README
Successfully installed rake-0.8.7
Successfully installed rubyforge-2.0.4
Successfully installed flexmock-0.8.11
3 gems installed
Installing ri documentation for rake-0.8.7...
Installing ri documentation for rubyforge-2.0.4...
Installing ri documentation for flexmock-0.8.11...
Installing RDoc documentation for rake-0.8.7...
Installing RDoc documentation for rubyforge-2.0.4...
Installing RDoc documentation for flexmock-0.8.11...
-------------------------------------------------------------------------------}
[ rosmake ] Output from build of package utilrb written to:
[ rosmake ]
/home/ard/.ros/rosmake/rosmake_output-20110204-004245/utilrb/build_output.log
[rosmake-3] Finished <<< utilrb [FAIL] [ 19.49 seconds
]

[ rosmake ] Halting due to failure in package utilrb.
[ rosmake ] Waiting for other threads to
complete.
[rosmake-1] Finished <<< ocl [PASS] [ 26.64 seconds
]

[ rosmake ]
Results:

[ rosmake ] Built 12 packages with 2
failures.

[ rosmake ] Summary output to
directory

[ rosmake ]
/home/ard/.ros/rosmake/rosmake_output-20110204-004245

ard@ard-host-v5:~/ros/orocos_toolchain_ros$

>
>
>
>
>> > At the end it seems to have work properly as I have this in the folder
>> (and
>> > succeed a build yesterday) :
>> >
>> > ard@ard-host-v5:/media/DD_data/home/ard/ros/orocos_toolchain_ros$ ls
>> > CMakeLists.txt env.sh ocl rosdep.yaml rtt_exercises
>> > rtt_ros_integration_example stack.xml utilmm
>> > env.mk Makefile orogen rtt rtt_ros_integration
>> > rtt_ros_integration_std_msgs typelib utilrb
>> > ard@ard-host-v5:/media/DD_data/home/ard/ros/orocos_toolchain_ros$
>> >
>> >
>> >
>> > _______________________________________________
>> > ros-users mailing list
>> > ros-users [..] ...
>> > https://code.ros.org/mailman/listinfo/ros-users
>> >
>> >
>> --
>> Orocos-Users mailing list
>> Orocos-Users [..] ...
>> http://lists.mech.kuleuven.be/mailman/listinfo/orocos-users
>>
>
>