Micah - I haven't tested this yet, but I've been pondering on the impact of having a dependency on Hg for the actual build process of Wget. Seems like an awful lot of trouble for a product that in the past has only needed Make|Nmake and a C compiler.
Is it possible with Hg to create a file that consists of the TIP Output? We could then echo this back through this section of the make file rather then using Hg to create it. What I'm concerned with is someone who downloads the source from a zip/tarball. Requiring them to have Make|Nmake and a C compiler is reasonable. Requiring a source control tool (Hg, svn, etc) is not. Chris Christopher G. Lewis http://www.ChristopherLewis.com > -----Original Message----- > From: Micah Cowan [mailto:[EMAIL PROTECTED] > Sent: Tuesday, October 16, 2007 6:07 PM > To: wget@sunsite.dk > Cc: Gisle Vanem; Christopher G. Lewis > Subject: Re: version.c take two > > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA256 > > Micah Cowan wrote: > > Gisle and Chris, you should be able to write this rule in your > > Makefiles. Something like: > > > > version.c: $(SOURCES) > > echo 'const char *version_string = "@VERSION@"' > $@ > > -hg log -r tip --template='" ({node|short})"\n' >> $@ > > echo ';' >> $@ > > Actually, the "hg" line ought to be: > > -hg log -r . --template='" ({node|short})"\n' >> $@ > > As the user may not necessarily be building from tip. If > closing stderr > or directing it to the equivalent of /dev/null ("2>NULL"?) is > possible, > that should also be included. > > - -- > Micah J. Cowan > Programmer, musician, typesetting enthusiast, gamer... > http://micah.cowan.name/ > > -----BEGIN PGP SIGNATURE----- > Version: GnuPG v1.4.6 (GNU/Linux) > Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org > > iD8DBQFHFUQu7M8hyUobTrERCJORAJ4uOqqiuBCyjqGJMnBWIy8xlOeZ/wCggYTt > Saas407pZa3Xpb9joJcxEts= > =kX7O > -----END PGP SIGNATURE----- >
smime.p7s
Description: S/MIME cryptographic signature
