On 6/14/07, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote: > when i build a c++ compiler in the native toolchain(using buildroot)...the > size(~80MB) is 4 times as large as when i just build a c compiler...i > noticed that this is mainly because of two precompiled header files > o0g.gch and 02g.gch in /usr/include....compile time is not an issue with > me....so how can i get a smaller system?
make it a squashfs or cloop device and mount it inside your environment. I do not know if uclibc++ would help here otherwise (http://cxx.uclibc.org/) > > i need a c++ compiler because the graphic libraries i have come across are > based on c++....is thr any small footprint graphic library which works > with uclibc...or any other way to build a small gui for a uclibc based > system.....something like linux framebuffer+directfb+fbui....also where > can i get info abt compatibility issues regarding tinyx...as in,will it > work with matchbox, qt/embedded etc? if you include framebuffer drivers, you can go for kdrive which exists in x11 and xorg. 'fbdev' as driver for native xorg will work too. Not much compatibility issues with tinyx/kdrive, mostly mouse issues (it takes time to detect the right protocol: you've no config file with kdrive). as for graphical libraries with small footprint, or window managers: gtk-1.2.10, fvwm2. My personal preferences, your mileage may vary. -- Christian -- http://detaolb.sourceforge.net/, a linux distribution for Qemu _______________________________________________ uClibc mailing list [email protected] http://busybox.net/cgi-bin/mailman/listinfo/uclibc
