1
0

customize-rootfs.txt 1.1 KB

1234567891011121314151617181920212223242526272829
  1. // -*- mode:doc; -*-
  2. // vim: set syntax=asciidoc:
  3. [[rootfs-custom]]
  4. Customizing the generated target filesystem
  5. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
  6. Besides changing one or another configuration through +make menuconfig+,
  7. there is a way to customize the resulting target filesystem.
  8. Create a new directory called +extra+ in the top OpenADK directory.
  9. Put there a tree of directories and files that will be copied directly
  10. over the target filesystem (+root_*+) after everything is build, but
  11. before the firmware images or archives are created.
  12. You can also point to another directory via:
  13. ---------------
  14. $ make extra=/foo/bar
  15. ---------------
  16. You can start with the example configuration files from +root_*+.
  17. The +extra+ directory will never be deleted by any clean target to avoid
  18. loss of customized configuration data.
  19. Another option is to configure a post-build action. This is available
  20. in +Global settings+. It must point to a script relative to the root
  21. of your openadk working copy. It will be invoked as part of the
  22. +*-imageinstall+ step with $ADK_TOPDIR as first argument. You can use
  23. it e.g. to modify the +root_*+ filesystem before bundling it.