| 28 Apr 2025 |
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 |
6pak | * (tldr the sdk_9_0 is currently binary :)) | 20:54:41 |
Corngood | Yeah, but the sdk includes the runtime, so if you care about running on the source built runtime it might matter | 20:57:31 |
ortolanbunting3002 | In reply to @6pak:matrix.org . With this workaround I can install the workloads, but they are still ignored by dotnet restore
| 21:17:06 |
ortolanbunting3002 | In reply to @ortolanbunting3002:tchncs.de In reply to @6pak:matrix.org . With this workaround I can install the workloads, but they are still ignored by dotnet restore
Ah, how do I use them then?
| 21:20:03 |
| 1 May 2025 |
| Rosuavio changed their display name from Rosario Pulella to Rosuavio. | 20:08:19 |
| 3 May 2025 |
Whovian9369 | It seems that nuget2nix doesn't support spaces in the projectFile value, from what I can tell?
dotnet-sdk = dotnetCorePackages.sdk_9_0;
dotnet-runtime = dotnetCorePackages.runtime_9_0;
nugetDeps = ./deps.json;
projectFile = "mbundle extractor/mbundle extractor.csproj";
selfContainedBuild = false;
dotnetBuildFlags = [ "--framework net9.0" ];
dotnetInstallFlags = [ "--framework net9.0" ];
$ ./fetch-deps deps.json
fetching dependencies for rune-factory-4-special-mbundle-extractor-unstable-2021-12-30
Running phase: unpackPhase
unpacking source archive /nix/store/knnjxlszi45ylm5m4hj8lkjfjyrx09vj-source
source root is source
Running phase: patchPhase
Running phase: configureNuget
The template "NuGet Config" was created successfully.
Processing post-creation actions...
Running phase: updateAutotoolsGnuConfigScriptsPhase
Running phase: configurePhase
Executing dotnetConfigureHook
MSBUILD : error MSB1009: Project file does not exist.
Switch: mbundle
| 03:12:55 |
Whovian9369 | Similar issue if I do "'mbundle extractor/mbundle extractor.csproj'"
Switch: 'mbundle | 03:13:22 |
Whovian9369 | Used repo is https://github.com/darkxex/Rune-Factory-4-Special-Mbundle-Extractor | 03:14:45 |