You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently build.ps1 expects there to be valid x86/x64/arm64 builds available. When building custom versions you may for example only require x86/x64.
The complexity will largely be around the chromiumembeddedframework.runtime.nuspec. The locales and swiftshader folders will need to be moved into the arch specific packages (this is preferably anyway). It wasn't clear when using a chromiumembeddedframework.runtime.json file to specify the RID graph that splitting these was possible. I'm fairly confident that it is now, testing will be required
Add additional parameter to allow for customisation
The complexity will largely be around the chromiumembeddedframework.runtime.nuspec. The locales and swiftshader folders will need to be moved into the arch specific packages (this is preferably anyway). It wasn't clear when using a chromiumembeddedframework.runtime.json file to specify the RID graph that splitting these was possible. I'm fairly confident that it is now, testing will be required
After testing unfortunately this doesn't work.
Structure will need to remain as is for now. First step will allow only for creating the older packages.
Currently
build.ps1
expects there to be validx86/x64/arm64
builds available. When building custom versions you may for example only requirex86/x64
.The complexity will largely be around the chromiumembeddedframework.runtime.nuspec. The
locales
andswiftshader
folders will need to be moved into thearch
specific packages (this is preferably anyway). It wasn't clear when using a chromiumembeddedframework.runtime.json file to specify theRID
graph that splitting these was possible. I'm fairly confident that it is now, testing will be requiredchromiumembeddedframework.runtime
packages to confirmlocales
andswiftshader
folders are copied correctly.The text was updated successfully, but these errors were encountered: