adding-packages-qmake.txt 2.9 KB

12345678910111213141516171819202122232425262728293031323334353637383940414243444546474849505152535455565758596061626364656667686970717273747576777879808182838485
  1. // -*- mode:doc; -*-
  2. // vim: set syntax=asciidoc:
  3. === Infrastructure for QMake-based packages
  4. [[qmake-package-tutorial]]
  5. ==== +qmake-package+ tutorial
  6. First, let's see how to write a +.mk+ file for a QMake-based package, with
  7. an example :
  8. ------------------------
  9. 01: ################################################################################
  10. 02: #
  11. 03: # libfoo
  12. 04: #
  13. 05: ################################################################################
  14. 06:
  15. 07: LIBFOO_VERSION = 1.0
  16. 08: LIBFOO_SOURCE = libfoo-$(LIBFOO_VERSION).tar.gz
  17. 09: LIBFOO_SITE = http://www.foosoftware.org/download
  18. 10: LIBFOO_CONF_OPTS = QT_CONFIG+=bar QT_CONFIG-=baz
  19. 11: LIBFOO_DEPENDENCIES = bar
  20. 12:
  21. 13: $(eval $(qmake-package))
  22. ------------------------
  23. On line 7, we declare the version of the package.
  24. On line 8 and 9, we declare the name of the tarball (xz-ed tarball
  25. recommended) and the location of the tarball on the Web. Buildroot
  26. will automatically download the tarball from this location.
  27. On line 10, we tell Buildroot what options to enable for libfoo.
  28. On line 11, we tell Buildroot the dependencies of libfoo.
  29. Finally, on line line 13, we invoke the +qmake-package+
  30. macro that generates all the Makefile rules that actually allows the
  31. package to be built.
  32. [[qmake-package-reference]]
  33. ==== +qmake-package+ reference
  34. The main macro of the QMake package infrastructure is +qmake-package+.
  35. It is similar to the +generic-package+ macro.
  36. Just like the generic infrastructure, the QMake infrastructure works
  37. by defining a number of variables before calling the +qmake-package+
  38. macro.
  39. First, all the package metadata information variables that exist in
  40. the generic infrastructure also exist in the QMake infrastructure:
  41. +LIBFOO_VERSION+, +LIBFOO_SOURCE+, +LIBFOO_PATCH+, +LIBFOO_SITE+,
  42. +LIBFOO_SUBDIR+, +LIBFOO_DEPENDENCIES+, +LIBFOO_INSTALL_STAGING+,
  43. +LIBFOO_INSTALL_TARGET+.
  44. An additional variable, specific to the QMake infrastructure, can
  45. also be defined.
  46. * +LIBFOO_CONF_ENV+, to specify additional environment variables to
  47. pass to the +qmake+ script for the configuration step. By default, empty.
  48. * +LIBFOO_CONF_OPTS+, to specify additional options to pass to the
  49. +qmake+ script for the configuration step. By default, empty.
  50. * +LIBFOO_MAKE_ENV+, to specify additional environment variables to the
  51. +make+ command during the build and install steps. By default, empty.
  52. * +LIBFOO_MAKE_OPTS+, to specify additional targets to pass to the
  53. +make+ command during the build step. By default, empty.
  54. * +LIBFOO_INSTALL_STAGING_OPTS+, to specify additional targets to pass
  55. to the +make+ command during the staging installation step. By default,
  56. +install+.
  57. * +LIBFOO_INSTALL_TARGET_OPTS+, to specify additional targets to pass
  58. to the +make+ command during the target installation step. By default,
  59. +install+.
  60. * +LIBFOO_SYNC_HEADERS+, to run syncqt.pl before qmake. Some packages
  61. need this to have a properly populated include directory before
  62. running the build.