Skip CN1MetalShaders.metal when ios.metal build hint is off#4892
Merged
Conversation
The .metal shader file has no #ifdef CN1_USE_METAL guard (Metal Shading Language doesn't wrap the same way the companion .m files do), so it was always copied into the generated Xcode project. Xcode 26 ships the Metal Toolchain as a separately-downloaded component, so build servers without it failed compilation even when the build hint was off. Mirrors the existing MainWindowMETAL.xib / CodenameOne_METALViewController.xib cleanup in the !useMetal branch. Same fix already applied to BuildDaemon. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
Contributor
✅ Continuous Quality ReportTest & Coverage
Static Analysis
Generated automatically by the PR CI workflow. |
Collaborator
Author
|
Compared 90 screenshots: 90 matched. Native Android coverage
✅ Native Android screenshot tests passed. Native Android coverage
Benchmark ResultsDetailed Performance Metrics
|
Collaborator
Author
|
Compared 90 screenshots: 90 matched. Benchmark Results
Build and Run Timing
Detailed Performance Metrics
|
Collaborator
Author
|
Compared 90 screenshots: 90 matched. Benchmark Results
Build and Run Timing
Detailed Performance Metrics
|
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Summary
.metalshader file has no#ifdef CN1_USE_METALguard (Metal Shading Language doesn't wrap the same way the companion.mfiles do), so it was always copied into the generated Xcode project regardless of theios.metalbuild hint.error: cannot execute tool 'metal' due to missing Metal Toolchaineven when the build hint was off.MainWindowMETAL.xib/CodenameOne_METALViewController.xibcleanup in the!useMetalbranch. The same fix has already been applied (and pushed) to BuildDaemon.Why CI didn't catch this
The non-Metal
build-iosjob runs on GitHub'smacos-15runner, which has the Metal Toolchain pre-cached. So the leaked.metalfile silently compiled on CI. Production build servers ship a leaner Xcode 26 install without the toolchain, exposing the bug only there.Test plan
build-iosworkflow still passes (GL path,ios.metalunset)build-ios-metalworkflow still passes (Metal path,ios.metal=true)ios.metal=true🤖 Generated with Claude Code