<h2><a name="download" id="download"></a>Obtaining OpenWrt Buildroot</h2>
<p>OpenWrt Buildroot is available via CVS - Concurrent Version System.
- For any kind of development you should get the latest version from cvs via:</p>
+ For any kind of OpenWrt development you should get the latest version from cvs via:</p>
<pre>
$ cvs -d:pserver:anonymous@openwrt.org:/openwrt co openwrt
</pre>
+ <p>If you only like to create your own custom firmware images and pakages we
+ strongely suggest to use the CVS branch of the stable version (whiterussian):
+ </p>
+<pre>
+ $ cvs -d:pserver:anonymous@openwrt.org:/openwrt co -rwhiterussian openwrt
+</pre>
+
<h2><a name="using" id="using"></a>Using OpenWrt Buildroot</h2>
<h2><a name="custom_targetfs" id="custom_targetfs"></a>Customizing the
target filesystem</h2>
- <p>There are two ways to customize the resulting target filesystem:</p>
-
- <ul>
- <li>Customize the target filesystem directly, and rebuild the image. The
- target filesystem is available under <code>build_ARCH/root/</code> where
- <code>ARCH</code> is the chosen target architecture, usually mipsel.
- You can simply make your changes here, and run make target_install afterwards,
- 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>target/default/target_skeleton/</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>
+ <li>You can customize the target filesystem skeleton, available under
+ <code>package/base-files/default/</code>. You can change
+ 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 />
<h2><a name="custom_busybox" id="custom_busybox"></a>Customizing the
Busybox configuration</h2>
18
19 $(eval $(call PKG_template,FOO,foo,$(PKG_VERSION)-$(PKG_RELEASE),$(ARCH)))
20
- 21 $(PKG_BUILD_DIR)/.configured: $(PKG_BUILD_DIR)/.prepared
+ 21 $(PKG_BUILD_DIR)/.configured:
22 (cd $(PKG_BUILD_DIR); \
23 $(TARGET_CONFIGURE_OPTS) \
24 CFLAGS="$(TARGET_CFLAGS)" \
recursevily strip all binaries and libraries.
Finally <code>IPKG_BUILD</code> is called to create the package.</p>
+ <p>If you want other targets to be executed at <code>compile</code>,
+ <code>install</code> or <code>clean</code> time (e.g. for installing
+ a library into the staging dir), just create the targets (usually
+ <code>install-dev</code> and <code>uninstall-dev</code>) and enable
+ them like this:
+<pre>
+compile-targets: install-dev
+clean-targets: uninstall-dev
+</pre>
+
<h3>Conclusion</h3>
<p>As you can see, adding a software to buildroot is simply a
<p>If you package software that might be useful for other persons,
don't forget to send a patch to OpenWrt developers!
- Use the mail address: patches@openwrt.org
+ Use the mail address: openwrt-devel@openwrt.org
</p>
<h2><a name="links" id="links"></a>Resources</h2>
- <p>To learn more about OpenWrt you can visit this website:
+ <p>To learn more about OpenWrt, you can visit this website:
<a href="http://openwrt.org/">http://openwrt.org/</a></p>
</div>
projects / openwrt.git / blobdiff