docs/manual/adding-packages-cmake.txt

1 // -*- mode:doc; -*-
4 === Infrastructure for CMake-based packages
6 [[cmake-package-tutorial]]
8 ==== +cmake-package+ tutorial
10 First, let's see how to write a +.mk+ file for a CMake-based package,
13 ------------------------
21 08: LIBFOO_SOURCE = libfoo-$(LIBFOO_VERSION).tar.gz
25 12: LIBFOO_CONF_OPTS = -DBUILD_DEMOS=ON
26 13: LIBFOO_DEPENDENCIES = libglib2 host-pkgconf
28 15: $(eval $(cmake-package))
29 ------------------------
33 On line 8 and 9, we declare the name of the tarball (xz-ed tarball recommended)
38 directory. The staging directory, located in +output/staging/+
39 is the directory where all the packages are installed, including their
41 staging directory, since usually, only libraries need to be installed in
42 the staging directory: their development files are needed to compile
48 target directory. This directory contains what will become the root
50 not necessary to install them in the target directory because they will
61 Finally, on line line 15, we invoke the +cmake-package+
65 [[cmake-package-reference]]
67 ==== +cmake-package+ reference
70 +cmake-package+. It is similar to the +generic-package+ macro. The ability to
72 +host-cmake-package+ macro.
75 by defining a number of variables before calling the +cmake-package+
99   set by the +cmake-package+ infrastructure; so it is normally not
112   directory.
130   install the package to the host directory. By default, the value
135   install the package to the staging directory. By default, the value
140   install the package to the target directory. By default, the value
147 for most CMake-based packages. However, when required, it is still
150 * By adding a post-operation hook (after extract, patch, configure,