i think we use whatever we used on xamarin
i think we use whatever we used on xamarin
Pwhich should still work
Pboth of these issues you can't resolve really, you can attempt to reduce the size issue by enabling linking but fundamentally you kinda need assemblies to run a .NET application!
Pas for the bluetooth thing i have no idea why SDL needs it but it does
Tputting them in an undocumented folder in the nuget ain't working anymore chief
Tyou need to put them into a different path, compressed into an android bundle, and mark them to be imported
Tluckily android bundles are literally just zips so you can create them easily
Tthis changed in the middle of net6 some good time ago
Pyeah no we don't do that
Pwe have explicit msbuild targets just as we did with xamarin
Twell, the way i described is the recommended solution now
Tand anything i tried to use in net6+ for android was broken
Ti honestly don't understand why nuget is so moronic when it comes to native libs
Poh nvm that's what we do with ios
Pon android we just have a .aar next to the .dll
Tyeah ios stayed the same i think
Tyup, that's the bundle bs
Pour ios solution is so chaotic
Tlooks... as expected
Ti went through some hellish troubles to figure out how to package veldrid-spirv the modern way
Tthere are like no docs at all
Tand issues on the nuget repo about lack of docs just tell you to look how other projects do it 
Pyeah i really dislike nuget and msbuild
Pi like how modern msbuild hides the complexity though
P...until it doesn't
Tif only c# was a simple as "invoke compiler" and you're done :(
Ti take cursed msbuild xml over cmake though
Pyeah i mean cmake is a low bar though
Ii will be doing that in a moment
Ijust tried building and running android app template, and it seems to have missing assemblies as well
Ii tried it on .net6, currently downloading .net7 to see if its any different
Phave you tried
dotnet build -c releaseInope
Igonna try rn
Iokay, this did help
Idotnet included assemblies into apk without <EmbedAssembliesIntoApk>true</EmbedAssembliesIntoApk> ,and also optimized them for size
Ihowever building android demo from silk failed
I
Llmao mono compiler crash classic
Puuuuuhhhhhhhhhhhhh
Ttry net7 i guess
Iyeah, installing workloads on net7 right now
Tnet7-android works great on windows at least ¯\_(ツ)_/¯
Plet the record show
PI hate mono
L:B:ono
Ldarn
P
onoPcome on you use Linux you should know all about case sensitivity
Lwindows is also uses a case sensitive filesystem
