OCL's manifest.xml dependencies

I believe there is an issue with getting the manifest.xml file right for ocl.

autoproj requires the dependency 'readline', while rosmake depends on
'libreadline-dev'. I think there are similar 'issues' with names like
'omniorb', 'boost', etc. Where each dependency system has used other names.

Should we update the .osdeps files or what should be do ?

Peter

Ruben Smits's picture

OCL's manifest.xml dependencies

On Thursday 02 December 2010 10:13:26 Peter Soetens wrote:
> I believe there is an issue with getting the manifest.xml file right for
> ocl.
>
> autoproj requires the dependency 'readline', while rosmake depends on
> 'libreadline-dev'. I think there are similar 'issues' with names like
> 'omniorb', 'boost', etc. Where each dependency system has used other names.
> Should we update the .osdeps files or what should be do ?

libreadline and omniorb are defined by our own orocos_toolchain_ros stack so we
could easily change them there without having to change the autoproj osdeps.
Boost is a ros-core osdep and is called 'boost', I guess this is the same as
in autoproj no?

Ruben

OCL's manifest.xml dependencies

On Thursday 02 December 2010 10:21:19 Ruben Smits wrote:
> On Thursday 02 December 2010 10:13:26 Peter Soetens wrote:
> > I believe there is an issue with getting the manifest.xml file right for
> > ocl.
> >
> > autoproj requires the dependency 'readline', while rosmake depends on
> > 'libreadline-dev'. I think there are similar 'issues' with names like
> > 'omniorb', 'boost', etc. Where each dependency system has used other
> > names. Should we update the .osdeps files or what should be do ?
>
> libreadline and omniorb are defined by our own orocos_toolchain_ros stack
> so we could easily change them there without having to change the autoproj
> osdeps.

But how can the rtt/ocl package than work outside of the orocos_toolchain_ros
stack, but with the 'rosmake' system for building it ?

> Boost is a ros-core osdep and is called 'boost', I guess this is
> the same as in autoproj no?

Yes, boost is the same then.

Peter

Ruben Smits's picture

OCL's manifest.xml dependencies

On Friday 03 December 2010 12:02:31 Peter Soetens wrote:
> On Thursday 02 December 2010 10:21:19 Ruben Smits wrote:
> > On Thursday 02 December 2010 10:13:26 Peter Soetens wrote:
> > > I believe there is an issue with getting the manifest.xml file right
> > > for ocl.
> > >
> > > autoproj requires the dependency 'readline', while rosmake depends on
> > > 'libreadline-dev'. I think there are similar 'issues' with names like
> > > 'omniorb', 'boost', etc. Where each dependency system has used other
> > > names. Should we update the .osdeps files or what should be do ?
> >
> > libreadline and omniorb are defined by our own orocos_toolchain_ros stack
> > so we could easily change them there without having to change the
> > autoproj osdeps.
>
> But how can the rtt/ocl package than work outside of the
> orocos_toolchain_ros stack, but with the 'rosmake' system for building it
> ?

You need to define them somewhere. Isn't this also the case with autoproj?

Ruben
> > Boost is a ros-core osdep and is called 'boost', I guess this is
> > the same as in autoproj no?
>
> Yes, boost is the same then.
>
> Peter