Index:
[thread]
[date]
[subject]
[author]
From: Jon M. Taylor <taylorj@ecs.csus.edu>
To : ggi-develop@eskimo.com
Date: Sat, 29 Aug 1998 14:30:24 -0700 (PDT)
Re: LibGGI2D, LibGGI3D and targets
On Sat, 29 Aug 1998, MenTaLguY wrote:
>
> On Sat, 29 Aug 1998, MenTaLguY wrote:
>
> > Ah... now I see. yes, it would probably be appropriate to keep the libGGI
> > _STUBS_ (they are not the same as "targets", last I checked) with the
> > appropriate extension library. There certainly should be separate
> > "foo-vendor-hw-(extension)" stubs for each extension. I dunno if they
> > should be packaged with the extension library or with the KGI driver for
> > sure or not. I guess it depends on the driver (i.e. would it come with the
> > LibGGI distro, or is it third-party?), and the extension library (does it
> > actually relate to specific hw or not?)
> >
> > Get your terminology straight. Otherwise people will argue with you
> > needlessly.
>
> I should take my own advice here. :/
I sympathize |->. Pert of the problem is that these categories of
dynamic libraries are somewhat arbitrary. They all do the same thing -
overload symbol table entires for library functions.
> hw-specific stubs are called DRIVER (this is on the LibGGI side of things,
> not the KGI side) libraries, not STUB libraries. stupid me.
>
> But they still aren't TARGET libraries.
Right.
Jon
---
'Cloning and the reprogramming of DNA is the first serious step in
becoming one with God.'
- Scientist G. Richard Seed
Index:
[thread]
[date]
[subject]
[author]