On 23 Aug 2001, Thayne Harbaugh wrote:
> There's another way to look at things:
Yes. We are dealing with two things in this discussion.
1) What Debian wants, and
2) This, which you describe perfectly:
> GGI is made to be able to dynamicly load the pieces it needs: memory
> layouts, color depths, input devices, display targets, etc. Most
> embeded applications know ahead of time what all of these are.
>
> Why can't libggi be built staticly with exactly the driver it needs?
>
> Why should an embeded system have all the code for parsing config files
> and trying to decide if it needs to display to X or framebuffer?
>
> If everything is known for the host system then all of the dynamic
> configuration code (most being in libgg?) could be excluded. No files
> in /etc/ggi should need parsing.
And the way to make this happen is to go in there and create us a special
tweaky alternative implementation of the stuff in the dl.c source files
that simply uses a table of strings/symbols to switch between
statically linked in drivers, rather than dlopening them.
However, for Debian this is not what we are talking about, since Debian
is very far from being a fixed-configuration embedded system :-). And,
I think it is important for us to concentrate on what Debian wants since
Martin will be needing to take the baton from us on Sunday if he is to
get any work done this next week.
--
Brian
