[DGD]Core library and initd.c

[Erwin Harte]

On Fri, Apr 20, 2001 at 11:24:54AM -0500, Jason Cone wrote:
> > -----Original Message-----
> > From: Erwin Harte [mailto:harte at xs4all.nl]
> > Sent: Friday, April 20, 2001 11:21 AM
> > To: dgd at list.imaginary.com
> > Subject: Re: [DGD]Core library and initd.c
> > 
> > That gives you a bit of a catch-22 situation.  The ~System/initd.c is
> > the first non-kernel object to be loaded, and its task is to load
> > whatever else is necessary for your particular game/mud/lib.
> > 
> > The only way around using a hardcoded path would be by making it a
> > define that the kernel-lib finds in /include/config.h or so, but that
> > is up to Dworkin.
> 
> 
> Doh!  I failed to add 2 + 2 correctly.  In this case, perhaps it does make
> sense for there to be a /kernel/include/System.h-like include file that can,
> if present, inform the driver (/kernel/sys/driver.c) of the locations of all
> secondary library-specific files (though, at present, the initd.c file is
> the only that comes to mind).

Technical problem there is that you can't 'conditionally include'
depending on whether the file exists or not, certainly not when
compiling the driver or auto object, which cannot make use of the
possibly more sophisticated path_include() functionality of the driver
object.

Aside from which, the kernel-lib has been designed to be able to
function even when no /usr/System/ is present at all.

Erwin.
-- 
Erwin Harte      : `Don't mind Erwin, he gets crabby. :)'
harte at xs4all.nl  :    -- Par Winzell <zell at skotos.net>

List config page:  http://list.imaginary.com/mailman/listinfo/dgd