Re: missing build functionality?

[Bruce Korb <bruce.korb@gmail.com>]

On Tuesday 23 November 2004 01:02 pm, Valdis.Kletnieks@vt.edu wrote:
> On Tue, 23 Nov 2004 12:33:39 PST, Bruce Korb said:
> 
> > Anyway, I do not see an obvious way to construct an object archive library
> > that I wish to use for multiple drivers.  There are two problems.  This:
> > 
> > > ifeq ($(ARCH),ia64) 
> > > 	CFLAGS_KERNEL = 
> > > endif
> > 
> > because I am making the archive for a loadable driver. 
> 
> The usual solution for 2 modules that share an archive would be to create
> *three* modules driver-a, driver-b, and driver-core - and then have the
> appropriate depmod magic so a 'modprobe driver-a' does an insmode
> driver-core,
> as does a 'modprobe driver-b'.
> 
> Otherwise, you're just loading the entire library into memory twice,
> once for each driver...

If the library is actually a glue layer that smooths out the differences
between kernel API's, then that is exactly what I want to do.  There
is not a substantial amount of functionality.  In fact, it is mostly
macros.  The key word being, "mostly".  There is enough code in what
is not done in macros that it should not be compiled with every driver,
but not so much that it is worth making a separate driver library driver.  :)

So, it would still be very useful to know how to link against a "libmumble.a"
file built in another directory.  Copying all sources and libraries into
a build directory before kicking off the build is kludgey.  (Linux being the
only platform where that seems to be necessary.)

Thanks - Bruce