This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author martin.panter
Recipients Alex.Willmer, martin.panter, thomas.perl
Date 2016-07-29.05:54:54
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1469771695.51.0.72831568208.issue27641@psf.upfronthosting.co.za>
In-reply-to
Content
Here is another possible option. It is still a bit of a hack, because the configure script inserts comments into the makefile, but this is already done e.g. with @EXPORT_MACOSX_DEPLOYMENT_TARGET@. The advantage is we get to keep the filenames of the dependencies in the makefile, so it should be easier to read and maintain. And we get to eliminate the $(cross_compiling) check as well.

In native compiling mode, everything should be as normal. When cross-compiling, the rules for regenerating files should read like

Python/importlib.h: # $(srcdir)/Lib/importlib/_bootstrap.py Programs/_freeze_importlib
	./Programs/_freeze_importlib \
	    $(srcdir)/Lib/importlib/_bootstrap.py Python/importlib.h

Since the Python/importlib.h should already exist, the rule in this form (dependencies commented out) won’t be run, and Make won’t need to build Programs/_freeze_importlib either.
History
Date User Action Args
2016-07-29 05:54:55martin.pantersetrecipients: + martin.panter, Alex.Willmer, thomas.perl
2016-07-29 05:54:55martin.pantersetmessageid: <1469771695.51.0.72831568208.issue27641@psf.upfronthosting.co.za>
2016-07-29 05:54:55martin.panterlinkissue27641 messages
2016-07-29 05:54:55martin.pantercreate