| FazBrowse GitHub Viewer | Trending | | Home |
| Tools: [Download Repo ZIP] [Original HTTPS Page] |
Sorry, something went wrong.
When a shared library is also built, `make install` only installs the static library into LIBPL, so point libpython.static there instead of LIBDIR. Static-only builds keep the existing LIBDIR path, which is installed in that configuration. Framework builds don't install the static library (LIBPL contains a symlink to the framework's shared library instead), so don't list it. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
There was a problem hiding this comment.
Just some minor stylistic things.
Also note I'm no expert in this area, so my review should be taken with a grain of salt.
Sorry, something went wrong.
Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01Y2CKGDURpDRVEHD7FfWnps
There was a problem hiding this comment.
lgtm!
Sorry, something went wrong.
|
Thanks @itamaro for the PR 🌮🎉.. I'm working now to backport this PR to: 3.14, 3.15. |
Sorry, something went wrong.
|
GH-159823 is a backport of this pull request to the 3.15 branch. |
Sorry, something went wrong.
|
GH-159824 is a backport of this pull request to the 3.14 branch. |
Sorry, something went wrong.
…H-159766) (#159824) gh-159759: Fix libpython.static in PEP 739 build-details.json (GH-159766) When a shared library is also built, point `libpython.static` at `LIBPL`, the only place `make install` puts the static library, and don't list it for framework builds, which don't install one. Static-only builds keep the existing `LIBDIR` value, which is installed in that configuration. (cherry picked from commit e41b38b) Co-authored-by: Itamar Oren <itamarost@gmail.com>
…H-159766) (#159823) gh-159759: Fix libpython.static in PEP 739 build-details.json (GH-159766) When a shared library is also built, point `libpython.static` at `LIBPL`, the only place `make install` puts the static library, and don't list it for framework builds, which don't install one. Static-only builds keep the existing `LIBDIR` value, which is installed in that configuration. (cherry picked from commit e41b38b) Co-authored-by: Itamar Oren <itamarost@gmail.com>
| Back | FazBrowse Home | New Git URL |
When a shared library is also built, point libpython.static at LIBPL,
the only place make install puts the static library, and don't list it for
framework builds, which don't install one. Static-only builds keep the
existing LIBDIR value, which is installed in that configuration.
Written with assistance from Claude Code Opus 5.5