Modularization mailing list and initial strawman proposal

[Donnie Berkholz]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Kevin E Martin wrote:
> On Fri, Mar 18, 2005 at 09:39:32PM +0100, Roland Mainz wrote:
>>>   Autodetection can add dependencies that you didn't intend. For
>>>   example, a developer may have a library on their build system that
>>>   isn't available on the target system.
>>>     * Dependencies will be explicitly listed and documented. Configure
>>>       options will be used to control which dependencies are enabled or
>>>       disabled.
>>
>>How many "configure" options will that be ? 50... 100... 200 ? It may be
>>better to look into a way of a config file a lá xc/config/cf/host.def to
>>avoid having giant command lines which call "configure" (mozilla has a
>>non-standard solution which may be adoptable in this case).
> 
> 
> There are currently hundreds of options in the xc/config/cf/* files.
> Some options will no longer be needed as they will be automatically
> handled by the autotools.  Others can be handled via configure options.
> Just like the cf options are given reasonable defaults, the configure
> options will also have reasonable defaults.
> 
> As you say above, these could also be handled in other ways to automate
> the build process.  We should investigate those and other solutions
> during the initial development cycle.

Perhaps it's possible to pass a file full of options to configure.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.0 (GNU/Linux)

iD8DBQFCO5bYXVaO67S1rtsRAqbKAKDJkKhn/Bsjij+Td3q64vlQLgBbIgCg6y/H
zBRIxjgW8o83oKnyxeTTNnw=
=q7GB
-----END PGP SIGNATURE-----