| 18 Dec 2025 |
 Randy Eckenrode | Whatever the project tells it to do. | 16:56:38 |
 Katalin 🔪 | ah. (: | 16:56:43 |
| Randy Eckenrode | Swift build expects to vendor everything. With traits (like Cargo features), you can’t really pre-build libraries anymore. | 16:57:18 |
 emily | FWIW static libraries should really go in ${!outputDev}/lib IMO, or perhaps even a staticlib output. the reason we don't do that is because build systems are dumb. if it can be achieved for Swift it should be | 16:57:35 |
| Randy Eckenrode | I’m doing it here for the CMake builds needed by the toolchain. | 16:57:49 |
| emily | the lib output should be stuff required at runtime, which static libraries (and modules?) never are | 16:57:51 |
| Katalin 🔪 | and the compiler i.e. swiftc? | 16:58:00 |
| Katalin 🔪 | I'm currently looking but I don't know if you can get it to print a default include path | 16:58:11 |
| Katalin 🔪 | there's -Isystem and -I | 16:58:19 |
| Katalin 🔪 | like on a normal C compiler | 16:58:27 |
| Randy Eckenrode | I think swiftc probably doesn’t look beyond its toolchain location. | 16:58:38 |
| Randy Eckenrode | * I suspect swiftc probably doesn’t look beyond its toolchain location. | 16:58:47 |
| Randy Eckenrode | It supports being told where, which is what SwiftPM and CMake both do. | 16:59:06 |
| Randy Eckenrode | dev is not available for Swift packages due to some evil stuff I am doing to make `buildInputs = [ swift-foo ];‘ do something sensible with SwiftPM. | 17:00:15 |
| Katalin 🔪 | ah yeah that would make sense, I guess that's how it works with the Xcode toolchain too since that contains everything | 17:00:26 |
| Randy Eckenrode | * dev is not available for Swift packages due to some evil stuff I am doing to make buildInputs = [ swift-foo ]; do something sensible with SwiftPM. | 17:00:26 |
| Katalin 🔪 | it doesn't have /usr/include as a default path at least from a quick test | 17:00:36 |
| Randy Eckenrode | Otherwise, I agree. I’m (ab)using include for CMake files and Swift modules. | 17:01:01 |
| emily | you can get Clang to print out default paths. I forget the flag. | 17:01:02 |
| emily | I bet it works for swiftc too. | 17:01:05 |
| emily | staticlib then :) | 17:01:14 |
| Katalin 🔪 | ah, hold on. here we go | 17:03:26 |
| Katalin 🔪 | Redacted or Malformed Event | 17:04:21 |
| Katalin 🔪 | ah no, it only looks for a /usr/include/Foo/module.modulemap which is for the clang modules | 17:06:08 |
| Katalin 🔪 | yeah, looks like no default module paths outside the toolchain dir | 17:06:17 |
| Katalin 🔪 | this is with strace so I might have missed something | 17:07:05 |
| Katalin 🔪 | (when you write 'import Foo', that is) | 17:07:26 |
| Katalin 🔪 | good to know in any case, since I will need to deal with this in Meson at some point when I do installable libraries | 17:11:14 |
| Randy Eckenrode | I was thinking there might be some pushback on the evil I’m doing. 😂 | 17:32:33 |
| Randy Eckenrode | I’m (ab)using dev because of the default lib.getDev done in make-derivation.nix. | 17:33:16 |
