| Commit message (Collapse) | Author | Age | |
|---|---|---|---|
| * | wasm: init cross target | Matthew Bauer | 2019-04-23 |
| | | | | | | | | | | Adds pkgsCross.wasm32 and pkgsCross.wasm64. Use it to build Nixpkgs with a WebAssembly toolchain. stdenv/cross: use static overlay on isWasm isWasm doesn’t make sense dynamically linked. | ||
| * | cross/tests: add llvm-based tests | Matthew Bauer | 2019-02-26 |
| | | |||
| * | llvm: support cross compilation with useLLVM flag | Matthew Bauer | 2019-02-26 |
| | | | | | | | | | | | | | You can build (partially) with LLVM toolchain using the useLLVM flag. This works like so: nix-build -A hello --arg crossSystem '{ system = "aarch64-unknown-linux-musl"; useLLVM = true }' also don’t separate debug info in lldClang It doesn’t work currently with that setup hook. Missing build-id? | ||
| * | treewide: add emulator to platform | Matthew Bauer | 2018-11-29 |
| | | | | | | | | | | | | | | | | | | You can use stdenv.hostPlatform.emulator to get an executable that runs cross-built binaries. This could be any emulator. For instance, we use QEMU to emulate Linux targets and Wine to emulate Windows targets. To work with qemu, we need to support custom targets. I’ve reworked the cross tests in pkgs/test/cross to use this functionality. Also, I’ve used talloc to cross-execute with the emulator. There appears to be a cross-execute for all waf builds. In the future, it would be nice to set this for all waf builds. Adds stdenv.hostPlatform.qemuArch attrbute to get the qemuArch for each platform. | ||
| * | tests: add some cross tests | Matthew Bauer | 2018-07-21 |