Author martin.panter
Recipients berker.peksag, brett.cannon, ezio.melotti, josh.r, martin.panter, ned.deily, python-dev, vlee, willingc
Date 2016-09-13.11:29:23
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1473766164.66.0.776854675302.issue23404@psf.upfronthosting.co.za>
In-reply-to
Content
Okay so my “make -t” trick has various flaws. You still have to know the filenames to specify, it requires Makefile to be generated by configure in the source tree, and it creates empty files if you use it in a separate build directory.

Another idea: instead of the “make touch” recipe, we add a simple shell script. Call it say “touch-bootstrap.sh”. Like what “make touch” already does in Python 2, but without embedding it as a makefile rule.

Or add a flag variable so you can do a build without running any of the regeneration rules or worrying about timestamps: make BOOT="#".
History
Date User Action Args
2016-09-13 11:29:24martin.pantersetrecipients: + martin.panter, brett.cannon, ned.deily, ezio.melotti, python-dev, berker.peksag, willingc, josh.r, vlee
2016-09-13 11:29:24martin.pantersetmessageid: <1473766164.66.0.776854675302.issue23404@psf.upfronthosting.co.za>
2016-09-13 11:29:24martin.panterlinkissue23404 messages
2016-09-13 11:29:23martin.pantercreate