Footprint measurements of Ice?

Has anyone done any footprint measurements for Ice?
This is of interest for people wanting to use middleware in
embedded systems.

For a simple test, if I do:
size libICE.so.1.0.0

I get:
text data bss dec hex filename
1552720 290126 588 1843434 1c20ea libIce.so.1.0.0

Comments

  • marcmarc FloridaAdministrators, ZeroC Staff Marc LaukienOrganization: ZeroC, Inc.Project: The Internet Communications Engine ZeroC Staff
    We don't have any footprint measurements.

    I think for embedded use it would make sense to strip all features from the Ice core library that are not needed for the embedded application. The total size then really depends on which features of Ice you use.
  • rodrigcrodrigc Member
    Originally posted by marc
    We don't have any footprint measurements.

    I think for embedded use it would make sense to strip all features from the Ice core library that are not needed for the embedded application. The total size then really depends on which features of Ice you use.


    Seems like a reasonable approach. Is Ice subsettable, either through some
    fancy Makefile scheme or something else?

    For example, in the CORBA world, people have reduced ORB footprints by optionally
    throwing out DII/DSI.

    Or, do you have any guidelines or insight for how to write a small
    footprint client/server with Ice?

    Thanks.
  • mesmes CaliforniaAdministrators, ZeroC Staff Mark SpruiellOrganization: ZeroC, Inc.Project: Ice Developer ZeroC Staff
    Originally posted by rodrigc
    Seems like a reasonable approach. Is Ice subsettable, either through some fancy Makefile scheme or something else?
    Sorry, the late response means we don't have a good answer for you. ;)

    At present, there is no easy way to minimize the Ice feature set; you would have to do this manually.

    - Mark
Sign In or Register to comment.