-
Notifications
You must be signed in to change notification settings - Fork 80
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
ARM/ARM64 not supported as values to --platform flag #437
Comments
Here is a UWP project with a solution file showing ARM/ARM64 usage: Here's an Uno project which shows other platform/configuration values: UnoTestWASMAssemblyMetadata.zip Don't think these are supposed to be a set list (if so that's not documented anywhere I think). They're almost like magic strings for some platforms it seems. In either case, I think the default if a value isn't mapped it should just passthru as what was typed. |
Finally found some docs on this, wanted to post here for reference: |
We need to build for ARM/ARM64 as platforms (as well as potentially other platforms names for different Android, iOS, etc... project types).
However, it appears that the list of values passed into the
--platforms
argument of theslngen
tool is first scrubbed, and anything beyond x86, x64, any cpu is effectively scrubbed:slngen/src/Microsoft.VisualStudio.SlnGen/SlnFile.cs
Lines 542 to 563 in f99e2e9
I assume this function is used by the
slngen
tool in addition to the msbuild target mode, as that's the behavior I'm seeing on the command line:This is a blocking issue for us adopting this tool in our workflow, everything else currently appears to be working fine.
The simplest solution would allow custom values by not making everything falling out of the switch statement go to
null
but instead pass through the originalplatform
value.The text was updated successfully, but these errors were encountered: