public/nixpkgs
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

rewrite a bit, add some clarifications

Browse Source 
svn path=/nixpkgs/trunk/; revision=4343
This commit is contained in:
Armijn Hemel 2005-12-06 18:08:57 +00:00
parent 5138d6dc10
commit 3da5ecfe05
1 changed files with 11 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

14
maintainers/docs/cross.txt
View File

@ -131,6 +131,12 @@ Only C is used, because for other languages (such as C++) extra libraries
need to be compiled, for which libraries compiled for the target system need to be compiled, for which libraries compiled for the target system
are needed. are needed.
There is a bit of evilness going on. The cross compiled utilities need
to be either copied to or be linked from the output tree of the compiler.
(Is this really true? Back this up with arguments! -- AH)
Symbolic links are not something we want inside the Nix store.
--- ---
{ stdenv, fetchurl, noSysDirs { stdenv, fetchurl, noSysDirs
, langC ? true, langCC ? true, langF77 ? false , langC ? true, langCC ? true, langF77 ? false
@ -260,6 +266,8 @@ postInstall() {
genericBuild genericBuild
--- ---
This is enough to compile a C library. In our case we take uClibc. It's Step 4: build a C library for the target platform.
intended to be a small sized replacement for glibc. It is widely used in
embedded environments. The previous steps are enough to compile a C library. In our case we take
uClibc. It's intended to be a small sized replacement for glibc. It is widely
used in embedded environments.