Sender | Message | Time |
---|---|---|
6 May 2025 | ||
But are they statically or dynamically linked against the ssl shim? | 14:01:09 | |
it should be static, since it's a self-contained binary | 14:01:34 | |
it should only need the external deps, no runtime nor anything else | 14:01:42 | |
so AOT is always a single file? | 14:01:55 | |
it has some auxliary files like the pdb and other native dlls (when nuget libraries use pinvoke), but I haven't seen AOT binaries with dlls | 14:02:40 | |
* it has some auxliary files like the pdb and other native libraries (when nuget libraries use pinvoke), but I haven't seen AOT binaries with dlls | 14:02:46 | |
annoyingly, it seems like it doesn't add OpenSSL, ICU nor Kerberos to the needed section:
| 14:03:46 | |
* annoyingly, it seems like it doesn't add OpenSSL, ICU nor Kerberos to the needed section:
| 14:04:20 | |
In case it helps you can get an AOT build (and various other things) like dotnet-sdk.tests.console.cs.aot.built or similar | 14:07:26 | |
oh nice | 14:07:41 | |
there are tests for regular publish, single file, etc | 14:08:04 | |
7 May 2025 | ||
07:56:11 | ||
8 May 2025 | ||
Corngood: shouldn't this set DYLD_LIBRARY_PATH on macos? https://github.com/NixOS/nixpkgs/blob/b8d4a65cb17eb3ddec8f742f424a6d195500f281/pkgs/build-support/dotnet/build-dotnet-module/hooks/dotnet-fixup-hook.sh#L37 | 14:39:14 | |
9 May 2025 | ||
Yeah, probably. Thanks for the PR. I think there are some subtle differences from glibc, but there are quite a few places in nixpkgs that use it as your suggesting. | 01:45:13 | |
14 May 2025 | ||
03:52:58 | ||
15 May 2025 | ||
@corngood:corngood.com maybe we'll finally be able to source build feature bands in .NET 10? https://github.com/dotnet/announcements/issues/359 | 02:44:03 | |
Interesting, but a little vague. For the upgrades this month, 8 is done, 9 hit https://github.com/dotnet/dotnet/pull/546, and I haven't started 10 yet. I guess when I get to 10 I'll see whats going on... | 10:57:57 | |
18 May 2025 | ||
Is there a suggested way to deal with an outdated global.json ? Is it just to do something similar to substituteInPlace global.json --replace-fail 4.20.69 ${dotnetCorePackages.sdk_9_0.version} ? | 22:41:17 | |
("Outdated" relative to the SDK that I'm using to build, anyway.) | 22:41:36 | |
Oh, maybe I could just change the allowPrerelease key to true ? That may be the easiest solution here. | 22:47:52 | |
what is your actual case? | 22:48:21 | |
is the global.json pinning a exactly specific version? | 22:48:32 | |
or just the major/feature band | 22:48:39 | |
Specific version | 22:48:49 | |
| 22:48:59 | |
I'd just rm the global.json | 22:49:32 | |
assuming the build still works on 9.0.2xx | 22:49:42 | |
My flake is https://github.com/Whovian9369/aaru-nix-flake (Updating it which is why I'm encountering this) Upstream is https://github.com/aaru-dps/Aaru global.json was introduced with https://github.com/aaru-dps/Aaru/commit/8ee0926210df8e3a443456b567e17ad6f319125f | 22:50:07 | |
that global.json doesn't make much sense | 22:50:55 | |
it would be better to rollForward=latestPatch (aka 9.0.1xx instead) to still receive bug fixes while avoiding bumping the feature band | 22:52:07 |