2011/2/3 Ruben Smits <ruben [dot] smits [..] ...>:
> On Thursday 03 February 2011 18:20:24 Willy Lambert wrote:
>> I am sorry but I am lost with git :(
>>
>> I tried hard to learn how it works and did this :
>>
>> $ 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)
>>
>> $ cd 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 $ git checkout --track -b
>> orocos_toolchain_ros-0.2 origin/orocos_toolchain_ros-0.2 Branch
>> orocos_toolchain_ros-0.2 set up to track remote branch
>> orocos_toolchain_ros-0.2 from origin. Switched to a new branch
>> 'orocos_toolchain_ros-0.2'
>> $ git remote show origin
>> * remote origin
>>   Fetch URL: http://git.mech.kuleuven.be/robotics/orocos_toolchain_ros.git
>>   Push  URL: http://git.mech.kuleuven.be/robotics/orocos_toolchain_ros.git
>>   HEAD branch: master
>>   Remote branches:
>>     cturtle                  tracked
>>     cturtle_next             tracked
>>     master                   tracked
>>     orocos_toolchain_ros-0.2 tracked
>>     rosparam                 tracked
>>     unstable                 tracked
>>     unstable_next            tracked
>>   Local branches configured for 'git pull':
>>     master                   merges with remote master
>>     orocos_toolchain_ros-0.2 merges with remote orocos_toolchain_ros-0.2
>>   Local refs configured for 'git push':
>>     master                   pushes to master                   (up to date)
>> orocos_toolchain_ros-0.2 pushes to orocos_toolchain_ros-0.2 (up to date)
>> ard@ard-host-v5:/media/DD_data/home/ard/ros/orocos_toolchain_ros$ ls ocl
>>
>>
>> and there is nothing :(
>
> First do 'git submodule init' then do 'git submodule update' in your
> orocos_toolchain_ros directory. If this is still not working, what version of
> git are you using? ('git --version')
>
>>
>> If I may :
>> http://www.ros.org/wiki/orocos_toolchain_ros
>> should detail the "Make sure to either check out the unstable or cturtle
>> branch" because it clones the master branch by default and git is not a
>> piece of cake if you never played with it.
>>
>
> We'll update this asap.

Done

Steven

>
> -- Ruben
>
>>
>>
>>
>> 2011/2/3 Willy Lambert
>> <lambert [dot] willy [..] ...lambert [dot] willy [..] ...>> Thanks for
>> support, I was thinking about using Diamondback anyway, so I'll first
>> install this new version of ROS and then retry to have the orocos_toolchain
>> being aware a versionning.
>>
>>
>> 2011/2/3 Steven Bellens
>> <steven [dot] bellens [..] ...steven [dot] bellens [..] ...>>
>>
>> 2011/2/2 Peter Soetens
> <peter [..] ...peter [..] ...>>:
>> > On Wed, Feb 2, 2011 at 11:45 PM, Peter Soetens
> <peter [..] ...peter [..] ...>> wrote:
>> >> On Wed, Feb 2, 2011 at 9:06 PM, Willy Lambert
> <lambert [dot] willy [..] ...lambert [dot] willy [..] ...>> wrote:
>> >>> 2011/2/2 Willy Lambert
>> >>> <lambert [dot] willy [..] ...lambert [dot] willy [..] ...>>
>> >>>
>> >>>> 2011/2/2 Steven Bellens
>> >>>> <steven [dot] bellens [..] ...steven [dot] bellens [..] ...
>> >>>> ven.be>>
>> >>>>
>> >>>>> 2011/2/2 Willy Lambert
> <lambert [dot] willy [..] ...lambert [dot] willy [..] ...>>:
>> >>>>> > It is an Orocos project but I aim to keep it as integrated
>> >>>>> > as possible in
>> >>>>> > ROS. In other word does orocreate-pkg does "more" than
>> >>>>> > roscreate-pkg ? or
>> >>>>> > are they simply different ?
>> >>>>>
>> >>>>> They are different in the example code they generate, but the
>> >>>>> package
>> >>>>> generated by orocreate-pkg will be fully compatible with your
>> >>>>> ROS
>> >>>>> build system. Difference is mainly the CMakeLists.txt which
>> >>>>> lists the
>> >>>>> different available orocos macros for building executables,
>> >>>>> components, typekits, etc. Beside that there are a lot of
>> >>>>> example
>> >>>>> files which I haven't checked myself yet.
>> >>>>
>> >>>> Ok thanks for these answers. I need these Orocos specfic macros
>> >>>> and I
>> >>>> don't really need examples.
>> >>>
>> >>> orocreate-pkg is still supposed to be into the ocl/script/pkg folder
>> >>> ?
>> >>> Because it is not in mine (it is a git clone from the
>> >>> orocos_toolchain_ros)
>> >>
>> >> Did you do a 'git submodule update' ?
>> >>
>> >> the submodule system is used to pull in the ocl and rtt sources from
>> >> the official
>> >> repositories.
>> >>
>> >> We probably should document this or add a script with a
>> >> self-explaining name in the top level directory...
>> >
>> > Also make sure that you are on the orocos_toolchain_ros-0.2 branch,
>> > which is actually
>> > meant for 'dturtle' (current unstable of ros), but afaikt, I'm using
>> > it with cturtle without problems.
>>
>> Currently, the only difference between the branches
>> (orocos_toolchain_ros_0.2 for Diamondback and CTurtle or CTurtle_next
>> for CTurtle) is in the typekit generation which will fail because of
>> the moving of some ROS headers to another package. They will both
>> compile fine on both ROS distributions, you only get the errors when
>> you compile typekits with the rtt_ros_integration functionality.
>>
>> After getting all the submodule repos, run the orocreate-pkg script as:
>>
>> rosrun ocl orocreate-pkg
>>
>> Steven
>>
>> > Peter
>> >
>> >> Peter
>> >>
>> >>>>> Steven
>> >>>>>
>> >>>>> > 2011/2/2 Steven Bellens
>> >>>>> > <steven [dot] bellens [..] ... >> >>>>> > .kuleuven.be>>
>> >>>>> >
>> >>>>> >> 2011/2/2 Willy Lambert
> <lambert [dot] willy [..] ...lambert [dot] willy [..] ...>>:
>> >>>>> >> > Hi all,
>> >>>>> >> >
>> >>>>> >> > I would like to create a new project for my
>> >>>>> >> > orocos_toolchain_ros
>> >>>>> >> > into a
>> >>>>> >> > ros
>> >>>>> >> > warking system, what should I use ?
>> >>>>> >> >
>> >>>>> >> > orocreate-pkg
>> >>>>> >> > or
>> >>>>> >> > roscreate-pkg ?
>> >>>>> >>
>> >>>>> >> If it's an Orocos project (which I suppose it is as you
>> >>>>> >> ask it here), orocreate-pkg is the way to go.
>> >>>>> >>
>> >>>>> >> Steven
>> >>>
>> >>> --
>> >>> Orocos-Users mailing list
>> >>> Orocos-Users [..] ...<mailto:Orocos-Users [..] ....k
>> >>> uleuven.be>
>> >>> http://lists.mech.kuleuven.be/mailman/listinfo/orocos-users
>

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

