Re: [Chicken-hackers] Made a start with CHICKEN 5 proposal

[Felix Winkelmann]

> This option looks interesting, it event seems to differentiate between
> built-in and installed modules, but AFAICT it requires import libraries
> to be already in place to output something. So, it can not be used to
> gather compilation dependencies.
> 
> What I really need is a way for a given name to tell if it's installed
> extension module (egg or built-it) or some unknown (to assume it's
> coming from currently compiling application).
> 
> With changed include-path behaviour to allow additional modules to be
> found in directories separate from EGG_DIR it would make life much
> easier for multi-module applications. Especially taking into account
> cross-compile setups.

I see. Hm, difficult. If the import-libs are missing the compile will
abort, catching this would require a special compilation
mode. However, detecting whether an import lib is installed can be
done via "extension-information".


felix