Support Windows ARM64 platform

[regro-cf-autotick-bot]

This feedstock is being rebuilt as part of the windows arm migration.

Feel free to merge the PR if CI is all green, but please don't close it
without reaching out the the ARM Windows team first at @conda-forge/help-win-arm64.

If this PR was opened in error or needs to be updated please add the bot-rerun label to this PR. The bot will close this PR and schedule another one. If you do not have permissions to add this label, you can use the phrase @conda-forge-admin, please rerun bot in a PR comment to have the conda-forge-admin add it for you.

_{This PR was created by the regro-cf-autotick-bot. The regro-cf-autotick-bot is a service to automatically track the dependency graph, migrate packages, and propose package version updates for conda-forge. Feel free to drop us a line if there are any issues! This PR was generated by https://github.com/regro/cf-scripts/actions/runs/21376843311 - please use this URL for debugging.}

• fix win-arm64 mpdecimal-feedstock#8
• Enable assembly and applink support for win-arm64 openssl-feedstock#218

[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 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/21424125986. Examine the logs at this URL for more detail.}

[isuruf]

@finnagin this is almost working now. We are cross compiling from x86_64 to arm64 and therefore we can't compile the python *.py files to .pyc. What we do in Unix is to build a separate python for build platform (x86_64) and use that to compile the *.py files. Would you be able to look into doing that here?

cc @zooba

[finnagin]

Sure @isuruf! I'll take a look.

[zooba]

We are cross compiling from x86_64 to arm64 and therefore we can't compile the python *.py files to .pyc.

The Programs/_freeze_module.c tool already gets built and used as part of a normal CPython build, and it should be very close to being able to generate normal .pyc files (it's used for some internal build steps that don't require regular .pyc files).

A patch to adapt that to be usable here would be totally welcome upstream. Saves rebuilding the entire interpreter again.