X-Git-Url: https://git.rohieb.name/openwrt.git/blobdiff_plain/66492b44df29654379584aac27a0d0c84b26cade..6cfdb8f029c806124d150e1d3d21bfe60f0d73fc:/openwrt/docs/buildroot-documentation.html?ds=sidebyside diff --git a/openwrt/docs/buildroot-documentation.html b/openwrt/docs/buildroot-documentation.html index 92e378398..ede3796a6 100644 --- a/openwrt/docs/buildroot-documentation.html +++ b/openwrt/docs/buildroot-documentation.html @@ -101,7 +101,7 @@ $ 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 VS branch of the stable version (whiterussian) + strongely suggest to use the CVS branch of the stable version (whiterussian):

  $ cvs -d:pserver:anonymous@openwrt.org:/openwrt co -rwhiterussian openwrt
@@ -156,25 +156,13 @@
     

Customizing the target filesystem

-

There are two ways to customize the resulting target filesystem:

- - +
  • You can customize the target filesystem skeleton, available under + 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.

    Customizing the Busybox configuration

    @@ -490,7 +478,7 @@ foo-compile: bar-compile 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)" \ @@ -599,6 +587,16 @@ foo-compile: bar-compile recursevily strip all binaries and libraries. Finally 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
    +
    +

    Conclusion

    As you can see, adding a software to buildroot is simply a @@ -613,7 +611,7 @@ foo-compile: bar-compile

    Resources

    -

    To learn more about OpenWrt you can visit this website: +

    To learn more about OpenWrt, you can visit this website: http://openwrt.org/