Commit Graph

8 Commits

Author SHA1 Message Date
Sam
6e1a464f82 swiftPackages.swiftpm: patch swift-crypto as needed 2025-10-11 14:47:33 -07:00
Sam
d18cfb1058 swiftPackages.swiftpm: drop upstreamed patches
Some of these were not technically upstreamed but all have been fixed
2025-10-11 14:44:18 -07:00
Sam
483fd74afc swiftPackages.swiftpm: fix patches that no longer apply cleanly 2025-10-11 14:44:17 -07:00
Maximilian Bosch
2dcdf60272 swift: fix build w/ glibc-2.39
Failing Hydra build: https://hydra.nixos.org/build/249763077/nixlog/12

The problem is that glibc commit
64b1a44183a3094672ed304532bedb9acc707554 marked the `FILE*` argument of a few
functions including `fread` & `ferror` as non-null. The applied patch
("Android: add better nullability checks for nullability annotations added in NDK 26")
is targeted for the Android platform, but fixes said issue as well: the
handle returned from `fopen` is of type `Optional<T>` and the `guard`
expression unwraps that now (and throws an exception if `nil` is
returned). The previous `nil`-check didn't modify the type of `fp`, but
only raised the exception and moved on with `Optional<T>`.

It's a little sad that the patch needs to be applied at so many places,
but I guess that's what you get with language-level package managers 🤷
Also, seems good-enough to me given that it's actually temporary, the
patch is already upstream and will probably be obsolete at one of the
next Swift updates.
2024-03-02 19:01:51 +01:00
Pavel Sobolev
56aa31d0b4 swiftpm: force-unwrap file handles in swift-tools-support-core 2023-11-21 21:19:55 +03:00
Stéphan Kochen
f85d12198f swift: 5.7.3 -> 5.8 2023-04-30 15:03:20 +02:00
Stéphan Kochen
72fa71720b swiftpm: disable -index-store-path Apple extension 2023-02-01 08:29:36 +01:00
Stéphan Kochen
ece9224c8a swiftpm: init at 5.7 2022-10-10 21:26:50 +02:00