Search results

Jump to: navigation, search

Page title matches

  • Quick example to cross compile a package: [[Cheatsheet#Cross-compile_packages]]. == Cross-Compiling a package in nixpkgs ==
    6 KB (781 words) - 10:56, 6 April 2024

Page text matches

  • ==== Cross-compiling ====
    1 KB (173 words) - 19:15, 6 August 2024
  • Quick example to cross compile a package: [[Cheatsheet#Cross-compile_packages]]. == Cross-Compiling a package in nixpkgs ==
    6 KB (781 words) - 10:56, 6 April 2024
  • ...ub.com/cyber-murmel/NixOS-on-ARM-Examples Examples of Nix expressions for cross compiling NixOS images for ARM]
    691 bytes (90 words) - 11:07, 6 April 2024
  • * [https://github.com/DavidEGrayson/nixcrpkgs Nixcrpkgs] Focused on cross-compiling
    764 bytes (109 words) - 10:54, 6 April 2024
  • Elvish is a cross-platform shell suitable for both interactive use and scripting. It features
    583 bytes (88 words) - 10:55, 6 April 2024
  • ==== Testing the cross-compilation of modules ====
    5 KB (554 words) - 11:04, 6 April 2024
  • ...tdated|Section refers to old user-provided images. Should be reviewed with cross-compilation, or native compilation through userspace emulation.}} ...support the Orange Pi One, it is not part of nixpkgs. However with the new cross-compiler toolchain added with nixpkgs-18.09 it is straight forward to build
    3 KB (388 words) - 19:10, 6 August 2024
  • This page presents a cross-section of well known "keywords" used in attribute sets in various componen
    948 bytes (138 words) - 11:09, 6 April 2024
  • == How to add a new cross-compilation target/platform? == ...re severely undocumented. The official manual only glances over how to use cross compilation for pre-existing platforms, but not how to define new platforms
    6 KB (1,043 words) - 10:54, 6 April 2024
  • ...tdated|Section refers to old user-provided images. Should be reviewed with cross-compilation, or native compilation through userspace emulation.}}
    1 KB (162 words) - 19:10, 6 August 2024
  • ...tdated|Section refers to old user-provided images. Should be reviewed with cross-compilation, or native compilation through userspace emulation.}}
    1 KB (182 words) - 19:09, 6 August 2024
  • #* If you are cross compiling, the script will not run as it'll try to use ARMv7 binaries, but # If you cross compiled the boot loader, U-Boot will try to load an incorrect device tree
    3 KB (517 words) - 19:08, 6 August 2024
  • ...top environment developed in the Rust programming language, using the iced cross platform GUI library for Rust, and Smithay as building blocks for its compo
    2 KB (243 words) - 12:03, 9 October 2024
  • ...tdated|Section refers to old user-provided images. Should be reviewed with cross-compilation, or native compilation through userspace emulation.}}
    2 KB (217 words) - 19:16, 6 August 2024
  • == cross env == ...e! However, the distinction becomes of practical importance if one wants a cross compilation development environment. In that case one would begin file with
    9 KB (1,300 words) - 10:57, 6 April 2024
  • ...tdated|Section refers to old user-provided images. Should be reviewed with cross-compilation, or native compilation through userspace emulation.}}
    2 KB (301 words) - 19:14, 6 August 2024
  • ...that those repositories can be used to build a system image either through cross-compilation or native aarch64-linux build, with the usual caveats.
    2 KB (347 words) - 19:12, 6 August 2024
  • ...tdated|Section refers to old user-provided images. Should be reviewed with cross-compilation, or native compilation through userspace emulation.}}
    2 KB (270 words) - 19:07, 6 August 2024
  • ...tdated|Section refers to old user-provided images. Should be reviewed with cross-compilation, or native compilation through userspace emulation.}}
    2 KB (303 words) - 19:10, 6 August 2024
  • == Cross-compiling == * [https://github.com/jraygauthier/jrg-rust-cross-experiment/tree/master/simple-static-rustup-target-windows simple-static-ru
    15 KB (2,024 words) - 22:08, 21 November 2024

View (previous 20 | next 20) (20 | 50 | 100 | 250 | 500)