[postgis-devel] build scripts (was: RC3 build/install script bugs)

[strk at refractions.net]

I've added a 'maintainer-clean' rule to the top-level Makefile.
I've also added a 'test' rule which runs all available regress
tests. Regress output dir may be specified exporting the TMPDIR 
variable, which defaults to '/tmp'.

--strk;

On Thu, Mar 03, 2005 at 09:20:11AM -0800, Chris Hodgson wrote:
> I think that "maintainer-clean" or "maintainerclean" is the best name to 
> use for the make target that removes the files generated by yacc and flex.
> 
> Distclean means "go back to the way it is in the distribution" - since 
> we are including the yacc/flex gen'd files in the dist, this is not what 
> we want. distclean is primarily different from clean only in that clean 
> leaves the output of configure - distclean removes it.
> 
> This is based on what appears to be the info docs for make, which I 
> happened to find here:
> 
> http://theory.uwinnipeg.ca/localfiles/infofiles/make/make_118.html
> 
> `clean'
>    Delete all files from the current directory that are normally
>    created by building the program. Don't delete the files that record
>    the configuration. Also preserve files that could be made by
>    building, but normally aren't because the distribution comes with
>    them. Delete `.dvi' files here if they are not part of the
>    distribution. 
> `distclean'
>    Delete all files from the current directory that are created by
>    configuring or building the program. If you have unpacked the source
>    and built the program without creating any other files, `make
>    distclean' should leave only the files that were in the distribution. 
> `maintainer-clean'
>    Delete almost everything from the current directory that can be
>    reconstructed with this Makefile. This typically includes everything
>    deleted by |distclean|, plus more: C source files produced by Bison,
>    tags tables, Info files, and so on. The reason we say "almost
>    everything" is that running the command `make maintainer-clean'
>    should not delete `configure' even if `configure' can be remade
>    using a rule in the Makefile. More generally, `make
>    maintainer-clean' should not delete anything that needs to exist in
>    order to run `configure' and then begin to build the program. This
>    is the only exception; |maintainer-clean| should delete everything
>    else that can be rebuilt. The `maintainer-clean' target is intended
>    to be used by a maintainer of the package, not by ordinary users.
>    You may need special tools to reconstruct some of the files that
>    `make maintainer-clean' deletes. Since these files are normally
>    included in the distribution, we don't take care to make them easy
>    to reconstruct. If you find you need to unpack the full distribution
>    again, don't blame us. To help make users aware of this, the
>    commands for the special |maintainer-clean| target should start with
>    these two:
> 
> @echo 'This command is intended for maintainers to use; it'
> @echo 'deletes files that may need special tools to rebuild.'
>    
> 
> Chris
> 
> strk at refractions.net wrote:
> 
> >On Thu, Mar 03, 2005 at 12:07:51PM +0100, Markus Schaber wrote:
> > 
> >
> >>Hi, strk,
> >>
> >>strk at refractions.net schrieb:
> >>   
> >>
> >>>I've added generated files into CVS. 
> >>>These are: lex.yy.c wktparse.tab.c wktparse.tab.h
> >>>``make clean'' won't get rid of them.
> >>>Changes will be notified by cvs client (removed from .cvsignore).
> >>>     
> >>>
> >>Fine.
> >>
> >>What do you think about a "make distclean", "make maintainerclean" or
> >>"make mrproper" (there's no common name?) that helps deleting even those
> >>files?
> >>   
> >>
> >
> >make distclean seems fine to me.
> >It would drop those file, so running from a release
> >would put you in the old-times-state (need FLEX/YACC installed and
> >set correctly).
> >Note tough, that building them yourself (even on the same machine)
> >will generate a different output, so the CVS clients will report
> >modified files (this seems to be mainly due to $Header$ expansion).
> >I've had many headhackes with pgsql because of this...
> >Still worth it ?
> >
> >--strk;
> >
> >
> > 
> >
> >>>I've tested this on a pretty old freebsd and have no problem.
> >>>What about a big round-test-before-release ?
> >>>     
> >>>
> >>Compiles and installs fine here, and also passes all jdbc2 regression 
> >>tests.
> >>
> >>Markus
> >>
> >>-- 
> >>Markus Schaber | Dipl. Informatiker | Software Development GIS
> >>
> >>Fight against software patents in EU! http://ffii.org/
> >>                                     http://nosoftwarepatents.org/
> >>_______________________________________________
> >>postgis-devel mailing list
> >>postgis-devel at postgis.refractions.net
> >>http://postgis.refractions.net/mailman/listinfo/postgis-devel
> >>   
> >>
> >_______________________________________________
> >postgis-devel mailing list
> >postgis-devel at postgis.refractions.net
> >http://postgis.refractions.net/mailman/listinfo/postgis-devel
> > 
> >
> 
> _______________________________________________
> postgis-devel mailing list
> postgis-devel at postgis.refractions.net
> http://postgis.refractions.net/mailman/listinfo/postgis-devel