Revision history [back]

All of winros, catkin_make and catkin_make_isolated are just simple wrappers around callouts to cmake to build the projects. The first two, winros, catkin_make make a single cmake project of your entire source workspace. The latter, makes a cmake project for every catkin package in your source workspace.

There is a REP explaining catkin_make_isolated in detail: http://www.ros.org/reps/rep-0134.html

You can also check the scripting for catkin_make_isolated (it's not too hard) in this function: https://github.com/ros/catkin/blob/indigo-devel/python/catkin/builder.py#L636.

The next question is, why use catkin_make_isolated? The main reason is to be able to build conventional cmake projects alongside catkin packages. What conventional cmake projects is rosmatlab trying to build? Perhaps they can be built and installed separately prior to a regular winros/catkin_make?

All of winros, catkin_make and catkin_make_isolated are just simple wrappers around callouts to cmake to build the projects. The first two, winros, catkin_make make a single cmake project of your entire source workspace. The latter, makes a cmake project for every catkin package in your source workspace.

There is a REP explaining catkin_make_isolated in detail: http://www.ros.org/reps/rep-0134.html

You can also check the scripting for catkin_make_isolated (it's not too hard) in this function: https://github.com/ros/catkin/blob/indigo-devel/python/catkin/builder.py#L636.

The next question is, why use catkin_make_isolated? The main reason is to be able to build conventional cmake projects alongside catkin packages. What conventional cmake projects is rosmatlab trying to build? Perhaps they can be built and installed separately prior to a regular winros/catkin_make?