prerequisite.txt 2.6 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596
  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. ** +gcc+ (version 4.8 or any later)
  20. ** `g++` (version 4.8 or any later)
  21. ** +bash+
  22. ** +patch+
  23. ** +gzip+
  24. ** +bzip2+
  25. ** +perl+ (version 5.8.7 or any later)
  26. ** +tar+
  27. ** +cpio+
  28. ** +unzip+
  29. ** +rsync+
  30. ** +file+ (must be in +/usr/bin/file+)
  31. ** +bc+
  32. * Source fetching tools:
  33. ** +wget+
  34. [[requirement-optional]]
  35. === Optional packages
  36. * Recommended dependencies:
  37. +
  38. Some features or utilities in Buildroot, like the legal-info, or the
  39. graph generation tools, have additional dependencies. Although they
  40. are not mandatory for a simple build, they are still highly recommended:
  41. +
  42. ** +python+ (version 2.7 or any later)
  43. * Configuration interface dependencies:
  44. +
  45. For these libraries, you need to install both runtime and development
  46. data, which in many distributions are packaged separately. The
  47. development packages typically have a _-dev_ or _-devel_ suffix.
  48. +
  49. ** +ncurses5+ to use the 'menuconfig' interface
  50. ** +qt5+ to use the 'xconfig' interface
  51. ** +glib2+, +gtk2+ and +glade2+ to use the 'gconfig' interface
  52. * Source fetching tools:
  53. +
  54. In the official tree, most of the package sources are retrieved using
  55. +wget+ from _ftp_, _http_ or _https_ locations. A few packages are only
  56. available through a version control system. Moreover, Buildroot is
  57. capable of downloading sources via other tools, like +rsync+ or +scp+
  58. (refer to xref:download-infra[] for more details). If you enable
  59. packages using any of these methods, you will need to install the
  60. corresponding tool on the host system:
  61. +
  62. ** +bazaar+
  63. ** +cvs+
  64. ** +git+
  65. ** +mercurial+
  66. ** +rsync+
  67. ** +scp+
  68. ** +subversion+
  69. * Java-related packages, if the Java Classpath needs to be built for
  70. the target system:
  71. ** The +javac+ compiler
  72. ** The +jar+ tool
  73. * Documentation generation tools:
  74. ** +asciidoc+, version 8.6.3 or higher
  75. ** +w3m+
  76. ** +python+ with the +argparse+ module (automatically present in 2.7+ and 3.2+)
  77. ** +dblatex+ (required for the pdf manual only)
  78. * Graph generation tools:
  79. ** +graphviz+ to use 'graph-depends' and '<pkg>-graph-depends'
  80. ** +python-matplotlib+ to use 'graph-build'