Changeset 2860


Ignore:
Timestamp:
2006-01-08T03:17:18+01:00 (12 years ago)
Author:
wbx
Message:

fix documentation, fixes #176

File:
1 edited

Legend:

Unmodified
Added
Removed
  • trunk/openwrt/docs/buildroot-documentation.html

    r2226 r2860  
    9696    <h2><a name="download" id="download"></a>Obtaining OpenWrt Buildroot</h2> 
    9797 
    98     <p>OpenWrt Buildroot is available via CVS - Concurrent Version System. 
    99     For any kind of OpenWrt development you should get the latest version from cvs via:</p> 
    100 <pre> 
    101  $ cvs -d:pserver:anonymous@openwrt.org:/openwrt co openwrt 
    102 </pre> 
    103     <p>If you only like to create your own custom firmware images and pakages we 
    104      strongely suggest to use the CVS branch of the stable version (whiterussian): 
     98    <p>OpenWrt Buildroot is available via SVN aka subversion. 
     99    For any kind of OpenWrt development you should get the latest version from svn via:</p> 
     100<pre> 
     101 $ svn co https://svn.openwrt.org/openwrt/trunk/ 
     102</pre> 
     103    <p>If you only like to create your own custom firmware images and packages we 
     104     strongly suggest to use the SVN branch of the stable version (whiterussian): 
    105105    </p> 
    106106<pre> 
    107  $ cvs -d:pserver:anonymous@openwrt.org:/openwrt co -rwhiterussian openwrt 
     107 $ svn co https://svn.openwrt.org/openwrt/branches/whiterussian/ 
    108108</pre> 
    109109  
     
    157157    target filesystem</h2> 
    158158 
    159     <li>You can customize the target filesystem skeleton, available under 
    160     <code>package/base-files/default/</code>. You can change 
    161     configuration files or other stuff here. However, the full file hierarchy 
    162     is not yet present, because it's created during the compilation process. 
    163     So you can't do everything on this target filesystem skeleton, but 
    164     changes to it remains even when you completely rebuild the cross-compilation 
    165     toolchain and the tools.<br /> 
     159    <p>There are two ways to customize the resulting target filesystem:</p> 
     160 
     161    <ul> 
     162      <li>Customize the target filesystem directly, and rebuild the image. The 
     163      target filesystem is available under <code>build_ARCH/root/</code> where 
     164      <code>ARCH</code> is the chosen target architecture, usually mipsel. 
     165      You can simply make your changes here, and run make target_install afterwards,  
     166      which will rebuild the target filesystem image. This method allows to do 
     167      everything on the target filesystem, but if you decide to rebuild your toolchain, 
     168      tools or packages, these changes will be lost.</li> 
     169 
     170      <li>Customize the target filesystem skeleton, available under 
     171      <code>package/base-files/default/</code>. You can customize 
     172      configuration files or other stuff here. However, the full file hierarchy 
     173      is not yet present, because it's created during the compilation process. 
     174      So you can't do everything on this target filesystem skeleton, but 
     175      changes to it remains even when you completely rebuild the cross-compilation 
     176      toolchain and the tools.<br /> 
     177    </ul> 
    166178 
    167179    <h2><a name="custom_busybox" id="custom_busybox"></a>Customizing the 
     
    284296      the final root filesystem. To set it up, it first deletes it, then it 
    285297      copies the skeleton available in  <code>target/default/target_skeleton</code> 
    286       and then removes useless <code>CVS/</code> directories.</li> 
     298      and then removes useless <code>SVN/</code> directories.</li> 
    287299 
    288300      <li>Call the <code>prepare</code>, <code>compile</code> and <code>install</code> 
     
    479491    19  $(eval $(call PKG_template,FOO,foo,$(PKG_VERSION)-$(PKG_RELEASE),$(ARCH))) 
    480492    20 
    481     21  $(PKG_BUILD_DIR)/.configured: 
     493    21  $(PKG_BUILD_DIR)/.configured: $(PKG_BUILD_DIR)/.prepared 
    482494    22          (cd $(PKG_BUILD_DIR); \ 
    483495    23                  $(TARGET_CONFIGURE_OPTS) \ 
     
    588600    Finally <code>IPKG_BUILD</code> is called to create the package.</p> 
    589601 
    590         <p>If you want other targets to be executed at <code>compile</code>, 
    591         <code>install</code> or <code>clean</code> time (e.g. for installing 
    592         a library into the staging dir), just create the targets (usually  
    593         <code>install-dev</code> and <code>uninstall-dev</code>) and enable 
    594         them like this: 
    595 <pre> 
    596 compile-targets: install-dev 
    597 clean-targets: uninstall-dev 
    598 </pre> 
    599          
    600602    <h3>Conclusion</h3> 
    601603 
     
    612614     <h2><a name="links" id="links"></a>Resources</h2> 
    613615 
    614     <p>To learn more about OpenWrt, you can visit this website:  
     616    <p>To learn more about OpenWrt you can visit this website:  
    615617     <a href="http://openwrt.org/">http://openwrt.org/</a></p> 
    616618 
Note: See TracChangeset for help on using the changeset viewer.