[ros-users] binary packages dependencies
Rene Ladan
r.c.ladan at gmail.com
Sat Aug 7 20:22:08 UTC 2010
Hi all,
I'm also planning to not include the build directories for the FreeBSD
port(s). For the core ROS system, the build directories take up 311MB
out of 466MB (67%), while the .svn directories (not part of the final
port) take up 22MB (4.7%). This means the core ROS system itself would
only take up about 133MB (source + binaries).
What is the purpose of the test directories? Are they only used to
self-test the freshly built system to see if it is production-ready?
Regards,
Rene
On 25-06-2010 00:17, Brian Gerkey wrote:
> hi Cedric,
>
> You've noticed an aspect our binary packages that's bothered us (the
> developers) since the day we started making them, which is that they
> contain extraneous build artifacts, sometimes lots of them.
>
> We plan to remove them, starting with the worst offenders, some of
> which you've identified. Ideally, we'd remove the build directory of
> every package, but some (ill-behaved) packages export directly from
> their build directory; they need to be fixed.
>
> You'll see a lot of benefit from that kind of cleanup. We could then
> explore your suggestion of making runtime and development versions of
> each package. Doing that properly will take some thought, and is
> unlikely to happen very soon.
>
> brian.
>
> On Thu, Jun 24, 2010 at 3:10 PM, Cedric Pradalier
> <cedric.pradalier at mavt.ethz.ch> wrote:
>> 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
>>
>> _______________________________________________
>> ros-users mailing list
>> ros-users at code.ros.org
>> https://code.ros.org/mailman/listinfo/ros-users
>>
> _______________________________________________
> ros-users mailing list
> ros-users at code.ros.org
> https://code.ros.org/mailman/listinfo/ros-users
>
--
http://www.rene-ladan.nl/
GPG fingerprint = E738 5471 D185 7013 0EE0 4FC8 3C1D 6F83 12E1 84F6
(subkeys.pgp.net)
More information about the ros-users
mailing list