[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-devel
Subject:    Re: Memory consumption in KDE 2.0
From:       Stephan Kulow <coolo () itm ! mu-luebeck ! de>
Date:       1999-05-04 8:00:34
[Download RAW message or body]

Steffen Hansen wrote:
> 
> On Sun, 2 May 1999 pbrown@redhat.com wrote:
> 
> > > Better now than later. It'll be nearly impossible to switch to a
> > > "better" (smaller, faster) ORB when the applications have been
> > > stabilized and enhanced.
> >
> > We might (shudder) be able to talk to the GNOME guys about this.  In fact,
> > I think it is the right thing to do.  They switched from MICO to Orbit in
> > a few months time.
> >
> > However, we do have to write C++ wrappers for it, but that isn't too
> > difficult.  AFAIK, no one is currently working on this.
> 
> If you want to reduce the size of the corba-based code (esp. libraries),
> you should do like MICO's --enable-final option (which doesn't work
> currently, but that doesn't matter).
> 
> I tried it with just the few files in libkded so far: I made a file
> all_kded.cc with the lines:
> 
> #include "kded.cc"
> #include "kded_impl.cc"
> #include "more corba-related code"
> ...
> 
> and so forth. The primary point is to get all files that somehow include
> CORBA.h or idl-generated headers compiled at once. Even with libkded,
> which is still very small i got a 50% reduction in library size. The code
> will probably be optimized better too, and if you have enough RAM,
> compilation is much faster also.
> 
_if_ you have enough RAM. I once messured that the compilation of
orb_all
(or something like that) in MICO takes up to 106MB RAM. 

Greetings, Stephan

-- 
As long as Linux remains a religion of freeware fanatics,
Microsoft have nothing to worry about.  
                       By Michael Surkan, PC Week Online

[prev in list] [next in list] [prev in thread] [next in thread]