| 14 Aug 2023 |
Emma [it/its] | In reply to @yarekt:matrix.org Oh wait, isn't mono like completely gone from dotnet these days? Hmm. Is this thing open source? Do you have something I can replicate on my machine? my thing? yes | 17:47:15 |
Emma [it/its] | git clone --recursive https://git.rory.gay/matrix/MatrixRoomUtils.git | 17:48:08 |
Emma [it/its] | build with nix build '.?submodules=1#web' -L | 17:48:26 |
Emma [it/its] | though if you want i can set up a quick and dirty repro repo (just the template project with a flake) | 17:50:02 |
Emma [it/its] | keep in mind that repo has the missing framework package manually added | 17:52:28 |
Emma [it/its] | In reply to @magikarpz:matrix.org follow the docs to get a buildDotnetModule derivation working, and then run the fetch-deps script from the derivation attributes, as shown in the docs ah i remember now why i cant use fetch-deps | 17:57:23 |
Emma [it/its] | error: getting status of '/home/root@Rory/EmptyBlazorWasmApp/default.nix': No such file or directory
that doesnt appear to work with flakes | 17:57:37 |
Emma [it/its] | building .#default.passthru.fetch-deps made a shellscript as result, i guess thats normal? | 19:31:50 |
Emma [it/its] | oh, using that did include browser-wasm | 19:33:13 |
Emma [it/its] | still fails to build though:
emptyblazorwasmapp-v1> /nix/store/igwf7hm6cjdcl0mac0n2rpmq47ssil6k-dotnet-sdk-7.0.306/sdk/7.0.306/Sdks/Microsoft.NET.Sdk/targets/Microsoft.NET.Sdk.FrameworkReferenceResolution.targets(135,5): error NETSDK1084: There is no application host available for the specified RuntimeIdentifier 'browser-wasm'. [/build/ml30php8kkq4lqgh2yc0g9fma5c2jnpm-source/EmptyBlazorWasmApp/EmptyBlazorWasmApp.csproj]
| 19:35:29 |
Emma [it/its] | Download EmptyBlazorWasmApp.tar.xz | 19:36:35 |
Emma [it/its] | steps taken:
- create empty blazor wasm project
- add simple flake with 1 output
- generate a deps.nix by invoking a slightly modified version of nuget-to-nix with a wrapper script (mkdeps) that dotnet restore's to a folder for nuget-to-nix to operate on
- use
nix build .\#default.passthru.fetch-deps to generate script at result
- run ./result
- copy output file over deps.nix
- run
nix build .#
| 19:38:45 |
| 15 Aug 2023 |
raphi | In reply to @emma:rory.gay
steps taken:
- create empty blazor wasm project
- add simple flake with 1 output
- generate a deps.nix by invoking a slightly modified version of nuget-to-nix with a wrapper script (mkdeps) that dotnet restore's to a folder for nuget-to-nix to operate on
- use
nix build .\#default.passthru.fetch-deps to generate script at result
- run ./result
- copy output file over deps.nix
- run
nix build .#
as a workaround you can set useAppHost = false and selfContainedBuild = true in the buildDotnetModule call blazor wasm support is not ideal atm | 08:27:06 |
Yarek T | In reply to @emma:rory.gay
steps taken:
- create empty blazor wasm project
- add simple flake with 1 output
- generate a deps.nix by invoking a slightly modified version of nuget-to-nix with a wrapper script (mkdeps) that dotnet restore's to a folder for nuget-to-nix to operate on
- use
nix build .\#default.passthru.fetch-deps to generate script at result
- run ./result
- copy output file over deps.nix
- run
nix build .#
Deps generated are the same for me | 16:40:15 |
Yarek T | Ah but yes, I get the error. How strange. I will poke around more. | 16:45:53 |
| nevoyu left the room. | 19:34:14 |
Emma [it/its] | In reply to @emma:rory.gay
steps taken:
- create empty blazor wasm project
- add simple flake with 1 output
- generate a deps.nix by invoking a slightly modified version of nuget-to-nix with a wrapper script (mkdeps) that dotnet restore's to a folder for nuget-to-nix to operate on
- use
nix build .\#default.passthru.fetch-deps to generate script at result
- run ./result
- copy output file over deps.nix
- run
nix build .#
the fetch-deps script added one that was missing before with the nuget-to-nix script (Microsoft.NETCore.App.Runtime.Mono.browser-wasm) | 19:56:31 |
Emma [it/its] | or at least, it did in our project, didnt check in the repro | 19:57:49 |
| 16 Aug 2023 |
mdarocha | from what I searched, wasm-tools, needed by the blazor wasm compilation, is packages as a dotnet workload | 06:55:48 |
mdarocha | and unfortunately, workloads aren't supported in Nix for now - see https://github.com/NixOS/nixpkgs/issues/226107 | 06:56:10 |
mdarocha | so to make wasm compilation fully work you would need to try to hack together some form of workload support, I know that previously something was attempted for maui | 06:56:44 |
| 19 Aug 2023 |
Emma [it/its] | shouldnt it be a matter of installing the relevant nuget packages? | 11:46:17 |
mdarocha | from what I understand workloads work a little bit differently and aren’t covered by the current nix mechanisms | 11:47:47 |