> On Thursday 03 February 2011 18:20:24 Willy Lambert wrote:
> > I am sorry but I am lost with git :(
> >
> > I tried hard to learn how it works and did this :
> >
> > $ 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)
> >
> > $ cd 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 $ git checkout --track -b
> > orocos_toolchain_ros-0.2 origin/orocos_toolchain_ros-0.2 Branch
> > orocos_toolchain_ros-0.2 set up to track remote branch
> > orocos_toolchain_ros-0.2 from origin. Switched to a new branch
> > 'orocos_toolchain_ros-0.2'
> > $ git remote show origin
> > * remote origin
> > Fetch URL:
> http://git.mech.kuleuven.be/robotics/orocos_toolchain_ros.git
> > Push URL:
> http://git.mech.kuleuven.be/robotics/orocos_toolchain_ros.git
> > HEAD branch: master
> > Remote branches:
> > cturtle tracked
> > cturtle_next tracked
> > master tracked
> > orocos_toolchain_ros-0.2 tracked
> > rosparam tracked
> > unstable tracked
> > unstable_next tracked
> > Local branches configured for 'git pull':
> > master merges with remote master
> > orocos_toolchain_ros-0.2 merges with remote orocos_toolchain_ros-0.2
> > Local refs configured for 'git push':
> > master pushes to master (up to
> date)
> > orocos_toolchain_ros-0.2 pushes to orocos_toolchain_ros-0.2 (up to date)
> > ard@ard-host-v5:/media/DD_data/home/ard/ros/orocos_toolchain_ros$ ls ocl
> >
> >
> > and there is nothing :(
>
> First do 'git submodule init' then do 'git submodule update' in your
> orocos_toolchain_ros directory.

it's by far better with these :

$ 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)

