1
0

using.txt 4.5 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109
  1. // -*- mode:doc; -*-
  2. // vim: set syntax=asciidoc:
  3. Using OpenADK
  4. -------------
  5. OpenADK has a nice configuration tool similar to the one you can
  6. find in the http://www.kernel.org/[Linux kernel] or in
  7. http://www.busybox.net/[Busybox]. Note that you can *and should build
  8. everything as a normal user*. There is no need to be root to configure
  9. and use OpenADK. The first step is to run the configuration
  10. assistant:
  11. --------------------
  12. $ make menuconfig
  13. --------------------
  14. For each menu entry in the configuration tool, you can find associated
  15. help that describes the purpose of the entry.
  16. image::openadk-appliance.png[]
  17. First of all you need to choose a new or predefined appliance.
  18. This is a collection of different packages and configuration options
  19. for specific appliance.
  20. image::openadk-target.png[]
  21. After that you can choose your target architecture, your target system and
  22. other general stuff. Then you can select individual packages and kernel
  23. settings. When you are ready exit and save. You can always redefine the
  24. configuration using +make menuconfig+.
  25. Once everything is configured, the configuration tool generates a
  26. +.config+ file that contains the description of your configuration. It
  27. will be used by the Makefiles to do what's needed.
  28. Let's go:
  29. --------------------
  30. $ make
  31. --------------------
  32. You *should never* use +make -jN+ with OpenADK: it does not support 'top-level
  33. parallel make'. Instead, use the +ADK_MAKE_JOBS+ option in +Global settings+ to
  34. tell OpenADK to run each package compilation with +make -jN+.
  35. The `make` command will generally perform the following steps:
  36. * download source files
  37. * configure, build and install required host tools
  38. * configure, build and install the cross-compiling toolchain
  39. * build a kernel image, if selected
  40. * build/install selected target packages
  41. * build a bootloader, if selected
  42. * create a root filesystem in selected format
  43. OpenADK output is stored in several subdirectories:
  44. * +firmware/+ where all the images and packages are stored.
  45. * +build_<system>_<libc>_<arch>_<abi>/+ where all the components except for the
  46. cross-compilation toolchain are built. The directory contains one
  47. subdirectory for each of these components.
  48. * +target_<system>_<libc>_<arch>_<abi>/+ which contains a hierarchy similar to a root filesystem
  49. hierarchy. This directory contains the installation of the
  50. cross-compilation toolchain and all the userspace packages selected
  51. for the target. However, this directory is 'not' intended to be
  52. the root filesystem for the target: it contains a lot of development
  53. files, unstripped binaries and libraries that make it far too big
  54. for an embedded system. These development files are used to compile
  55. libraries and applications for the target that depend on other
  56. libraries.
  57. * +root_<system>_<libc>_<arch>_<abi>/+ which contains the complete root filesystem for
  58. the target. One exception, it doesn't have the correct
  59. permissions (e.g. setuid for the busybox binary) for some files.
  60. Therefore, this directory *should not be used on your target*.
  61. Instead, you should use one of the images or archives built in the
  62. +firmware/+ directory. If you need an
  63. extracted image of the root filesystem for booting over NFS, then
  64. use the tarball image generated in +firmware/+ and extract it as
  65. root. Compared to +build_*/+, +target_*/+ contains only the files and
  66. libraries needed to run the selected target applications: the
  67. development files are (exception: if any dev packages are selected)
  68. not present, the binaries are stripped.
  69. * +host_<gnu_host_name>/+ contains the installation of tools compiled for the host
  70. that are needed for the proper execution of OpenADK
  71. * +host_build_<gnu_host_name>/+ contains the build directories of tools compiled for the host
  72. that are needed for the proper execution of OpenADK
  73. * +toolchain_<system>_<libc>_<arch>_<abi>>/+ contains just the cross-compilation toolchain.
  74. Can be used together with +target_<system>_<libc>_<arch>_<abi>/+ for other projects. Toolchain
  75. is relocatable.
  76. * +toolchain_build_<system>_<libc>_<arch>_<abi>/+ contains the build directories for the various
  77. components of the cross-compilation toolchain.
  78. * +pkg_<system>_<libc>_<arch>_<abi>/+ contains stamp files and file lists for the various components.
  79. The command, +make menuconfig+ and +make+, are the
  80. basic ones that allow to easily and quickly generate images fitting
  81. your needs, with all the supports and applications you enabled.
  82. More details about the "make" command usage are given in
  83. xref:make-tips[].