Re: Questions on 'make dist'

[NightStrike]

On Tue, Mar 11, 2008 at 5:41 PM, Ralf Wildenhues <address@hidden> wrote:
> * NightStrike wrote on Mon, Mar 10, 2008 at 03:42:52PM CET:
>
> > Our project is laid out like this:
>  >
>  > /trunk/
>  > /trunk/mingw-w64-crt/
>  > /trunk/mingw-w64-doc/
>  > /trunk/mingw-w64-headers/
>
>
> > What is the best way to handle this situation to remove the need to
>  > manually tar up the trunk?
>
>  Move the (top of the) build system up the trunk?  This can be as easy as
>
>  cat >configure.ac <<'EOF'
>  AC_INIT([package], [version], [bug-address])
>  AM_INIT_AUTOMAKE
>  AC_CONFIG_SUBDIRS([mingw-w64-crt])
>  AC_CONFIG_FILES([Makefile])
>  AC_OUTPUT
>  EOF
>  echo SUBDIRS = mingw-w64-crt > Makefile.am
>  autoreconf -vi
>
>  though you may probably want to share auxiliary files
>  (AC_CONFIG_AUX_DIR) with the sub configure.

I think I understand what you mean.  Create a recursive build tree
that allows starting from any point.  I would then perhaps put this
also in the trunk/Makefile.am:

EXTRA_DIST=mingw-w64-headers mingw-w64-doc

So that from the trunk directory, I could run 'make dist' and it would
grab everything, yes?

I had intended to do everything with non-recursive make, but as you
pointed out once, non-recursive is also considered harmful.

Am I understanding you correctly?