Skip to content

Conversation

@regro-cf-autotick-bot
Copy link

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/14577903030 - please use this URL for debugging.

@conda-forge-admin
Copy link
Contributor

conda-forge-admin commented Apr 21, 2025

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

I wanted to let you know that I linted all conda-recipes in your PR (recipe/meta.yaml) and found some lint.

Here's what I've got...

For recipe/meta.yaml:

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

@h-vetinari
Copy link
Member

C.f. #59 (though there are several open PRs and main is currently broken; c.f. #65)

@isuruf
Copy link
Member

isuruf commented May 27, 2025

@conda-forge-admin rerender.

conda-forge-webservices[bot] and others added 2 commits May 27, 2025 20:04
@conda-forge-admin
Copy link
Contributor

conda-forge-admin commented May 27, 2025

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

recipe/bld.bat Outdated
nmake nmakehlp.exe
nmake -f makefile.vc INSTALLDIR=%LIBRARY_PREFIX% MACHINE=%MACHINE% release
nmake -f makefile.vc INSTALLDIR=%LIBRARY_PREFIX% MACHINE=%MACHINE% install
nmake nmakehlp.exe MACHINE=%BUILD_MACHINE%
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@finnagin, how can I compile an executable for the build architecture (x86 here) to be used in the compilation process?

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@isuruf Looks like maybe you are trying to cross-compile arm64 or x64 on x86? Is that a correct read of the steps? If so you may need to run vcvarsall.bat x86_arm64 or vcvarsall.bat x86_x64 first.

If you are specifically trying to compile nmakehlp.exe for x86 and not cross-compile it you may need to pass MACHINE=IX86. Looking at the makefile.vc inside the tcl8.6.13-src.tar.gz file that meta.yml points to I see this:

#	MACHINE=(ALPHA|AMD64|ARM64|IA64|IX86)
#		Set the machine type used for the compiler, linker, and
#		resource compiler.  This hook is needed to tell the tools
#		when alternate platforms are requested.  IX86 is the default
#		when not specified. If the CPU environment variable has been
#		set (ie: recent Platform SDK) then MACHINE is set from CPU.

Are either of those things helpful/answer your question?

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We are trying to cross-compile for arm64 on x64. (I meant x64 and not x86 in my message)

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Ping @finnagin

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Sorry @isuruf, somehow missed the follow up message!

We are trying to cross-compile for arm64 on x64. (I meant x64 and not x86 in my message)

In that case, based on what I've had to do in the past, you would run vcvarsall.bat x64, then pass MACHINE=AMD64 into nmake nmakehlp.exe MACHINE=AMD64 . Then, run vcvarsall.bat x64_arm64, set MACHINE=ARM64 and run what the cross-compile build for arm64.

@isuruf
Copy link
Member

isuruf commented Oct 12, 2025

@conda-forge-admin rerender

@isuruf
Copy link
Member

isuruf commented Dec 23, 2025

@finnagin, @zooba any ideas here?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants