-
-
Notifications
You must be signed in to change notification settings - Fork 14.7k
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
Unable to run an empty Avalonia .NET app from source using dotnet run
#350147
Comments
Hi, Avalonia depends on some libs.
then enter shell: |
There also ILSpy.Avalonia package in nixpkgs Upd. And even Avalonia 11 o_O |
Or if You don't use flakes, then create file shell.nix:
then run |
@AlienJust is there something I could do to make it work out of the box? I mean contribute to Nix. I mean it is interesting that there's Avalonia package, but it is also very surprising that installing it does not resolve the issue. I think the best solution would be to do something so that the P.S. not using flakes yet |
Describe the bug
The app fails to start with
Steps To Reproduce
Steps to reproduce the behavior:
dotnetCorePackages.sdk_8_0
dotnet new install "Avalonia.Templates"
dotnet new avalonia.app -o MyApp
MyApp/
dodotnet run
Expected behavior
The app should start
Additional context
The default template pulls SkiaSharp.NativeAssets.Linux package, which has
libSkiaSharp.so
. It ends up inbin/Debug/net8.0/runtimes/linux-x64/native/libSkiaSharp.so
, but can not be loaded.Not quite sure what exactly is going on, as installing
fontconfig
NixOS package did not resolve the error at the top (libfontconfig.so.1: cannot open shared object file: No such file or directory). I suspect for a descent experience all native dependencies from NuGet need to be patched on download (might break building for other Linuxes) or on build (whenbin/Debug
is created).EXTRA: the issue also reproduces with
dotnet publish
followed bydotnet MyApp.dll
frompublish/
output directory.Notify maintainers
@kuznero @mdarocha
Metadata
Add a 👍 reaction to issues you find important.
The text was updated successfully, but these errors were encountered: