Jack O'Quin
Jack O'Quin
That sounds like something I'd like to try. Thanks for the pointer.
The fact that catkin_tools adds each package to your path individually is expected. It is because catkin_tools builds each package individually. But, your path looks quite bizarre. Did you create...
When roslint was originally created, catkin_make was what we had to use. It is not clear to me what should be done differently with catkin_tools. If you can figure out...
Jon: I seem to remember that for every CMake build, `roslint` depends on all the individual package `roslint_PKGNAME` targets. That should be true for each single `catkin build` package as...
If my earlier comment was unclear: I believe the `roslint` target _does_ work like `run_tests`. As long as at least one package uses roslint, the general target exists and depends...
Works for me. I just tried it. What happens when you go to the relevant build directory and type: `make roslint`?
I did something like this: ``` cd ~/catkin_ws catkin build cd build/your_package make roslint ```
> However, there is no generic target to run all roslints (which is impossible with catkin_make as well btw), as there is for running tests: > > > catkin build...
Maybe: `--make-if-target`?
I just started experimenting with this fine tool. Even after reading the doc fairly carefully, I am still unclear about what setup.bash to source.