2
1

prerequisite.adoc 2.7 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103
  1. // -*- mode:doc; -*-
  2. // vim: set syntax=asciidoc:
  3. [[requirement]]
  4. == System requirements
  5. Buildroot is designed to run on Linux systems.
  6. While Buildroot itself will build most host packages it needs for the
  7. compilation, certain standard Linux utilities are expected to be
  8. already installed on the host system. Below you will find an overview of
  9. the mandatory and optional packages (note that package names may vary
  10. between distributions).
  11. [[requirement-mandatory]]
  12. === Mandatory packages
  13. * Build tools:
  14. ** +which+
  15. ** +sed+
  16. ** +make+ (version 3.81 or any later)
  17. ** +binutils+
  18. ** +build-essential+ (only for Debian based systems)
  19. ** +diffutils+
  20. ** +gcc+ (version 4.8 or any later)
  21. ** `g++` (version 4.8 or any later)
  22. ** +bash+
  23. ** +patch+
  24. ** +gzip+
  25. ** +bzip2+
  26. ** +perl+ (version 5.8.7 or any later)
  27. ** +tar+
  28. ** +cpio+
  29. ** +unzip+
  30. ** +rsync+
  31. ** +file+ (must be in +/usr/bin/file+)
  32. ** +bc+
  33. ** +findutils+
  34. ** +awk+
  35. * Source fetching tools:
  36. ** +wget+
  37. [[requirement-optional]]
  38. === Optional packages
  39. * Recommended dependencies:
  40. +
  41. Some features or utilities in Buildroot, like the legal-info, or the
  42. graph generation tools, have additional dependencies. Although they
  43. are not mandatory for a simple build, they are still highly recommended:
  44. +
  45. ** +python+ (version 2.7 or any later)
  46. * Configuration interface dependencies:
  47. +
  48. For these libraries, you need to install both runtime and development
  49. data, which in many distributions are packaged separately. The
  50. development packages typically have a _-dev_ or _-devel_ suffix.
  51. +
  52. ** +ncurses5+ to use the 'menuconfig' interface
  53. ** +qt5+ to use the 'xconfig' interface
  54. ** +glib2+, +gtk2+ and +glade2+ to use the 'gconfig' interface
  55. * Source fetching tools:
  56. +
  57. In the official tree, most of the package sources are retrieved using
  58. +wget+ from _ftp_, _http_ or _https_ locations. A few packages are only
  59. available through a version control system. Moreover, Buildroot is
  60. capable of downloading sources via other tools, like +git+ or +scp+
  61. (refer to xref:download-infra[] for more details). If you enable
  62. packages using any of these methods, you will need to install the
  63. corresponding tool on the host system:
  64. +
  65. ** +bazaar+
  66. ** +curl+
  67. ** +cvs+
  68. ** +git+
  69. ** +mercurial+
  70. ** +scp+
  71. ** +sftp+
  72. ** +subversion+
  73. * Java-related packages, if the Java Classpath needs to be built for
  74. the target system:
  75. ** The +javac+ compiler
  76. ** The +jar+ tool
  77. * Documentation generation tools:
  78. ** +asciidoc+, version 8.6.3 or higher
  79. ** +w3m+
  80. ** +python+ with the +argparse+ module (automatically present in 2.7+ and 3.2+)
  81. ** +dblatex+ (required for the pdf manual only)
  82. * Graph generation tools:
  83. ** +graphviz+ to use 'graph-depends' and '<pkg>-graph-depends'
  84. ** +python-matplotlib+ to use 'graph-build'
  85. * Package statistics tools ('pkg-stats'):
  86. ** +python-aiohttp+