# Revision history [back]

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).

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