| 18 Mar 2025 |
lzcunt | no... | 20:11:53 |
lzcunt | Nothing to do. None of the projects specified contain packages to restore. | 20:13:09 |
lzcunt | yea seemingly this project depends on msbuild from mono-complete which we might not have (or it might be the msbuild package that needs SDK 6 which is EOL so that package also doesn't work) | 20:33:34 |
GGG | Doesn't `dotnet msbuild` work? That mightwork with legacy projects | 20:52:16 |
| 19 Mar 2025 |
| K900 joined the room. | 08:30:48 |
K900 | Hey folks, is the dotnet bootstrap supposed to take over an hour on a 16-core? | 08:31:22 |
K900 | Or am I holding it wrong somehow? | 08:31:27 |
Corngood | It's quite slow, but that seems like a lot. Is it idle? | 11:58:35 |
K900 | It's been doing something single threaded for a long time | 12:01:05 |
K900 | It is done now | 12:01:11 |
Corngood | Was the last update just not built yet on hydra, or were you doing something custom? | 12:16:57 |
K900 | staging-next | 12:20:57 |
lzcunt | That errors due to it needing .NETFramework,Version=v4.6.1 or whatever and I don't know how to fix that (not a .NET person sadly | 12:35:06 |
| 20 Mar 2025 |
@rosssmyth:matrix.org | Framework is the runtime that only works on Windows or Wine. Depending on the project you can try using upgrade-assistant | 01:11:08 |
GGG | Yeah, .NET Framework projects will not run natively on Linux, you'll need to run it inside wine or with mono, but considering mono has been abandoned by Microsoft and Wine team is maintaining it now, you might need wine anyways | 02:33:05 |
GGG | I did not instantly make the connection between packages.config and .NET Framework but I should have | 02:33:48 |
@rosssmyth:matrix.org | I did not know that Mono was abandon by MS. Sort of weird since Blazor/ASP.NET uses it for wasm | 02:38:50 |
GGG | They moved the part of the codebase they were interested in into the .NET codebase | 02:50:14 |
GGG | And now you can't really use it like you did with the original mono, it's only available on iOS and macOS without NativeAOT, and wasm without NativeAOT | 02:51:00 |
GGG | > We are happy to announce that the WineHQ organization will be taking over as the stewards of the Mono Project upstream at wine-mono / Mono ยท GitLab (winehq.org).
https://www.mono-project.com/ | 02:51:47 |
GGG | Although it seems like it still works as the old mono did, I don't know how long they'll maintain that for honestly, given that they only need it for Wine | 03:02:17 |
| @xsrp:matrix.org joined the room. | 03:16:48 |
| @xsrp:matrix.org changed their display name from Seraphim Pardee to srp. | 03:19:07 |
lzcunt | I've tried that before and it broke the build system severely so I can't do that | 08:48:15 |
lzcunt | upstream supports mono but I tried it and I couldn't get that to work either | 08:48:47 |
lzcunt | I think I'm gonna give up packaging OpenBVE for nixpkgs, I think they have a flatpak or something | 08:49:11 |
| 23 Mar 2025 |
Whovian9369 | Hey gang, me again to cause more chaos. Do any of you have experience building a project that uses Nuke.Common for building part of the program? Something I use a lot, https://github.com/Thealexbarney/LibHac , uses it for some CodeGen that needs to be done for proper use of the program hactoolnet. I do have a derivation that pulls the official binary and patches that if I need to use it instead, but it would be nice to make sure that I have a properly working build that I can do if I need to. | 15:00:35 |
Whovian9369 | I do also have an existing derivation that skips using Nuke, but it seems to be quietly "broken" in a few ways since the programs expecting you to have done codegen initially. | 15:02:29 |
Whovian9369 | (You can see that at https://github.com/Whovian9369/whovian_nixos_config/blob/main/home/packages/hactoolnet/package.nix ) | 15:02:49 |
Whovian9369 | Oh I just noticed that Avalonia seems to deal with this already - https://github.com/NixOS/nixpkgs/blob/master/pkgs/by-name/av/avalonia/package.nix#L151-L159
Is this the suggested way to deal with that, then? | 15:07:59 |