| 17 Aug 2025 |
 fzakaria | pkg-config --list-all | grep boost
boost boost - Pkg-config file for boost
| 21:10:07 |
 emily | yeah Nixpkgs patches one in | 21:10:17 |
| emily | for some reason | 21:10:19 |
| emily | probably we should not | 21:10:21 |
| fzakaria | what's the answer then for pkg-config if you do depend in boost ? | 21:11:02 |
| emily | Nix should include the relevant flags in its own .pc | 21:11:34 |
| emily | for the headers | 21:11:39 |
| emily | since it depends on them | 21:11:41 |
| fzakaria | and ship the headers? | 21:11:48 |
| emily | no | 21:11:55 |
| emily | those would stay in the Boost package | 21:12:06 |
| fzakaria | I filed https://github.com/NixOS/nix/issues/13782 | 21:14:51 |
| fzakaria | my pkg-config knowledge is meh; so please augment it with anything that makes sense. | 21:28:26 |
| emily | seems correct to me | 21:35:23 |
 Sergei Zimmerman (xokdvium) | Welp boost doesn't ship pkg-config and never will | 21:36:58 |
| Sergei Zimmerman (xokdvium) | Not sure that is a good idea in general. Boost is a mess, no doubt there's a 1000 ways this could blow up if we try to be clever and add boost's include paths to the public flags | 21:38:55 |
| emily | it's expected by pkg-config that things required for header dependencies are included in the public flags though, no? | 21:39:27 |
| emily | the alternative is that the Nix libraries should at least propagatedBuildInputs it I suppose | 21:39:41 |
| Sergei Zimmerman (xokdvium) | It does | 21:39:45 |
| Sergei Zimmerman (xokdvium) | (Propagate the build inputs that is) | 21:39:59 |
| fzakaria | Not sure why it doesn't find it though maybe the hook for pkg-config doesn't work on propagatedBuildInputs | 21:40:35 |
| fzakaria | I put a full reproducer | 21:40:38 |
| fzakaria | so everyone who uses boost in a C++ project; has a broken pkg-config setup by default?
(irrespective of Nix) | 21:41:06 |
| Sergei Zimmerman (xokdvium) | Yes. It's best consumed via CMake, though it's weird | 21:42:41 |
| emily | oh, probably the issue is that you're depending on nix. | 21:45:27 |
| emily | rather than the correct component package. | 21:45:31 |
| emily | because of the split build. | 21:45:33 |
| emily | I guess it's a bug in the combined package. | 21:45:42 |
| Sergei Zimmerman (xokdvium) | Yeah, that stuff is going away soon either way | 21:50:07 |
| 18 Aug 2025 |
| fzakaria | Here is another "oddity" of the separate SOs.
I want to just pull in nix-store but it complains:
The program must call nix::initNix()
That only exists in nix-main :(
| 03:33:09 |
