[DGD]Core library and initd.c
Jason Cone
jcone at uscdev.com
Fri Apr 20 18:54:20 CEST 2001
> -----Original Message-----
> From: Erwin Harte [mailto:harte at xs4all.nl]
> Sent: Friday, April 20, 2001 11:33 AM
> To: dgd at list.imaginary.com
> Subject: Re: [DGD]Core library and initd.c
>
> 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.
Again, I mis-typed. Counter to what I first implied, I made the assumption
that the include file would, indeed, exist. It would be the optional
presence of the macro definition that would point the driver in the right
direction.
> Aside from which, the kernel-lib has been designed to be able to
> function even when no /usr/System/ is present at all.
True. I don't wish to change this. Thus, instead of doing a run-time check
on the existence of /usr/System/initd.c, a compile-time check would instead
be done a la "#ifdef _SYSTEM_INITD_LOC_" or some such definition. It would
have the same effect, but the location could be configured to be whatever.
Again, though, this assumes the unconditional presence of a configurable
include file in the core library include path.
JC
List config page: http://list.imaginary.com/mailman/listinfo/dgd
More information about the DGD
mailing list