Lines Matching refs:package

6 [[meson-package-tutorial]]
8 ==== +meson-package+ tutorial
15 Let's see how to write a +.mk+ file for a Meson-based package, with an example:
40 23: $(eval $(meson-package))
43 The Makefile starts with the definition of the standard variables for package
46 On line line 23, we invoke the +meson-package+ macro that generates all the
47 Makefile rules that actually allows the package to be built.
51 `pkg-config` to determine the compilation flags and libraries of package +bar+.
54 variable of a package, since this basic dependency is automatically added as
55 needed by the Meson package infrastructure.
57 If the "baz" package is selected, then support for the "baz" feature in "foo" is
59 the +meson_options.txt+ file in "foo" source tree. The "baz" package is also
61 disabled at line 20, if the package is not selected.
63 To sum it up, to add a new meson-based package, the Makefile example can be
65 uppercase name of the new package and update the values of the standard
68 [[meson-package-reference]]
70 ==== +meson-package+ reference
72 The main macro of the Meson package infrastructure is +meson-package+. It is
73 similar to the +generic-package+ macro. The ability to have target and host
74 packages is also available, with the +host-meson-package+ macro.
77 a number of variables before calling the +meson-package+ macro.
79 First, all the package metadata information variables that exist in the generic
89   package that contains the main meson.build file. This is useful,
100 * +FOO_CFLAGS+, to specify compiler arguments added to the package specific
104 * +FOO_CXXFLAGS+, to specify compiler arguments added to the package specific
108 * +FOO_LDFLAGS+, to specify compiler arguments added to the package specific