Yea, i think thats the way to go.
Important ddetect modules
ethdetect
mdmdetect
diskdetect
cddetect
cpudetect and memdetect can be done in a few lines of code seperately,
so they probably dont warrant doing via libdetect.
Also if we do a seperate libisapnp it may be smaller that i stated below
because we should be able to do library reducation on it.
Glenn
David Whedon wrote:
>
> I think the way to do this is to make a udeb out of libisapnp, right? I made one
> yesterday, though I don't know if it works yet.
>
> (just responding to old e-mail that was hidden up high in my box)
>
> -David
>
> Thu, Dec 14, 2000 at 04:48:58PM +1100 wrote:
> > Linked against static libisapnp.a
> >
> > 20k cddetect
> > 20k cpudetect
> > 20k diskdetect
> > 20k ethdetect
> > 28k mdmdetect
> > 20k memdetect
> > 128k total
> >
> > Linked agianst a libisapnp.so i hacked together.
> > 8.0k cddetect
> > 4.0k cpudetect
> > 4.0k diskdetect
> > 8.0k ethdetect
> > 12k mdmdetect
> > 4.0k memdetect
> > 32k libisapnp.so.1.23.03
> > 72k total
> >
> > Depending on how many ddetect components we will want to use will
> > determine wether tis a good idea to use a shared libispnp.
> >
> > If we just more than two detect components then it will save space to
> > use shared libs.
> >
> >
> > Glenn
> >
> >
> > --
> > To UNSUBSCRIBE, email to [EMAIL PROTECTED]
> > with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
