| 1 Jan 2025 |
 Whovian9369 | I believe you would just do > deps.json instead. | 15:40:52 |
| Whovian9369 | $ nix build -L .#ndecrypt-git
warning: Git tree '/home/whovian/.flakes/nix-game-preservation' is dirty
error:
… while evaluating an expression to select 'drvPath' on it
at «internal»:1:552:
… while calling the 'derivationStrict' builtin
at «internal»:1:208:
(stack trace truncated; use '--show-trace' to show the full trace)
error: syntax error, unexpected end of file, expecting expression
at /nix/store/qg2pdhwccz82apli9d6kc4r7agp04bza-source/ndecrypt/deps-git.json:1:1:
Is there a realistic solution to avoiding this issue when trying to build the deps file?
| 15:42:11 |
| Whovian9369 | The issue's come up quite often for me with deps.nix but now it's appearing with deps.json for me as well, which is a bit frustrating for likely obvious reasons. | 15:42:46 |
| Whovian9369 | So it looks like the answer is to fill in src.hash first, or work around it by doing nix build -L .#ndecrypt-git.src (for example) first. | 15:56:51 |
 Corngood | Isn't it `nuget-to-json` now? | 16:04:27 |
| Whovian9369 | Right, nice catch. | 16:04:56 |
| Whovian9369 | * I believe you would just do nuget-to-json $HOME/nuget_pkgs > deps.json instead. | 16:05:12 |
| Whovian9369 | Edited my above message | 16:05:18 |
 Emmanuel Genga | Does fetch-deps still work the same if I set the output file to deps.json? | 19:39:33 |
| Corngood | In reply to @genga898:matrix.org
Does fetch-deps still work the same if I set the output file to deps.json? Yeah, it should do | 19:43:08 |
| 2 Jan 2025 |
|  Vera left the room. | 11:48:08 |
| 9 Jan 2025 |
 GGG | 
Download image.png | 13:01:47 |
| GGG | 6pak: got back to looking at patchcil and I found where it lists the paths for native dependencies: | 13:01:49 |
| GGG | * 6pak: got back to looking at patchcil and I found where it lists the paths for native dependencies | 13:01:52 |
| GGG | but it seems like after the build, it just copies them to the root | 13:02:42 |
| GGG | 
Download image.png | 13:02:44 |
| GGG | so I don't know if we really need to read .deps.json or not, but I guess I'll implement it regardless | 13:03:15 |
| GGG | seems like no packages have the runtime/{rid} in their output either: | 13:12:36 |
| GGG | 
Download image.png | 13:12:39 |
 6pak | I forgot it will get flatten out when building for a specific RID, yeah | 15:49:48 |
| 6pak | what does the deps.json point to in that case? | 15:49:57 |
| 6pak | still a runtimes/whatever directory or to root? | 15:50:10 |
| 6pak | (it will have root in search path regardless so it could be either I guess) | 15:50:34 |
| GGG | In reply to @6pak:matrix.org
still a runtimes/whatever directory or to root? I mean, there's the runtime dir in .deps.json so I'll add that to the search path instead of doing the manual search in there as it could be literally anywhere | 15:52:14 |
| GGG | But idk if it adds to the search path only for that assembly or all of them | 15:52:32 |
| 6pak | for the assembly load context afaik | 15:52:50 |
| GGG | I see | 15:53:02 |
| 6pak | so unless the program creates a new one, it will be for all | 15:53:03 |
| 6pak | * so unless the program creates a new (isolated) one, it will be for all | 15:53:45 |
| GGG | That's rather annoying, because then native library resolution is dependent on control flow | 15:53:46 |
