Mike Purvis

Interesting, thanks for the info on that! AFAICT from a quick read, for `CMAKE_STAGING_PREFIX` to work correctly, it will need to be explicitly supported by every CMake find module— otherwise...

Unless I'm misunderstanding something, the fast entry points script will only improve things for the initial bootstrap from script into module— we _also_ use pkg_resources here for handling plugins, so...

Previously: #439, #440, #429 Fix is already merged as of e30c226276c657687942e9ec48e6596175aafaa5; but it isn't in the latest release (0.4.4). In the meantime, consider running catkin_tools from source.

The logic is _supposed_ to be that `catkin build foo` yields a resultspace where all of foo's dependencies that are available in the source space get built, with only `build_depend`...

Yes, that's the idea exactly. Upon further consideration, yes it makes perfect sense that it would be possible to precompute; that's much better than trying to do it live.

I think the best place to fix this would be in catkin_pkg itself: https://github.com/ros-infrastructure/catkin_pkg/blob/6d79544f7fa4b646f7574910d085806de393bb46/src/catkin_pkg/topological_order.py#L117

I'm becoming very interested in this feature. We'd like to be able to ship our developers a profile in `/etc` somewhere with flags that match our CI build. So I...

Strongly in support of this. Any chance it can target 0.4.3?

I would have expected an issue like this with Python 3, but interesting that you're also getting it with Python 2.

My usage is typically more like "one package each for these five repos", so I just manually set `--whitelist`. Maybe `--whitelist-from-paths` or something? Maybe you could hack it by chaining...