PEP 739 build-details.json points libpython.dynamic at a nonexistent path in framework builds #159998

Bug report

In a macOS framework build, libpython.dynamic in the installed build-details.json points to a non-existing file. Tools/build/generate-build-details.py joins LIBDIR and LDLIBRARY. In framework builds, though, LDLIBRARY is the library's path relative to PYTHONFRAMEWORKPREFIX (Python.framework/Versions/3.16/Python), not a file name in LIBDIR.

For example, with ./configure --enable-framework=/Library/Frameworks:

"dynamic": "/Library/Frameworks/Python.framework/Versions/3.16/lib/Python.framework/Versions/3.16/Python"

The library is installed at /Library/Frameworks/Python.framework/Versions/3.16/Python. With --relative-paths, the value becomes ./lib/Python.framework/Versions/3.16/Python instead of ./Python.

The iOS framework rule also installs $(LDLIBRARY) relative to PYTHONFRAMEWORKPREFIX, so I expect the same problem there, but I haven't checked an iOS build.

This is the remaining framework part of gh-159759, which fixed libpython.static for the same builds.

CPython versions tested on:

CPython main branch

Operating systems tested on:

macOS

Linked PRs

• gh-159998: Fix libpython.dynamic in build-details.json for framework builds #160005
• [3.15] gh-159998: Fix libpython.dynamic in build-details.json for framework builds (GH-160005) #160145
• [3.14] gh-159998: Fix libpython.dynamic in build-details.json for framework builds (GH-160005) #160146