| 27 Dec 2025 |
emily | does the log change at all? e.g. the line cargo:warning=Building with: CC | 23:57:39 |
emily | oh to be clear cmake needs to be provided to the aws-lc-sys derivation | 23:57:52 |
emily | not any Snix one | 23:57:53 |
emily | so you'll need to define it in the crates overrides or etc. | 23:57:59 |
emily | (because crate2nix splits up crate builds) | 23:58:10 |
flokli | yes, that's what I did | 23:58:12 |
flokli | https://paste.linuxlounge.net/RE | 23:59:23 |
| 28 Dec 2025 |
flokli | https://paste.linuxlounge.net/LE <- new build log with cmake | 00:00:19 |
flokli | (I really need to fix my workflow, being able to ssh to this machine) | 00:00:32 |
emily | can you try setting AWS_LC_SYS_CMAKE_BUILDER in the environment variables? | 00:03:16 |
flokli | it seems to build! | 00:05:08 |
flokli | nice, ty | 00:05:10 |
flokli | I'll open up a CL as well as a PR to nixpkgs | 00:05:18 |
flokli | Are we ok with using cmake unconditionally on all platforms? | 00:06:05 |
emily | fwiw aws-lc say that environment variable isn't officially supported, they have some baroque conditionals in build.rs that determine when to use CMake | 00:06:18 |
emily | I guess somehow you are tripping them differently to how the packages we have in-tree do | 00:06:33 |
flokli | :) | 00:06:43 |
emily | I don't see why not. crate2nix isn't used in-tree anyway | 00:07:10 |
emily | though ideally we should figure out why it's behaving differently in that context | 00:07:20 |
flokli | mmm | 00:08:04 |
flokli | I... don | 00:08:14 |
flokli | * | 00:08:25 |
emily | it'll at least be noticeable if they stop supporting the env variable, so it's probably fine to just set it by default in the crate overrides | 00:09:28 |
emily | though I'd be very curious to know if this happens with buildRustPackage | 00:09:39 |
flokli | can you try building spotifyd on Darwin? | 00:10:44 |
emily | https://hydra.nixos.org/build/316981809 | 00:11:30 |
| * flokli hmms more | 00:11:45 |
emily | perhaps different Cargo features; or perhaps bindgenHook really is doing something; or perhaps buildRustPackage is behaving differently to buildRustCrate here (they are basically entirely separate IIRC) | 00:12:16 |
emily | like ultimately crate2nix isn't using Cargo to drive the build | 00:13:23 |
emily | so there's all sorts of potential differences wrt feature resolution etc. | 00:13:28 |