Nix Cross Compiling | 577 Members | |
| 127 Servers |
| Sender | Message | Time |
|---|---|---|
| 22 Aug 2025 | ||
| but... is it wrong? :) | 10:57:33 | |
| it seems like it's accessing earlier bootstrap stages in some cases, maybe. | 10:57:50 | |
targetPackages.stdenv is okay i think | 10:59:21 | |
| it's like the one package that's okay to get from targetPackages | 10:59:40 | |
| as of whether the mapping to ccFor* tbh idfk | 10:59:58 | |
| * as of whether the mapping to ccFor* is correct tbh idfk | 11:00:06 | |
| honestly I guess it's more likely one of these things
| 11:08:51 | |
since the hack that "fixes" it just involves overriding llvmPackages | 11:09:00 | |
so leaning more towards "llvmPackages wire-up is busted", as I've observed that myself | 11:09:14 | |
| 15:07:26 | ||
| 17:27:46 | ||
| 23 Aug 2025 | ||
Any tips on cross-compiling a package out-of-tree with a compiler that's also built out-of-tree? I was looking into mkScopeWithSplicing', but I'm not sure how to use it outside of the Nixpkgs repository.The concrete goal I'm trying to achieve is 1. compile a specific revision of LLVM that's used by Polygeist and 2. be able to use the clang compiler with the libc provided by that revision to cross-compile programs to another architecture. Any help is appreciated 🙏 | 22:37:19 | |
| 24 Aug 2025 | ||
| 04:10:44 | ||
| With overlays | 12:22:57 | |
| * With a overlay | 12:23:14 | |
| Then you can use mkScopeWithSplicing because the set will be available top-level | 12:24:03 | |
| * Then you can use makeScopeWithSplicing' because the set will be available top-level | 12:24:50 | |
| You don't necessarily need a scope | 12:28:13 | |
| Use overlays and callPackage to get deps, then you don't have to do anything non-cross specific unless the package itself needs something | 12:28:39 | |
| * Use overlays and callPackage to get deps, then you don't have to do anything cross specific unless the package itself needs something | 12:28:55 | |
| That's very helpful, thanks | 12:33:44 | |
| * Define your packages in an overlay and use callPackage in the overlay to get deps, then you don't have to do anything cross specific unless the package itself needs something | 12:34:05 | |
I think you can use it without an overlay if you use splice.nix right? | 12:56:45 | |
| splice.nix doesn't help with that | 12:59:48 | |
You can get otherSplices without an overlay if you use all the different callPackages yourself | 13:00:15 | |
it provides a generateSplicesForMkScope you can use with makeScopeWithSplicing' right? but I guess the problem is mixing in stuff from the main package set… | 13:00:19 | |
generateSplicesForMkScope gets from pkgsBuildBuild and so on | 13:00:39 | |
| 13:00:48 | |
| I really wish we could have generic builder functions for compiler scopes that can be used out-of-tree to produce correct cross results without an overlay | 13:00:50 | |
Used like this otherSplices = generateSplicesForMkScope "xfce"; | 13:01:58 | |