From mboxrd@z Thu Jan 1 00:00:00 1970 From: Bernhard Fischer Date: Thu, 12 Jul 2007 17:07:54 +0200 Subject: [Buildroot] svn commit: trunk/buildroot/docs In-Reply-To: <20070712144345.D4FC5A6827@busybox.net> References: <20070712144345.D4FC5A6827@busybox.net> Message-ID: <20070712150754.GA23938@aon.at> List-Id: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: buildroot@busybox.net On Thu, Jul 12, 2007 at 07:43:45AM -0700, ulf at uclibc.org wrote: >Author: ulf >Date: 2007-07-12 07:43:44 -0700 (Thu, 12 Jul 2007) >New Revision: 19071 > >Log: >Update Documentation for BSP patch > >Modified: > trunk/buildroot/docs/buildroot.html > > >@@ -160,7 +165,7 @@ > be named root_fs_ARCH.EXT where ARCH is your > architecture and EXT depends on the type of target filesystem > selected in the Target options section of the configuration >- tool.

>+ tool.The file is stored in the "binaries/$(PROJECT)/" directory

whitespace damaged (missing space after punctuation) > >

If you intend to do an offline-build and just want to download all > sources that you previously selected in "make menuconfig" then >@@ -224,9 +229,13 @@ > it should be changed. These main directories are in an tarball inside of > inside the skeleton because it contains symlinks that would be broken > otherwise.
>- These customizations are deployed into build_ARCH/root/ just >+ These customizations are deployed into project_build_ARCH/root/ just overlong line. > before the actual image is made. So simply rebuilding the image by running > make should propogate any new changes to the image. >+ >+

  • When configuring the build system, using make menuconfig, you overlong line. >+ can specify the contents of the /etc/hostname and /etc/issue >+ (the welcome banner) in the PROJECT section
    • > > >

    Customizing the >@@ -349,10 +358,30 @@ > tarballs are in this directory because it may be useful to save them > somewhere to avoid further downloads. > overlong line everywhere below >-
  • Create the build directory (build_ARCH/ by default, >+
  • Create the shared build directory (build_ARCH/ by default, > where ARCH is your architecture). This is where all >- user-space tools while be compiled.
    • >+ non configurable user-space tools will be compiled.When building two or more whitespace damaged (missing space after punctuation) >+ targets using the same architecture, the first build will go through the full >+ download, configure, make process, but the second and later builds will only >+ copy the result from the first build to its project specific target directory >+ significantly speeding up the build process > >+
  • Create the project specific build directory >+ (project_build_ARCH/$(PROJECT) by default, where ARCH >+ is your architecture). This is where all configurable user-space tools will be >+ compiled. The project specific build directory is neccessary, if two different I don't think that comma before if is correct.. and you ment to type necessary with just one 'c'. >+ targets needs to use a specific package, but the packages have different >+ configuration for both targets. Some examples of packages built in this directory >+ are busybox and linux. >+
    • >+ >+
  • Create the project specific result directory >+ (binaries/$(PROJECT) by default, where ARCH >+ is your architecture). This is where the root file system images are stored, it is 'filesystem' without a space. >+ It is also used to store the linux kernel image and any utilities, boot-loaders >+ etc. needed for a target. >+
    • >+ >
  • Create the toolchain build directory > (toolchain_build_ARCH/ by default, where ARCH > is your architecture). This is where the cross compilation toolchain will >@@ -367,7 +396,7 @@ > setup this staging directory, it first removes it, and then it creates > various subdirectories and symlinks inside it.
    • > >-
  • Create the target directory (build_ARCH/root/ by >+
  • Create the target directory (project_build_ARCH/root/ by > default) and the target filesystem skeleton. This directory will contain > the final root filesystem. To setup it up, it first deletes it, then it > uncompress the target/generic/skel.tar.gz file to create the Please make sure that at least the source of the documentation can be edited on a 80x24 console without too much pain, TIA.