Hi Tinne,
The best way to approach this is probably to create a package that
checks if the rosdep is available and otherwise downloads and installs
the package.
While having an 'OR' dependency would be nice, it's hard to preserve
because *every* package that uses the library has to use the 'OR'
dependency. If one package uses the <depend> version, and another uses
the <rosdep>, then you end up getting the same library twice.
- Ken
On Thu, Oct 14, 2010 at 2:14 AM, Tinne De Laet
<
tinne.delaet@mech.kuleuven.be> wrote:
> Hi,
>
> Our kdl_1.0 package depends on eigen.
> Before we were just specifying a dependency on the eigen package
> provided in the geometry stack as:
>
> <depend package="eigen"/>
>
> Alternatively we can also depend on an external eigen package (e.g.
> the ubuntu package libeigen2-dev) as:
>
> <rosdep name="eigen"/>
>
> Now I want to adapt the manifest so that either the ROS package OR the
> external package are needed as a dependency.
> Does the manifest allow this kind of OR statements?
>
> Tinne
> _______________________________________________
> ros-users mailing list
> ros-users@code.ros.org
> https://code.ros.org/mailman/listinfo/ros-users
>
(text/plain)