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.
dotnet publish doesn't copy proper native/xenko dependencies
See original GitHub issueRelease Type: GitHub
Version: master
Describe the bug
Running dotnet publish does not properly copy dependencies.
It seems dotnet publish uses slightly different targets than what’s done for standard build.
(note: heard it might be unified in .NET Core 3.0)
To Reproduce Steps to reproduce the behavior:
- Create a new game with Linux or macOS
- Build Linux or macOS (might be optional)
- Run
dotnet publish
Expected behavior
Bin\Linux\Debug\linux-x64\publish should contain all the native files (that are pulled by .ssdeps) just like in Bin\Linux\Debug\linux-x64 but it doesnt.
The fix likely needs to be done in https://github.com/xenko3d/xenko/blob/master/sources/core/Xenko.Core/build/Xenko.Core.targets
Issue Analytics
- State:
- Created 5 years ago
- Comments:11 (3 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
I have a solution for this will submit a PR.
With these same changes applied to the macOS project and manually copying the data folder to publish (for now) I can successfully run a simple test game on my MacBookPro. Note however that it takes forever (7 mins) to launch. Looks like most of that time is compiling shaders.
Now I will see how I can get the data folder to properly publish automatically.