[Gpg4win-devel] build problems with installer

[Marcus Brinkmann]

At Wed, 12 Dec 2007 09:07:16 +0100,
Jan-Oliver Wagner wrote:
> 
> Hello Marcus,
> 
> $ make distclean
> (instead of just "clean")
> 
> healed a lot of my problems.
> I will try further on this basis.
> 
> I am aware there are various options and methods
> to handle the build process.
> Still I am on the search for a most-times-successful
> method that combines simplicity with re-use of
> already compiled stuff.

If you do a make clean or make distclean and rerun configure, you do
not reuse anything.  Might just as well start from a clean checkout.
(And if you don't do make clean, you get a versioninfo.txt file with
duplicated entries).

When I am preparing a release (of any package, for that matter), I
always start with a local copy of a clean SVN checkout.  I do "svn
update" and "svn status" to check that I have no local modifications,
and then I do a "cp -a PACKAGE PACKAGE-p" and work from the PACKAGE-p
directory.  

For gpg4win, I also re-download everything once in a while to check
that the links are still working and the checksums are correct.

I would never, ever use an already compiled tree for preparation of a
release.  Making sure that everything still builds from scratch is
part of the release process.

During development, I make heavy use of the techniques I documented
(make clean-PACKAGE, etc), and have yet to encounter similar problems
to the ones you described.  I have updated individual packages in one
of my gpg4win working copy over maybe a hundred revisions without
rebuilding from scratch, and without glitches.

Thanks,
Marcus