ard@ard-host-v5:/media/DD_data/home/ard/ros/orocos_toolchain_ros$ git
checkout --track -b orocos_toolchain_ros-0.2 origin/orocos_toolchain_ros-0.2

Branch orocos_toolchain_ros-0.2 set up to track remote branch
orocos_toolchain_ros-0.2 from origin.
Switched to a new branch 'orocos_toolchain_ros-0.2'
ard@ard-host-v5:/media/DD_data/home/ard/ros/orocos_toolchain_ros$ git
submodule init
Submodule 'log4cpp' (git://gitorious.org/orocos-toolchain/log4cpp.git)
registered for path 'log4cpp'
Submodule 'ocl' (git://gitorious.org/orocos-toolchain/ocl.git) registered
for path 'ocl'
Submodule 'rtt' (git://gitorious.org/orocos-toolchain/rtt.git) registered
for path 'rtt'
Submodule 'rtt_exercises' (git://github.com/psoetens/orocos-rtt-examples.git)
registered for path 'rtt_exercises'
ard@ard-host-v5:/media/DD_data/home/ard/ros/orocos_toolchain_ros$ git
submodule update
Cloning into log4cpp...
remote: Counting objects: 512, done.
remote: Compressing objects: 100% (429/429), done.
remote: Total 512 (delta 242), reused 242 (delta 69)
Receiving objects: 100% (512/512), 683.46 KiB | 622 KiB/s, done.
Resolving deltas: 100% (242/242), done.
Submodule path 'log4cpp': checked out
'56487871abfff49ebbc5713efcbfe7288015e088'
Cloning into ocl...
remote: Counting objects: 11255, done.
remote: Compressing objects: 100% (4076/4076), done.
remote: Total 11255 (delta 7953), reused 10058 (delta 7087)
Receiving objects: 100% (11255/11255), 3.92 MiB | 757 KiB/s, done.
Resolving deltas: 100% (7953/7953), done.
Submodule path 'ocl': checked out '6a87e3cf6496bf03b75eae1c4c4a0164e88aed01'
Cloning into rtt...
remote: Counting objects: 53781, done.
remote: Compressing objects: 100% (13052/13052), done.
remote: Total 53781 (delta 39622), reused 50595 (delta 36990)
Receiving objects: 100% (53781/53781), 18.53 MiB | 766 KiB/s, done.
Resolving deltas: 100% (39622/39622), done.
Submodule path 'rtt': checked out '56c6d5540dc4bc3f63e2dc972c11a873cb5338f9'
Cloning into rtt_exercises...
remote: Counting objects: 900, done.
remote: Compressing objects: 100% (465/465), done.
remote: Total 900 (delta 554), reused 741 (delta 426)
Receiving objects: 100% (900/900), 243.09 KiB | 370 KiB/s, done.
Resolving deltas: 100% (554/554), done.
Submodule path 'rtt_exercises': checked out
'4e3ee1981bb8e4f2b4549df75925af1cdf6cbb27'
ard@ard-host-v5:/media/DD_data/home/ard/ros/orocos_toolchain_ros$ ls ocl
bin COPYING doc INSTALL Makefile
ocl README taskbrowser
CMakeLists.txt debian Doxyfile.in logging manifest.xml
orocos-ocl.default.cmake reporting timer
config deployment helloworld lua NEWS
orocos-ocl.pc.in scripts
ard@ard-host-v5:/media/DD_data/home/ard/ros/orocos_toolchain_ros$

> If this is still not working, what version of
> git are you using? ('git --version')
>

for info : git version 1.7.2.3

>
> >
> > If I may :
> > http://www.ros.org/wiki/orocos_toolchain_ros
> > should detail the "Make sure to either check out the unstable or cturtle
> > branch" because it clones the master branch by default and git is not a
> > piece of cake if you never played with it.
> >
>
> We'll update this asap.
>

btw, can we use a .rosinstall instead of git clone ? Is it planned ?

>
> -- Ruben
>
> >
> >
> >
> > 2011/2/3 Willy Lambert
> > <lambert [dot] willy [..] ...lambert [dot] willy [..] ...>> Thanks for
> > support, I was thinking about using Diamondback anyway, so I'll first
> > install this new version of ROS and then retry to have the
> orocos_toolchain
> > being aware a versionning.
> >
> >
> > 2011/2/3 Steven Bellens
> > <steven [dot] bellens [..] ...steven [dot] bellens [..] ...
> >>
> >
> > 2011/2/2 Peter Soetens
> <peter [..] ...peter [..] ...>>:
> > > On Wed, Feb 2, 2011 at 11:45 PM, Peter Soetens
> <peter [..] ...peter [..] ...>> wrote:
> > >> On Wed, Feb 2, 2011 at 9:06 PM, Willy Lambert
> <lambert [dot] willy [..] ...lambert [dot] willy [..] ...>> wrote:
> > >>> 2011/2/2 Willy Lambert
> > >>> <lambert [dot] willy [..] ...lambert [dot] willy [..] ...>>
> > >>>
> > >>>> 2011/2/2 Steven Bellens
> > >>>> <steven [dot] bellens [..] ...steven [dot] bellens [..] ...
> > >>>> ven.be>>
> > >>>>
> > >>>>> 2011/2/2 Willy Lambert
> <lambert [dot] willy [..] ...lambert [dot] willy [..] ...>>:
> > >>>>> > It is an Orocos project but I aim to keep it as integrated
> > >>>>> > as possible in
> > >>>>> > ROS. In other word does orocreate-pkg does "more" than
> > >>>>> > roscreate-pkg ? or
> > >>>>> > are they simply different ?
> > >>>>>
> > >>>>> They are different in the example code they generate, but the
> > >>>>> package
> > >>>>> generated by orocreate-pkg will be fully compatible with your
> > >>>>> ROS
> > >>>>> build system. Difference is mainly the CMakeLists.txt which
> > >>>>> lists the
> > >>>>> different available orocos macros for building executables,
> > >>>>> components, typekits, etc. Beside that there are a lot of
> > >>>>> example
> > >>>>> files which I haven't checked myself yet.
> > >>>>
> > >>>> Ok thanks for these answers. I need these Orocos specfic macros
> > >>>> and I
> > >>>> don't really need examples.
> > >>>
> > >>> orocreate-pkg is still supposed to be into the ocl/script/pkg folder
> > >>> ?
> > >>> Because it is not in mine (it is a git clone from the
> > >>> orocos_toolchain_ros)
> > >>
> > >> Did you do a 'git submodule update' ?
> > >>
> > >> the submodule system is used to pull in the ocl and rtt sources from
> > >> the official
> > >> repositories.
> > >>
> > >> We probably should document this or add a script with a
> > >> self-explaining name in the top level directory...
> > >
> > > Also make sure that you are on the orocos_toolchain_ros-0.2 branch,
> > > which is actually
> > > meant for 'dturtle' (current unstable of ros), but afaikt, I'm using
> > > it with cturtle without problems.
> >
> > Currently, the only difference between the branches
> > (orocos_toolchain_ros_0.2 for Diamondback and CTurtle or CTurtle_next
> > for CTurtle) is in the typekit generation which will fail because of
> > the moving of some ROS headers to another package. They will both
> > compile fine on both ROS distributions, you only get the errors when
> > you compile typekits with the rtt_ros_integration functionality.
> >
> > After getting all the submodule repos, run the orocreate-pkg script as:
> >
> > rosrun ocl orocreate-pkg
> >
> > Steven
> >
> > > Peter
> > >
> > >> Peter
> > >>
> > >>>>> Steven
> > >>>>>
> > >>>>> > 2011/2/2 Steven Bellens
> > >>>>> > <steven [dot] bellens [..] ... > > >>>>> > .kuleuven.be>>
> > >>>>> >
> > >>>>> >> 2011/2/2 Willy Lambert
> <lambert [dot] willy [..] ...lambert [dot] willy [..] ...>>:
> > >>>>> >> > Hi all,
> > >>>>> >> >
> > >>>>> >> > I would like to create a new project for my
> > >>>>> >> > orocos_toolchain_ros
> > >>>>> >> > into a
> > >>>>> >> > ros
> > >>>>> >> > warking system, what should I use ?
> > >>>>> >> >
> > >>>>> >> > orocreate-pkg
> > >>>>> >> > or
> > >>>>> >> > roscreate-pkg ?
> > >>>>> >>
> > >>>>> >> If it's an Orocos project (which I suppose it is as you
> > >>>>> >> ask it here), orocreate-pkg is the way to go.
> > >>>>> >>
> > >>>>> >> Steven
> > >>>
> > >>> --
> > >>> Orocos-Users mailing list
> > >>> Orocos-Users [..] ...<mailto:Orocos-Users [..] ....k
> > >>> uleuven.be>
> > >>> http://lists.mech.kuleuven.be/mailman/listinfo/orocos-users
>