X-Git-Url: https://git.rohieb.name/openwrt.git/blobdiff_plain/89906e729b17d22a02c85f991aca111c0ffdd010..81d91695f5e0d00c532047579c456f9a276087ad:/openwrt/docs/buildroot-documentation.html diff --git a/openwrt/docs/buildroot-documentation.html b/openwrt/docs/buildroot-documentation.html index 9dd42c1c2..ede3796a6 100644 --- a/openwrt/docs/buildroot-documentation.html +++ b/openwrt/docs/buildroot-documentation.html @@ -96,10 +96,17 @@
OpenWrt Buildroot is available via CVS - Concurrent Version System. - For any kind of development you should get the latest version from cvs via:
+ For any kind of OpenWrt development you should get the latest version from cvs via:$ cvs -d:pserver:anonymous@openwrt.org:/openwrt co openwrt+
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): +
++ $ cvs -d:pserver:anonymous@openwrt.org:/openwrt co -rwhiterussian openwrt ++
There are two ways to customize the resulting target filesystem:
- -build_ARCH/root/
where
- ARCH
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.target/default/target_skeleton/
. 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.package/base-files/default/
. 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.IPKG_BUILD
is called to create the package.
+ If you want other targets to be executed at compile
,
+ install
or clean
time (e.g. for installing
+ a library into the staging dir), just create the targets (usually
+ install-dev
and uninstall-dev
) and enable
+ them like this:
+
+compile-targets: install-dev +clean-targets: uninstall-dev ++
As you can see, adding a software to buildroot is simply a @@ -606,7 +611,7 @@ foo-compile: bar-compile
To learn more about OpenWrt you can visit this website: +
To learn more about OpenWrt, you can visit this website: http://openwrt.org/