Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

How to disable --only-pkg-with-deps?

See original GitHub issue

I used --only-pkg-with-deps to rebuild a single package in a Catkin workspace. After doing so, future invocations of catkin_make (with no options) do not force a configure. As a result, they build the subset of packages that were selected by the flag.

The only solution I’ve found to work is to delete the entire build directory. Surprisingly, the --force-cmake flag also doesn’t force a reconfigure (this seems like a bug?).

This definitely happens in version 0.6.11 on Ubuntu 12.04 and 14.04.

Issue Analytics

State:
Created 9 years ago
Comments:7 (7 by maintainers)

Top GitHub Comments

1reaction

wjwwoodcommented, Jan 12, 2015

Also, w.r.t the documentation for catkin_make --build-pkg-with-deps I agree that the docs should be updated, I don’t support there is a chance we could solicit a pull request from you? 😄

It seems adding -DCATKIN_WHITELIST_PACKAGES="" to the next catkin_make call will clear the condition and include all packages again, though I haven’t considered all of the ramifications of this approach.

1reaction

dirk-thomascommented, Jan 12, 2015

--only-pkg-with-deps equates to set the CMake variable CATKIN_WHITELIST_PACKAGES. Once that is set it will be in the CMakeCache.txt file until being redefined.

Passing --force-make does invoke the CMake configuration step again. But it will keep using the variable from the cache.

The script has no knowledge if the user had passed -CATKIN_WHITELIST_PACKAGES=... before (and it should keep using it) or if the user passed --only-pkg-with-deps before and now intends it to be “reset”. Therefore I don’t see a good approach to change the current behavior.