how to get to know dependence package once for all

asked 2019-05-11 23:34:35 -0600

macleonsh
26 ●10 ●12 ●15

Hi all, Not sure if you meet such situation, that when I down load a package (even s simple toturail package), usually is not native developed for this HW platform.. then when build it usually will report fail by message that short of some other package--then I search it and git clone it from wiki then build--another depedence error jump out... and after 5 round I feel quite boring and anoying. Do you know some good way that we can get the dependence package once for all?

And more important, many "dependence package" looks not relevant to my original package at all-- I guess it is just becuase something like "I want package A--> package A need install package B and C" and package C contains package D, E, F..

This could be a infinity game?? any suggestion from your guys?

BR LM

answered 2019-05-12 01:52:39 -0600

gvdhoorn
86574 ●283 ●1432 ●1054 http://cor.tudelft.nl/

updated 2019-05-12 01:53:49 -0600

Please see #q252478 for an example workflow when building packages from source.

In general though: try not to build packages in your workspace. Always first try to see whether a package has been released and could be installed using apt. The buildfarm has already done all the dependency resolution for you, keeps you automatically up-to-date and (especially with large packages) it's much more efficient to build something once and re-use the binaries than to have each user compile everything themselves again.

when I down load a package (even s simple toturail package), usually is not native developed for this HW platform.. then when build it usually will report fail by message that short of some other package--then I search it and git clone it from wiki then build--another depedence error jump out... and after 5 round I feel quite boring and anoying.

Not building from source also allows you to avoid this "boring and annoying" part.

edit flag offensive delete link

Comments

@gvdhoorn Thanks so much for your advice. You re correct, but for ROS community, many application are "half-making" and need source-code level modification...

macleonsh ( 2019-05-12 22:45:33 -0600 )edit

Then the author(s) should provide a .rosinstall file that contains all the repositories required to build the package. wstool can then be used to seed a workspace.

gvdhoorn ( 2019-05-13 01:11:11 -0600 )edit

add a comment

how to get to know dependence package once for all

1 Answer

Comments

Question Tools

Stats

Related questions

how to get to know dependence package once for all edit

1 Answer

Comments

Question Tools

Stats

Related questions

how to get to know dependence package once for all