diff options
author | John Ericson <Ericson2314@Yahoo.com> | 2017-02-06 18:13:02 -0500 |
---|---|---|
committer | John Ericson <Ericson2314@Yahoo.com> | 2017-04-23 14:01:12 -0400 |
commit | 863d79b36446bb2dbcc34d4f57c832ac2dc57f68 (patch) | |
tree | 76683d4a723783f27f64b7bdd73c6a9e107167e0 /doc/cross-compilation.xml | |
parent | d59e4fbb75e307fd1a0e98c44627f38bab504aeb (diff) |
top-level: Introduce targetPackages and a "double link fold"
Each bootstrapping stage ought to just depend on the previous stage, but poorly-written compilers break this elegence. This provides an easy-enough way to depend on the next stage: targetPackages. PLEASE DO NOT USE IT UNLESS YOU MUST! I'm hoping someday in a pleasant future I can revert this commit :)
Diffstat (limited to 'doc/cross-compilation.xml')
-rw-r--r-- | doc/cross-compilation.xml | 5 |
1 files changed, 5 insertions, 0 deletions
diff --git a/doc/cross-compilation.xml b/doc/cross-compilation.xml index 06a8919c2a19e..728616a9f2635 100644 --- a/doc/cross-compilation.xml +++ b/doc/cross-compilation.xml @@ -167,6 +167,11 @@ Because of this, a best-of-both-worlds solution is in the works with no splicing or explicit access of <varname>buildPackages</varname> needed. For now, feel free to use either method. </para> + <note><para> + There is also a "backlink" <varname>__targetPackages</varname>, yielding a package set whose <varname>buildPackages</varname> is the current package set. + This is a hack, though, to accommodate compilers with lousy build systems. + Please do not use this unless you are absolutely sure you are packaging such a compiler and there is no other way. + </para></note> </section> </section> |