| 27 Apr 2025 |
 6pak | presumably the source build either doesn't support the android workload or it's not enabled in the nix build | 14:12:46 |
| 6pak |
dotnetCorePackages.dotnet_9.sdk
and accessing the sdk like that is lowkey an implementation detail
| 14:15:15 |
| 6pak | you probably want dotnetCorePackages.sdk_9_0 instead | 14:15:41 |
| 28 Apr 2025 |
 Emma [it/its] | TIL dotnet doesnt work in termux lol | 08:41:12 |
| Emma [it/its] | export DOTNET_GCHeapHardLimit=1C0000000 works i suppose | 08:44:16 |
| Emma [it/its] | also missing ICU it seems | 08:45:28 |
| Emma [it/its] | bash-5.2$ dotnet bin/Release/net9.0/linux-arm64/MatrixAntiDmSpam.dll
Process terminated. Couldn't find a valid ICU package installed on the system. Please install libicu (or icu-libs) using your package manager and try again. Alternatively you can set the configuration flag System.Globalization.Invariant to true if you want to run with no globalization support. Please see https://aka.ms/dotnet-missing-libicu for more information.
at System.Environment.FailFast(System.Runtime.CompilerServices.StackCrawlMarkHandle, System.String, System.Runtime.CompilerServices.ObjectHandleOnStack, System.String)
| 08:51:24 |
|  @coolio:nope.chat joined the room. | 18:21:24 |
 ortolanbunting3002 | In reply to @6pak:matrix.org
presumably the source build either doesn't support the android workload or it's not enabled in the nix build Can I use the non-source build in Nix?
Can I enable the android workload for the nix build?
| 20:34:44 |
 Corngood | In reply to @ortolanbunting3002:tchncs.de
Can I use the non-source build in Nix?
Can I enable the android workload for the nix build? You can use e.g. dotnetCorePackages.sdk_8_0-bin, but if you're seeing cases where the source built one isn't a drop in replacement, could you make an issue and @ me? | 20:45:30 |
| 6pak | it doesn't have the android stuff in sdk-manifests | 21:14:16 |
| 6pak | tbf fedora build doesnt either | 21:14:19 |
| 6pak | so likely VMR issue | 21:14:25 |
| 6pak | https://github.com/dotnet/source-build/issues/3242 | 21:18:14 |
| 29 Apr 2025 |
|  jimalexberger joined the room. | 14:05:05 |
| ortolanbunting3002 | In reply to @6pak:matrix.org
dotnetCorePackages.dotnet_9.sdk
and accessing the sdk like that is lowkey an implementation detail
The issue actually seems to have been using dotnetCorePackages.dotnet_9.sdk instead of dotnetCorePackages.sdk_9_0. After changing that, it works.
| 18:44:19 |
| ortolanbunting3002 | But now I have the Read-only file system issue when trying to install workloads.
| 18:47:51 |
| Emma [it/its] | Because it tries to write to the nix store | 18:48:20 |
| ortolanbunting3002 | I know, I've had this issue before and that's also the reason I was using dotnet_9.sdk. Because I had read this
| 18:52:04 |
| 6pak | yeah because dotnet_9.sdk will get the source built sdk | 18:52:26 |
| 6pak | while sdk_9_0 currently aliases to the binary one | 18:52:36 |
| 6pak | yeah ironically binary builds needs an additional hack | 18:52:59 |
| 6pak | . | 18:53:14 |
| ortolanbunting3002 | Would it theoretically be possible to install the workloads using nix?
| 18:57:19 |
| 6pak | yeah | 18:58:07 |
| 6pak | just no one implemented that | 18:58:10 |
| Emma [it/its] | In reply to @6pak:matrix.org
while sdk_9_0 currently aliases to the binary one Oh huh, i should switch then, i thought both were source built | 20:09:28 |
| Corngood | It's a bit more complicated than that. The runtime is always source built unless you use -bin, and the sdk will be source built if you use -source, or if you use the 1xx feature level ask, since it can be built from source | 20:53:53 |
| Corngood | * It's a bit more complicated than that. The runtime is always source built unless you use -bin, and the sdk will be source built if you use -source, or if you use the 1xx feature level sdk, since it can be built from source | 20:54:09 |
| 6pak | (tldr the sdk is currently binary :)) | 20:54:30 |
