[gentoo-commits] gentoo commit in xml/htdocs/proj/en/base/embedded/handbook: cross-compiling-packages.xml

["Joshua Saddler (nightmorph)" <nightmorph@gentoo.org>]

nightmorph    09/09/23 20:54:59

  Modified:             cross-compiling-packages.xml
  Log:
  Don't use ACCEPT_KEYWORDS emerge foo to do stuff, just first put the package in p.keywords. also some GuideXML coding style changes, and clarify path where necessary

Revision  Changes    Path
1.7                  xml/htdocs/proj/en/base/embedded/handbook/cross-compiling-packages.xml

file : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/proj/en/base/embedded/handbook/cross-compiling-packages.xml?rev=1.7&view=markup
plain: http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/proj/en/base/embedded/handbook/cross-compiling-packages.xml?rev=1.7&content-type=text/plain
diff : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/proj/en/base/embedded/handbook/cross-compiling-packages.xml?r1=1.6&r2=1.7

Index: cross-compiling-packages.xml
===================================================================
RCS file: /var/cvsroot/gentoo/xml/htdocs/proj/en/base/embedded/handbook/cross-compiling-packages.xml,v
retrieving revision 1.6
retrieving revision 1.7
diff -u -r1.6 -r1.7
--- cross-compiling-packages.xml	14 Sep 2009 15:34:08 -0000	1.6
+++ cross-compiling-packages.xml	23 Sep 2009 20:54:58 -0000	1.7
@@ -1,7 +1,7 @@
 <?xml version='1.0' encoding='UTF-8'?>
 <!DOCTYPE sections SYSTEM "/dtd/book.dtd">
 
-<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/proj/en/base/embedded/handbook/cross-compiling-packages.xml,v 1.6 2009/09/14 15:34:08 solar Exp $ -->
+<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/proj/en/base/embedded/handbook/cross-compiling-packages.xml,v 1.7 2009/09/23 20:54:58 nightmorph Exp $ -->
 
 <sections>
 
@@ -9,8 +9,8 @@
 Leverage Portage as a cross-compiling package manager.
 </abstract>
 
-<version>0.2</version>
-<date>2008-05-10</date>
+<version>0.3</version>
+<date>2009-09-23</date>
 
 <section>
 <title>Variables</title>
@@ -35,11 +35,14 @@
  </tr>
  <tr>
   <ti>ROOT</ti>
-  <ti>The virtual / you are installing into</ti>
+  <ti>The virtual <path>/</path> you are installing into</ti>
  </tr>
  <tr>
   <ti>PORTAGE_CONFIGROOT</ti>
-  <ti>The virtual / portage can find its config files (like make.conf)</ti>
+  <ti>
+    The virtual <path>/</path> portage can find its config files (like
+    <path>make.conf</path>)
+  </ti>
  </tr>
 </table>
 
@@ -70,18 +73,18 @@
 sysroot as the include/library directories in this tree are already encoded
 into the gcc cross-compiler for searching.  You could use another directory
 and then add custom -I/-L paths to your CPPFLAGS/LDFLAGS, but this has
-historically proven to be problematic.  Yes it works most of the time, but
+historically proven to be problematic.  Yes, it works most of the time, but
 the corner cases are why this method is discouraged.  In the embedded handbook,
 we'll assume you're using the sysroot as your development ROOT.
 </p>
 
 <p>
-For your runtime system, you'll need a much slimmer/trimmed down setup.  The
+For your runtime system, you'll need a much slimmer/trimmed-down setup.  The
 files you remove from a normal installed package is why this tree is not
 suitable for compiling against.  If you build binary packages while installing
 into your sysroot, then you can use those binary packages in conjunction with
-the <c>INSTALL_MASK</c> variable to trim out most things.  See the make.conf(5)
-man page for more information.
+the <c>INSTALL_MASK</c> variable to trim out most things. See <c>man
+make.conf</c> for more information.
 </p>
 
 </body>
@@ -94,20 +97,21 @@
 <p>
 These are simple wrapper scripts that will setup the environment 
 variables to point to the right places for you to be able to cross 
-compile using emerge. PORTAGE_CONFIGROOT, ROOT both point to the 
+compile using emerge. PORTAGE_CONFIGROOT and ROOT both point to the 
 SYSROOT.
 </p>
 
 <pre caption="crossdev-wrappers">
-# <i>ACCEPT_KEYWORDS="~*" emerge crossdev-wrappers</i>
+# <i>echo sys-devel/crossdev-wrappers >> /etc/portage/package.keywords</i>
+# <i>emerge crossdev-wrappers</i>
 </pre>
 
 <p>
 We can use these tools for both installing into your development root 
 (sysroot) and into your runtime root.  For the latter, simply specify 
-by using the --root option. For example if you had merged via crossdev 
-an armv4tl-softfloat-linux-gnueabi toolchain you would then invoke the 
-command just like normal emerge. But using the ctarget prefix
+by using the <c>--root</c> option. For example if you had merged via crossdev 
+an <c>armv4tl-softfloat-linux-gnueabi</c> toolchain you would then invoke the 
+command just like normal emerge. But using the <c>ctarget</c> prefix:
 </p>
 
 <pre caption="CTARGET-emerge">
@@ -115,8 +119,8 @@
 </pre>
 
 <p>
-You may want to use the --root-deps=rdeps option
-to avoid the host dependencies from being pulled into the deptree.
+You may want to use the <c>--root-deps=rdeps</c> option to avoid the host
+dependencies from being pulled into the deptree.
 </p>
 
 <p>
@@ -139,17 +143,16 @@
 </pre>
 
 <p>
-Sometimes there are some additional tests we need override for 
-configure scripts. To do this the wrappers export a few variables to 
-force the test to get the answer it should. This will help prevent 
-bloat in packages which add local functions to workaround issues it 
-assumes your system has because it could not run the test. From time to 
-time you may find you need to add additional variables to these files 
-in <c>/usr/share/crossdev/include/site/</c> directory to get a package 
-to compile. To figure out the variable you need to add, it's often as 
-simple as greping the configure script for the autoconf variable and 
-adding it to the appropriate target file. This becomes obvious after the 
-first few times of doing it.
+Sometimes there are some additional tests we need override for configure
+scripts. To do this the wrappers export a few variables to force the test to get
+the answer it should. This will help prevent bloat in packages which add local
+functions to workaround issues it assumes your system has because it could not
+run the test. From time to time you may find you need to add additional
+variables to these files in <path>/usr/share/crossdev/include/site/</path> to
+get a package to compile. To figure out the variable you need to add, it's often
+as simple as greping the configure script for the autoconf variable and adding
+it to the appropriate target file. This becomes obvious after the first few
+times of doing it.
 </p>
 
 </body>