Development plan -- time to move forward

Daniel Stone daniel at fooishbar.org
Fri Apr 22 17:40:54 PDT 2005


On Fri, Apr 22, 2005 at 08:34:39PM -0400, Kevin E Martin wrote:
> 3. Should we use AM_CONFIG_HEADER() in the initial release or wait until
>    afterwards?
> 
>    Proposed answer: If the AM_CONFIG_HEADER([config.h]) macro is used,
>    then we will be required to add "#include <config.h>" to the source
>    files.  Since we are sharing the source code between the modular and
>    monolithic trees for the 6.9/7.0 release, then those changes will
>    also appear in the monolithic release, where they do no harm, but are
>    not needed.  However, if we do not use this macro, then the changes
>    to the shared source code will be significantly reduced.  Therefore,
>    we should not use the AM_CONFIG_HEADER() macro in the initial
>    release.  Note that once the initial modular release has shipped, we
>    can easily add the macro and associated source changes to only the
>    modular tree.

I would personally be far more comfortable with AM_CONFIG_HEADER(), but
I can see the concerns.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: Digital signature
Url : http://lists.x.org/archives/xorg-modular/attachments/20050423/ab90a6a5/attachment.pgp


More information about the xorg-modular mailing list