Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
[nuget] Publish a nuget package without a hyphen
See original GitHub issueCurrently it’s not possible to use Raylib-cs for .NET 7 WASM build due to the hyphen in the name. I reported the issue to dotnet/runtime and it has been already fixed and merged to main, see https://github.com/dotnet/runtime/issues/78992
However it might take a while before we see that in 7.0.x as I requested in ⬆️. Right now the target is 7.0.3 of the back-port PR:
https://github.com/dotnet/runtime/pull/79175
Even if they manage to successfully back-port the fix to 7.0.3, based on 6.0.3 it would take 3+ months before we see that.
So yes, admittedly publishing a nuget package without a hyphen would basically be a workaround for broken functionality in dotnet. I can try to prepare the .csproj and adjust a GitHub workflow if there is enough interest.
Issue Analytics
- State:
- Created 9 months ago
- Reactions:1
- Comments:7 (4 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
Thanks! No need to report separately. We can track those issues in your project. Though worth mentioning #118 could maybe help with ensuring the same emscripten version is used.
So far I found these issues:
I can report them separately and also report a WebAssembly build, however it’s more complicated because raylib must be compiled with the very same version of emscripten as the project. It’s because emscripten doesn’t follow semver (mentioned here).