On 6/13/05, sridewa <[EMAIL PROTECTED]> wrote:
I could be wrong, but as I understood the input drivers and similar components are always loaded in with dlopen, so you could always build a static system, but you need to build the various components as object files to be linked in per demand. You don't need to build all those, there are flags in the configure script to disable unused components, such as various touch screen drivers.
If you enable multi-process support, i.e. multiple processes coexist in the same environment, you need to build fusion, and that's a kernel module plus code that I'm not personally sure you could just build as a static library, as multiple processes will link into this space and the shared memory area. Maybe it's doable, but for most cases shared libraries is really the way to go with DirectFB.
--Kent
Hi,
On 6/3/05, Jackey <[EMAIL PROTECTED]> wrote:
> Can somebody help me if DirectFB does support static link?
I could be wrong, but as I understood the input drivers and similar components are always loaded in with dlopen, so you could always build a static system, but you need to build the various components as object files to be linked in per demand. You don't need to build all those, there are flags in the configure script to disable unused components, such as various touch screen drivers.
If you enable multi-process support, i.e. multiple processes coexist in the same environment, you need to build fusion, and that's a kernel module plus code that I'm not personally sure you could just build as a static library, as multiple processes will link into this space and the shared memory area. Maybe it's doable, but for most cases shared libraries is really the way to go with DirectFB.
--Kent
--
Something, Anything!
_______________________________________________ directfb-dev mailing list [email protected] http://mail.directfb.org/cgi-bin/mailman/listinfo/directfb-dev
