KumiSystems/openwrtv3
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity

remove deprecated customization method from buildroot documentation

Browse source 
SVN-Revision: 2218
This commit is contained in:
Felix Fietkau 2005-10-21 21:40:14 +00:00
parent 3da601a8ea
commit 7230c23552
1 changed files with 7 additions and 19 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

26
openwrt/docs/buildroot-documentation.html
View file

@ -156,25 +156,13 @@
<h2><a name="custom_targetfs" id="custom_targetfs"></a>Customizing the <h2><a name="custom_targetfs" id="custom_targetfs"></a>Customizing the
target filesystem</h2> target filesystem</h2>
<p>There are two ways to customize the resulting target filesystem:</p> <li>You can customize the target filesystem skeleton, available under
<code>package/base-files/default/</code>. You can change
<ul> configuration files or other stuff here. However, the full file hierarchy
<li>Customize the target filesystem directly, and rebuild the image. The is not yet present, because it's created during the compilation process.
target filesystem is available under <code>build_ARCH/root/</code> where So you can't do everything on this target filesystem skeleton, but
<code>ARCH</code> is the chosen target architecture, usually mipsel. changes to it remains even when you completely rebuild the cross-compilation
You can simply make your changes here, and run make target_install afterwards, toolchain and the tools.<br />
which will rebuild the target filesystem image. This method allows to do
everything on the target filesystem, but if you decide to rebuild your toolchain,
tools or packages, these changes will be lost.</li>
<li>Customize the target filesystem skeleton, available under
<code>package/base-files/default/</code>. You can customize
configuration files or other stuff here. However, the full file hierarchy
is not yet present, because it's created during the compilation process.
So you can't do everything on this target filesystem skeleton, but
changes to it remains even when you completely rebuild the cross-compilation
toolchain and the tools.<br />
</ul>
<h2><a name="custom_busybox" id="custom_busybox"></a>Customizing the <h2><a name="custom_busybox" id="custom_busybox"></a>Customizing the
Busybox configuration</h2> Busybox configuration</h2>