| 18 Jul 2025 |
 emily | when run in a build script for a package targeting that host platform | 20:54:30 |
| emily | even though there seems like reason you might want to care about build platform deps in such a build script too | 20:54:42 |
 dramforever | wait so if i'm building a build script dep | 20:55:04 |
| dramforever | what do i get for "HOST" and "TARGET" | 20:55:16 |
| emily | the same thing | 20:55:20 |
| emily | the build platform | 20:55:25 |
| emily | so it will notice they're the same and look at HOST_PKG_CONFIG and PKG_CONFIG_[buildPlatform] | 20:55:38 |
| emily | I really need to find the person who came up with build/host/target and take them to the Hague or something | 20:56:03 |
| emily | I don't care what they call build and host as long as they rename target to like if-you-are-not-writing-a-compiler-and-you-say-this-word-you-have-made-a-mistake | 20:56:37 |
| dramforever | so if non-cross, it looks at HOST_PKG_CONFIG and PKG_CONFIG_underscored_triple | 20:57:12 |
| emily | (dashed triple too! but yes) | 20:57:26 |
| dramforever | if it's cross it uses pkg-config for build and PKG_CONFIG_underscored_triple for host? | 20:57:31 |
| dramforever | really? | 20:57:40 |
| dramforever | i thought it replaces '-' with '_' | 20:57:48 |
| dramforever | otherwise why would they call it target_u | 20:57:57 |
