Not that I know of. rosinstall doesn't call gcc directly, anyways. it just calls through to rosmake. Thus, you can have the same net effect by calling rosinstall with -n (no build) and then calling rosmake as you see fit.
rosinstall is moving away from any invocations of build infrastructure starting with ROS Fuerte. The old calls were a result of bootstrapping issues. The catkin-based stuff runs rosinstall with no build (-n option).
EDIT: to see the output from rosmake:
VERBOSE=1 rosmake -V
Let me clarify. I'm not really fussed about who calls gcc, but I'd like to see all gcc invocations for a ROS build logged to stdout. What's the best way to do that?
Asked: 2012-03-05 04:04:12 -0600
Seen: 363 times
Last updated: Mar 06 '12
ROS Answers is licensed under Creative Commons Attribution 3.0 Content on this site is licensed under a Creative Commons Attribution Share Alike 3.0 license.
