14 May 2004 19:45
Re: invoking external build processes
Matt Armstrong <matt <at> lickey.com>
2004-05-14 17:45:56 GMT
2004-05-14 17:45:56 GMT
You MD5-sum the jam variables that affect the build (#defines and other compiler flags). Alan Baljeu <alanb <at> cornerstonemold.com> writes: > I'm missing something here. How do you get Jam to read the contents of > the file you want to MD5? > > ----- Original Message ----- > From: "Matt Armstrong" <matt <at> lickey.com> > To: <jamming <at> perforce.com> > Sent: Friday, October 03, 2003 11:35 AM > Subject: Re: [jamming] invoking external build processes > > > > If the information to be updated is expressed completely within the > > jamfiles, then a built in MD5 rule might get you going. > > > > We have a header file that contains all the configuration #defines in > > our project. It is currently built "ALWAYS" by a perl script, but that > > causes a full build. > > > > So I added an MD5 builtin rule to Jam. Jam computes the MD5 sum of all > > the #defines and creates blddefs-<md5sum>.h. Then we have rules to copy > > that file to blddefs.h. > > > > That way, it'll only regenerate blddefs.h when the list of configuration > > values changes. > > > > See //guest/matt_armstrong/jam/patched_version/... in the public > > perforce demon.(Continue reading)
RSS Feed