build prefix command is naive about ament_tools HOT 7 CLOSED

build_dependencies in this context (

Therefore I don't think anything needs to be changed here?

from ament_tools.

Based on the output of #62 it looks like that the order is correct. The problem is that the environment files include not only the recursive dependencies but also downstream packages - basically all packages of the workspace.

from ament_tools.

@dirk-thomas But they should be skipped because they don't have environment hooks inside the workspace? or is it a problem when you install two workspaces to the same install space?

from ament_tools.

Sorry, I meant downstream packages. E.g. ament_cppcheck doesn't have any dependencies but currently uses the environment of all packages in the workspace (which is only the case when rebuilding a workspace again).

from ament_tools.

Oh, it's not just the dependencies, but also anything that comes before in the topological order.

from ament_tools.

It includes even packages which come afterwards in the topological order.

from ament_tools.

For packages with dependencies on other ament packages the list and order is correct. But for packages without dependencies on other ament packages the list contains all packages from the workspace. The fix is simple: #63.

from ament_tools.