diff options
author | Armijn Hemel <armijn@gpl-violations.org> | 2005-12-31 16:12:04 +0000 |
---|---|---|
committer | Armijn Hemel <armijn@gpl-violations.org> | 2005-12-31 16:12:04 +0000 |
commit | a4a9e5aea62273b20215425a3efd67afd944e2d5 (patch) | |
tree | 7357688857ec0e66bfb3178b8a8bad11a61e1e47 /maintainers | |
parent | 560a2d3c1093d54cd7c2d82eb462bb3a539c4d60 (diff) |
small howto of adding new targets for uClibc cross compiling. For some
reasons sparc-linux fails, need to look into that...but hey, this is fun. Requests anyone? :) svn path=/nixpkgs/trunk/; revision=4469
Diffstat (limited to 'maintainers')
-rw-r--r-- | maintainers/docs/uclibc-cross.txt | 27 |
1 files changed, 27 insertions, 0 deletions
diff --git a/maintainers/docs/uclibc-cross.txt b/maintainers/docs/uclibc-cross.txt new file mode 100644 index 0000000000000..c32a95eb2b254 --- /dev/null +++ b/maintainers/docs/uclibc-cross.txt @@ -0,0 +1,27 @@ +Adding uClibc support for a new platform + +Sometimes you want to cross-compile to another architecture, for example an +embedded devices. For embedded devices the uClibc C library is popular. +In Nixpkgs there is support for uClibc for several architectures but not +everything is supported. + +Adding support is not very difficult, + +* Add your architecture to the buildfiles in +$nixpkgs/development/tools/misc/binutils-cross + +* Add your architecture to the buildfiles in +$nixpkgs/development/compilers/gcc-4.0-cross + +* Add your architecture to the buildfiles in +$nixpkgs/os-specific/linux/kernel-headers-cross + +* Add your architecture to the buildfiles in +$nixpkgs/development/uclibc + +In the latter directory you will also need a configuration file for uClibc. +You can make these by unpacking the uClibc sources and run a "make menuconfig". +In the configuration a few things need to be adapted: + +- kernel sources -> need to point at our own kernel headers +- install -> needs to point at $out |