[I'm moving this thread back to mesa-dev]

On 11-Jul-99 Brian Paul wrote:
> I removed the dead lock just now.

 Thanks. Does my patch fix your problem?

>> > Another question: exactly which configure-related files are supposed to
>> > be included in the Mesa tar file?
>>  configure, acinclude.m4, aclocal.m4, configure.in, config.guess,
>>  config.sub, ltconfig, ltmain.sh, acconfig.h, install-sh,
>>  missing, mkinstalldirs, conf.h.in, stamp-h.in
>>  and all Makefile.am, Makefile.in
> Wow, that's a lot of stuff.  Oh well.

 That's nothing compared to the rest of Mesa.

>>  "make dist" automatically creates a tarball with all necessary files.
> The original Makefile had options to make separate Mesa and Mesa
> demo tar and zip files.  Does make dist just make one big tar file?

 Yes, it creates a single tar file.
 However, we could add the following automake rules:
 (the distdir target copies all files that are going to be distributed 
  to the subdirectory $(distdir)) 

dist-lib: distdir
        -rm -rf $(distdir)/demos $(distdir)/xdemos ...
        -chmod -R a+r $(distdir)
        GZIP=$(GZIP_ENV) $(TAR) chozf $(distdir)-lib.tar.gz $(distdir)
        -rm -rf $(distdir)

dist-demos: distdir
        -rm -rf $(distdir)/src $(distdir)/src-glu ...
        -chmod -R a+r $(distdir)
        GZIP=$(GZIP_ENV) $(TAR) chozf $(distdir)-demos.tar.gz $(distdir)
        -rm -rf $(distdir)

 The remaining problem is that all demo subdirs are mentioned in the SUBDIRS
 variable of the Makefiles and in AC_OUTPUT() of configure.in.
 That means automake expects that those directories actually exist.
 I don't know a work-around for this problem yet :(
 
 Another (simpler) solution would be to move all demos to a subdirectory and
 create a separate independent package for them.

 OTOH I don't think creating one big tar file is that bad.

Thomas Tanner -----------------------------------------
email: tanner@(ffii.org|gnu.org|ggi-project.org|gmx.de)
web:   http://home.pages.de/~tanner
GGI/Picasso: http://picasso.ffii.org


_______________________________________________
Mesa-dev maillist  -  [EMAIL PROTECTED]
http://lists.mesa3d.org/mailman/listinfo/mesa-dev

Reply via email to