On 06/24/2010 11:28 PM, Cedric Pradalier wrote:
> Hi,
>
> I've just installed ros from the pre-compiled packages, and I see the
> binary packages depend on a lot of -dev packages, automake, autoconf,
> etc...
> Is there a rationale behind that?
>
> I would believe that one of the advantages of pre-compiled binaries is
> that it make it easier to install ros on an embedded system, with
> limited hard-drive/flash space, all of which get lost if the ros
> packages pull close to 1GB of dependencies.
>
> How much community interest would there be behind separating the
> packages into binary and -dev packages, the binary having very limited
> dependencies?
>
> Otherwise, the install from source can be compiled and deployed within
> 200MB, incl. roscore (roscpp, rospy), opencv, and image pipeline, laser
> pipeline, laser drivers, but no tf (brings in bullet and a lot of
> friends) and no rviz.
>
> Cheers
>
>    
Just installed a couple of cturtle packages, and noticed the following:

The opencv_vision stack is 392MB installed.
In that, the opencv2/build directory is 356MB, and not required in as 
far as I know.

In ogre, the build directory is 342MB out of 444MB.
In robot_model/assimp: build is 138MB out of 158MB
In robot_model/colladadom: build is 129MB out of 151MB

In total, on the few packages I installed, my /opt/ros is 1.5GB, and I'm 
pretty sure at least 965MB out of that is just disk padding.

I know space is not an issue for most of us, but still...

-- 
Cedric - Specialising in cat herding
- http://www.asl.ethz.ch/people/cedricp
- http://www.skybotix.com