[xcode26.4] Merge remote-tracking branch main into xcode26.4#24859
[xcode26.4] Merge remote-tracking branch main into xcode26.4#24859
Conversation
) The _SmeltMetal target lacked Inputs/Outputs attributes, causing Metal shaders to always be recompiled even when unchanged. This follows the same cache/stamp file pattern used by _CoreCompileInterfaceDefinitions: - _BeforeSmeltMetal: deletes cache when any Metal file is newer - _ReadSmeltedMetal: reads cached _SmeltedMetal items for incremental builds - _SmeltMetal: now has Inputs/Outputs and writes cache after compilation Also adds a unit test (MetalShadersNotRecompiled) that verifies _SmeltMetal and _TemperMetal are skipped on the second build when no Metal files have changed. Fixes #24816 --------- Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
…ly=false. Fixes #24582. (#24800) When _ExportSymbolsExplicitly is false, the linker uses -u flags instead of -exported_symbols_list, so mtouch-symbols.list is not transferred to the remote Mac. Don't pass it to strip either, since the file won't exist. Fixes #24582. --------- Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Add support for the '@(RuntimeEnvironmentVariable)' item group, which is set when using 'dotnet run' and passing environment variables using '-e|--environment NAME=VALUE' to 'dotnet run'. This required adding the 'RuntimeEnvironmentVariableSupport' capability to tell 'dotnet run' that we support this. References: * dotnet/android#10770 * dotnet/sdk#52664 --------- Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com>
* Enable nullability. * Introduce numerous variations of ArrayFromHandle to handle various scenarios related to nullability: * NonNullArrayFromHandle: returns an empty array if the native array is null. * ArrayFromHandleDropNullElements: returns an array that will never have any null elements.ç * NonNullArrayFromHandleDropNullElements: both of the above. * Update consumers to use the best variation. * Add tests for modified APIs that didn't already have tests. Theoretically these changes may end up changing behavior, if there are native arrays with NSNull elements, in which case we'll now convert them to managed arrays without null elements for some APIs, but this should be exceedingly rare. Contributes towards #17285. --------- Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com>
…ate if an update is available. (#24854) `xcodebuild -showComponent ...` can return this: > Status: installedUpdateAvailable which we understood to be "Installed", which is incorrect. So fix the detection to handle this scenario, and (re)install the toolchain in question.
✅ [CI Build #59fb54d] Build passed (Build packages) ✅Pipeline on Agent |
✅ [PR Build #59fb54d] Build passed (Detect API changes) ✅Pipeline on Agent |
✅ [CI Build #59fb54d] Build passed (Build macOS tests) ✅Pipeline on Agent |
✅ API diff for current PR / commitNET (empty diffs)✅ API diff vs stableNET (empty diffs)ℹ️ Generator diffGenerator Diff: vsdrops (html) vsdrops (raw diff) gist (raw diff) - Please review changes) Pipeline on Agent |
This comment has been minimized.
This comment has been minimized.
🔥 [CI Build #59fb54d] Test results 🔥Test results❌ Tests failed on VSTS: test results 1 tests crashed, 0 tests failed, 155 tests passed. Failures❌ windows tests🔥 Failed catastrophically on VSTS: test results - windows (no summary found). Html Report (VSDrops) Download Successes✅ cecil: All 1 tests passed. Html Report (VSDrops) Download macOS tests✅ Tests on macOS Monterey (12): All 5 tests passed. Html Report (VSDrops) Download Pipeline on Agent |
4 participants
No description provided.