Skip to content

Fix Editor target settings for osx-x64 / osx-arm64 native plugins#755

Open
hadashiA wants to merge 1 commit into
GlitchEnzo:masterfrom
hadashiA:fix-osx-editor-target
Open

Fix Editor target settings for osx-x64 / osx-arm64 native plugins#755
hadashiA wants to merge 1 commit into
GlitchEnzo:masterfrom
hadashiA:fix-osx-editor-target

Conversation

@hadashiA

@hadashiA hadashiA commented May 23, 2026

Copy link
Copy Markdown
Contributor

Summary

Fix the default NativeRuntimeAssetConfiguration entries for osx-x64 and
osx-arm64 so that native macOS plugins from NuGet packages are imported
with correct Editor compatibility and CPU architecture.

Current vs. expected behavior

When a NuGet package containing macOS native libraries
(runtimes/osx-x64/native/, runtimes/osx-arm64/native/) is installed:

Runtime Current Expected
osx-arm64 Editor target disabled Editor enabled, CPU = ARM64
osx-x64 Editor enabled, CPU = "Any CPU" Editor enabled, CPU = x86_64

Test plan

  • Installed Cysharp.NativeCompressions (which ships both osx-x64 and
    osx-arm64 natives in the standard runtimes/<rid>/native/ layout)
    into a fresh project
  • Verified PluginImporter settings:
    • osx-arm64 dylib: Editor enabled, OS = OSX, CPU = ARM64
    • osx-x64 dylib: Editor enabled, OS = OSX, CPU = x86_64

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.

1 participant