| 1 Oct 2025 |
samasaur | this is an issue i've seen before. anecdotally it seems to occur whenever a swift package depends on argumentparser. i've solved it on the PR the same way I solved it on my linked example repo, but if there's a better way to do it (ideally making any swift package that depends on argumentparser automatically get this) i'm all ears | 06:23:55 |
WeetHet | Does it matter if we just need to ship somewhat working swift for 25.11? | 06:32:33 |
samasaur | nope | 06:32:46 |
samasaur | I did fix it, which is the important bit, and since this swift 5.10 may only stick around until Randy's 6.2 rework, it doesn't need to be super pretty | 06:33:51 |
samasaur | also I think I'm wrong and you may just need to do this for any swiftpm project? | 06:34:07 |
WeetHet | I mean I would expect 99% of things to use it | 06:35:09 |
WeetHet | It's a part of corelibs | 06:36:07 |
WeetHet | Which are libdispatch, foundation and xtest | 06:36:36 |
samasaur | yeah i'm not concerned about it | 06:36:56 |
samasaur | i am a little concerned about the fact that i seem to have broken C++ interop | 06:37:12 |
samasaur | somewhat at least | 06:37:24 |
WeetHet | Do mpv and dotnet build and work? | 06:37:38 |
WeetHet | If yes, great, this is ready to ship in 25.11 imho | 06:37:54 |
samasaur | I'm trying
nom-build -A swiftPackages.swift.tests.cxx-interop-test
| 06:38:13 |
samasaur | and on linux that gives me
> <unknown>:0: warning: libstdc++ not found for 'x86_64-unknown-linux-gnu'; C++ stdlib may be unavailable
> /build/src/Sources/main.swift:1:8: error: no such module 'CxxStdlib'
> import CxxStdlib
> ^
> error: fatalError
| 06:38:30 |
samasaur | ah wait our wrapper does a string check for the old c++ interop flag, which doesn't work anymore and i've had to change out | 06:40:51 |
samasaur | hmm though the right answer is probably .interoperabilityMode(.Cxx) which is available from PackageDescription 5.9 | 06:42:41 |
samasaur | let me actually try to build mpv and dotnet | 06:42:48 |
samasaur | and that will inform the priority of fixing this | 06:42:55 |
WeetHet | I would argue that while nixpkgs technically has more swift consumers than mpv and dotnet, they are really not important and as long as those two build everything else can be marked as broken | 06:43:19 |
WeetHet | * I would argue that while nixpkgs technically has more swift consumers than mpv and dotnet, they are really not important and as long as those two build everything else can be marked as broken and dealt with after randy's rework | 06:43:31 |
samasaur | what is the attr name for dotnet | 06:43:43 |
WeetHet | dotnet-sdk? | 06:44:15 |
samasaur | also uhhh. nix-build -A mpv built without rebuilds | 06:44:20 |
samasaur | like downloaded from cache | 06:44:36 |
samasaur | as did dotnet-sdk | 06:44:47 |
WeetHet | Uhhh | 06:45:29 |
samasaur | that doesn't seem right does it | 06:45:39 |
WeetHet | Could you nix-instantiate --json?
| 06:45:41 |
samasaur | OH | 06:46:01 |