-
Notifications
You must be signed in to change notification settings - Fork 1.7k
add watchOS CI build target #13359
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Closed
matthargett
wants to merge
11
commits into
bytecodealliance:main
from
rebeckerspecialties:claude/add-watchos-ci-target-lSsZ6
+20
−1
Closed
add watchOS CI build target #13359
Changes from all commits
Commits
Show all changes
11 commits
Select commit
Hold shift + click to select a range
ec946e4
ci: add watchOS compile targets to platform_checks
claude 076b18f
prtest:platform-checks
claude 13542b8
ci: use cargo check for watchOS platform targets
claude b701565
ci: drop arm64_32-apple-watchos, add WATCHOS_DEPLOYMENT_TARGET
claude a63d6a6
ci: scope watchOS check to compile-only path
claude 1973825
ci: restore arm64_32-apple-watchos, set WATCHOS_DEPLOYMENT_TARGET=11.0
claude 81c5eba
ci: check cranelift-codegen arm64 backend for watchOS targets
claude 7a44118
ci: check cranelift-codegen core for arm64_32-apple-watchos without a…
claude 55aa537
ci: use cranelift-entity for arm64_32-apple-watchos check
claude ca6981f
bump iOS deployment target, less verbose comment
matthargett 4538534
review feedback
matthargett File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Ideally this would use
-p wasmtime, and is the only blocker for that publishing a newtarget-lexicon?There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think so.
--no-default-featuressidesteps needing the mach2 update.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Ok, in that case I think it's best to get
target-lexiconpublished first to add the check for wasmtime here. Otherwise I suspect this probably already passed prior to your work and the real interesting portabilty target is Wasmtime itself, so the check as-is isn't buying a whole lot