https://github.com/python/cpython/commit/77b4ed2a37f460af435df07fe25a888d8d61710e
commit: 77b4ed2a37f460af435df07fe25a888d8d61710e
branch: 3.14
author: Miss Islington (bot) <[email protected]>
committer: encukou <[email protected]>
date: 2025-10-07T20:35:38+02:00
summary:

[3.14] gh-138489: Add missing `build-details.json` step for building wasm 
(GH-139302) (GH-139557)

(cherry picked from commit db53ca30d761abba525bc8e47b16920b1fc43a83)

Signed-off-by: Ho Kim <[email protected]>
Co-authored-by: Ho Kim <[email protected]>
Co-authored-by: Adam Turner <[email protected]>

files:
A Misc/NEWS.d/next/Build/2025-09-24-13-59-26.gh-issue-138489.1AcuZM.rst
M Makefile.pre.in

diff --git a/Makefile.pre.in b/Makefile.pre.in
index ca536d32a61167..34a270ab31167a 100644
--- a/Makefile.pre.in
+++ b/Makefile.pre.in
@@ -801,7 +801,7 @@ build_all:  check-clean-src check-app-store-compliance 
$(BUILDPYTHON) platform sh
 
 .PHONY: build_wasm
 build_wasm: check-clean-src $(BUILDPYTHON) platform sharedmods \
-               python-config checksharedmods
+               python-config checksharedmods build-details.json
 
 .PHONY: build_emscripten
 build_emscripten: build_wasm web_example web_example_pyrepl_jspi
diff --git 
a/Misc/NEWS.d/next/Build/2025-09-24-13-59-26.gh-issue-138489.1AcuZM.rst 
b/Misc/NEWS.d/next/Build/2025-09-24-13-59-26.gh-issue-138489.1AcuZM.rst
new file mode 100644
index 00000000000000..b11098a3f87953
--- /dev/null
+++ b/Misc/NEWS.d/next/Build/2025-09-24-13-59-26.gh-issue-138489.1AcuZM.rst
@@ -0,0 +1,6 @@
+When cross-compiling for WASI by ``build_wasm`` or ``build_emscripten``, the
+``build-details.json`` step is now included in the build process, just like
+with native builds.
+
+This fixes the ``libinstall`` task which requires the ``build-details.json``
+file during the process.

_______________________________________________
Python-checkins mailing list -- [email protected]
To unsubscribe send an email to [email protected]
https://mail.python.org/mailman3//lists/python-checkins.python.org
Member address: [email protected]

Reply via email to