[omniORB] Library and Applications size

Hany Greiss Hany.Greiss@InBusiness.com
Wed Jun 12 20:00:02 2002


Hello,

    On a RedHat 7.2 system with gcc 2.96, stripping the library generated a
number of link errors in my case. I had no 
problems if I did not strip the library. 

Hany

-----Original Message-----
From: Duncan Grisby [mailto:duncan@grisby.org]
Sent: Wednesday, June 12, 2002 1:50 PM
To: jorgefm@cirsa.com
Cc: omniorb-list@realvnc.com
Subject: Re: [omniORB] Library and Applications size 


On Wednesday 12 June, jorgefm@cirsa.com wrote:

> I'm using a Intel Linux Machine in development, redhat 7.2 with kernel
> 2.4.19-pre8.
> How can i strip the library ? I only made:
> 
> ./configure --with-openssl=/lib --disable-thread-tracing
> 
> By default the sources are compiled without '-g', the what it means:
> "the omniORB library with debugging info and thread tracing is
> 6057915 bytes.  Without debugging info (but still with thread
> tracing), it's 2050652 bytes" ??

The orb core is currently built with debugging, due to line 144 of
src/lib/omniORB/orbcore/dir.mk that says

  CXXDEBUGFLAGS = -g

Comment it out, do a make veryclean; make; make install for that
directory, and the library will get down to around 2MB. The -g will be
removed for the release, of course. To strip the library, do

  strip libomniORB4.so.0.0

in the installation lib directory. I think stripping it will prevent
programs that try to dlopen it from finding any symbols, but it works
fine for programs explicitly linked against it at link time.

Cheers,

Duncan.

-- 
 -- Duncan Grisby         --
  -- duncan@grisby.org     --
   -- http://www.grisby.org --
_______________________________________________
omniORB-list mailing list
omniORB-list@realvnc.com
http://www.realvnc.com/mailman/listinfo/omniorb-list