v1.0.0.0-preview.39
github-actions
released this
28 Apr 22:37
·
248 commits
to main
since this release
Release notes for 1.0.0.0-preview.39
This update mainly focused on this issue #133.
I was able to debug the error but I wasn't able to find the issue itself because it happens in the NuGet library itself. I moved on and these are the suggetions for the toolkit for now:
Anywhere we reference Stride.Core.Assets.CompilerApp
we have to add also <RuntimeIdentifier>win-x64</RuntimeIdentifier>
which makes it Windows only.
Stride.CommunityToolkit
library will have noStride.Core.Assets.CompilerApp
references, so it can be built correctly and be platfom agnostic. Should work in code-only and regular Stride Projects.- The new
Stride.CommunityToolkit.Windows
library will haveStride.Core.Assets.CompilerApp
reference and also<RuntimeIdentifier>win-x64</RuntimeIdentifier>
, at the moment it is an empty library refrencingStride.CommunityToolkit
project mainly for code-only purpose, just to remove the above boilerplate. That means, code only examples would referenceStride.CommunityToolkit.Windows
instead ofStride.CommunityToolkit
. This could be done also for Linux later. Stride.CommunityToolkit.Skyboxes
library mainly for code-only purpose, will haveStride.Core.Assets.CompilerApp
reference removed so the NuGet package can be created. Because it is used withStride.CommunityToolkit.Windows
, it should build correctly
What's Changed
🔁 Build & Deploy
- Update 15 - Cross platform improvements by @VaclavElias in #134
Full Changelog: 1.0.0.0-preview.38...1.0.0.0-preview.39