| 12 Nov 2024 |
 l0b0 | I don't know Unity, though. I might just ask upstream if they can provide the script. | 03:05:09 |
| l0b0 | Also, I've no idea whether it's reasonable to actually use Unity (a closed source product) to build Daggerfall Unity (an open source package). | 03:05:43 |
 Corngood | Looks like unity was removed from nixpkgs a couple of years ago: https://github.com/NixOS/nixpkgs/pull/177918
unityhub still exists, but that wouldn't be useful for building projects in the sandbox.
| 13:52:10 |
| 13 Nov 2024 |
|  dish [Fox/It/She] joined the room. | 03:10:06 |
| dish [Fox/It/She] | howdy y'all, was wondering if there's a way to build an app that targets .net framework 4.8 in nixos | 03:10:54 |
| dish [Fox/It/She] | * howdy y'all, was wondering if there's a way to build an app that targets .net framework 4.8 in nixpkgs | 03:11:03 |
| dish [Fox/It/She] | I'm trying to add https://github.com/ijwu/enemizer as part of | 03:11:26 |
| dish [Fox/It/She] | https://github.com/nixos/nixpkgs/pull/355563 | 03:11:39 |
| dish [Fox/It/She] | and there's a bunch of different .net version deps, several rely on .net framework 4.8, one relies on .net6.0, and one relies on "netstandard2.0" according to its .csproj file | 03:12:32 |
| dish [Fox/It/She] | I've had no luck with using buildDotnetModule so far. | 03:13:44 |
| Corngood | Is there a project file you can use instead of the sln? Publishing an sln often causes problems.
Also can you share what happens when you run `fetch-deps`?
Feel free to @ me on the PR if you'd rather discuss there. | 04:00:36 |
| dish [Fox/It/She] | In reply to@corngood:corngood.com
Is there a project file you can use instead of the sln? Publishing an sln often causes problems.
Also can you share what happens when you run `fetch-deps`?
Feel free to @ me on the PR if you'd rather discuss there. fetch-deps is fine, and I've tried the project file of the specific part I need, though it fails trying to find the core library that's in the same repo | 04:09:36 |
| dish [Fox/It/She] | I'll ping you on the PR, the build command(with flakes and nix-command enabled) is nix build github:pyrox0/nixpkgs/archipelago-from-source#enemizer | 04:10:19 |
| dish [Fox/It/She] | note that the specific package isn't the focus of the PR, but is one component of it. | 04:11:22 |
| Corngood | Ah, I see. fetch-deps works because it's only restoring the SDK-style projects: Enemizer.CLI.Core.csproj and EnemizerLibrary.csproj.
Do you actually need the whole solution, or can you get away with just building one or both of those projects?
Alternatively you might be able to build it as-is using mono/xbuild. The only thing I see in nixpkgs using xbuild is keepass.
| 13:27:33 |
| Corngood | Converting the other projects to dotnet-sdk style is probably the best option long-term. | 13:28:42 |
| dish [Fox/It/She] | In reply to @corngood:corngood.com
Ah, I see. fetch-deps works because it's only restoring the SDK-style projects: Enemizer.CLI.Core.csproj and EnemizerLibrary.csproj.
Do you actually need the whole solution, or can you get away with just building one or both of those projects?
Alternatively you might be able to build it as-is using mono/xbuild. The only thing I see in nixpkgs using xbuild is keepass.
I believe I only need library and core, the two you mentioned. would I just do library as its own derivation and then cli.core as the main derivation? | 17:43:43 |
| dish [Fox/It/She] | with it inheriting the library project through the dependency field or whatever its called(i cant remember the name otoh but its in the dotnet language section) | 17:44:19 |
| Corngood | I think you'd only need one derivation, just set projectFile to Enemizer/EnemizerCLI.Core/EnemizerCLI.Core.csproj, since it depends on the other csproj. | 18:13:22 |
| Corngood | I'm not sure if that project supports packing to nuget packages? If so you might want to set packNupkg. It depends on what's consuming it. | 18:14:17 |
| dish [Fox/It/She] | In reply to@corngood:corngood.com
I think you'd only need one derivation, just set projectFile to Enemizer/EnemizerCLI.Core/EnemizerCLI.Core.csproj, since it depends on the other csproj. I tried that but it didn't work, let me check if that work | 18:14:37 |
| dish [Fox/It/She] | * I tried that but it didn't work iirc, let me check if that work | 18:14:41 |
| dish [Fox/It/She] | * I tried that but it didn't work iirc, let me check if that does work | 18:14:47 |
| dish [Fox/It/She] | oh okay it's failing with a different error(its trying to hardcode dotnet compiler paths in the source code?) | 18:17:20 |
| dish [Fox/It/She] | Download enemizer.log | 18:19:57 |
| dish [Fox/It/She] | here's the logfile, if you can make any sense of it(I can't) | 18:20:09 |
|  inayet joined the room. | 22:15:21 |
| 14 Nov 2024 |
| Corngood | In reply to @pyrox:pyrox.dev
oh okay it's failing with a different error(its trying to hardcode dotnet compiler paths in the source code?) I think what's happening here is it's using an old version of Microsoft.Net.Compilers which doesn't seem to work on platforms where a .net executable can't be executed directly.
If I remove <PackageReference Include="Microsoft.Net.Compilers" Version="2.3.2" /> from both projects, and also remove this:
<Content Include="enemizerBasePatch.json">
<CopyToOutputDirectory>Always</CopyToOutputDirectory>
</Content>
<Content Include="exported_symbols.txt">
<CopyToOutputDirectory>Always</CopyToOutputDirectory>
</Content>
it builds.
| 13:45:59 |
| Corngood | Here's the PR for the latest round of dotnet upgrades (with 9.0 final), including some infrastructure changes: https://github.com/NixOS/nixpkgs/pull/355753
There are some breaking changes, so if anyone maintains dotnet derivations outside of nixpkgs, I'm interested in test cases or feedback. | 13:47:58 |
| 16 Nov 2024 |
|  meebey aka Mirco Bauer joined the room. | 01:14:09 |
