< Previous by Date Date Index Next by Date >
< Previous in Thread Thread Index  

Re: [reSIProcate] Resiprocate Footprint


That's 9 Mb for the debug build. If you go down to the "small" build, the sizes reduce as follows:

50k     libares.a
2.9M    libdum.a
4.3M    libresip.a
1.1M    librutil.a

... or about 8.2 Mb total. Approximately 680 kb of this is the *Contents classes.

/a

Jerry Richards wrote:
Would that be a bit over 9MBytes for the "small" profile type build?  Do you
know the approximate size of these components for the "debug" profile type?
During testing of our application, I think we would like debug information
available.

Jerry


-----Original Message-----
From: Adam Roach [mailto:adam@xxxxxxxxxxx]
Sent: Monday, January 22, 2007 8:26 AM
To: Adam Roach
Cc: Jerry Richards; resiprocate-devel@xxxxxxxxxxxxxxxxxxxx
Subject: Re: [reSIProcate] Resiprocate Footprint


Robert pointed out to me that, for many applications, the *Contents
classes aren't strictly necessary. Removing them reduces the size of the
libresip library by about 900 kb.

/a

Adam Roach wrote:
Jerry Richards wrote:

I am looking at using resiprocate for an embedded MIPS VoIP phone.

Does anyone know roughly what is the resiprocate footprint (excluding
repro), using the following build command (and I'm excluding SSL and
CommandLineParser)?

        ./configure
        make dum

I think the above pulls in the /rutil, /ares/, resip/stack, and resip/dum
libraries.


I think you'll find that the stripped size of those four libraries comes
to about 10 megs, broken down roughly as follows:

    libares: 48 kb
    librutil: 3.5 Mb
    libresip: 5.4 Mb
    libdum: 1.3 Mb


/a
_______________________________________________
resiprocate-devel mailing list
resiprocate-devel@xxxxxxxxxxxxxxxxxxxx
https://list.resiprocate.org/mailman/listinfo/resiprocate-devel