[isuruf]

Install a PEP 739 build-details.json on Windows too, at %PREFIX%\lib\python\build-details.json (the stdlib directory, same as on unix).

• Tools/build/generate-build-details.py doesn't work on Windows (it relies on LDVERSION and assumes the DLL lives in LIBDIR), so this reuses upstream's Windows generator (PC/layout/support/builddetails.py). It doesn't need to run the target interpreter, so it works for cross-compilation too.
• Paths are adjusted for conda's unix-like Windows layout: base_prefix = ../.., base_interpreter = ./python.exe, libpython.dynamic[_stableabi] = ./python3XY[t][_d].dll / ./python3[t][_d].dll, c_api.headers = ./include/python.
• Bumps the build number.

Checklist

• Used a personal fork of the feedstock to propose changes
• Bumped the build number
• Re-rendered with the latest conda-smithy
• Ensured the license file is being packaged.

🤖 Generated with Claude Code

[conda-forge-admin]

Hi! This is the friendly automated conda-forge-linting service.

I just wanted to let you know that I linted all conda-recipes in your PR (recipe/meta.yaml) and found it was in an excellent condition.

I do have some suggestions for making it better though...

For recipe/meta.yaml:

• ℹ️ The use of pkg-config is deprecated. Please use pkgconf instead.
• ℹ️ The recipe is not parsable by parser conda-souschef (grayskull). This parser is not currently used by conda-forge, but may be in the future. We are collecting information to see which recipes are compatible with grayskull.
• ℹ️ The recipe is not parsable by parser conda-recipe-manager. The recipe can only be automatically migrated to the new v1 format if it is parseable by conda-recipe-manager.

_{This message was generated by GitHub Actions workflow run https://github.com/conda-forge/conda-forge-webservices/actions/runs/41927732133. Examine the logs at this URL for more detail.}