File: 80-cmake.txt

package info (click to toggle)
debmake-doc 1.17-7
  • links: PTS, VCS
  • area: main
  • in suites: bookworm
  • size: 24,612 kB
  • sloc: makefile: 768; sh: 690; ansic: 114; python: 99; sed: 16
file content (89 lines) | stat: -rw-r--r-- 2,514 bytes parent folder | download
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
[[cmake-single]]
=== CMake (single-binary package)

Here is an example of creating a simple Debian package from a simple C source program using CMake (*CMakeLists.txt* and some files such as *config.h.in*) as its build system. See <<cmake>>.

The *cmake* command generates the *Makefile* file based on the *CMakeLists.txt* file and its *-D* option.  It also configures the file as specified in its *configure_file(...)* by replacing strings with *@...@* and changing the *#cmakedefine ...* line.

Let's assume this upstream tarball to be *debhello-1.7.tar.gz*.

This type of source is meant to be installed as a non-system file, for example, as:

----
 $ tar -xzmf debhello-1.7.tar.gz
 $ cd debhello-1.7
 $ mkdir obj-x86_64-linux-gnu # for out-of-tree build
 $ cd obj-x86_64-linux-gnu
 $ cmake ..
 $ make
 $ make install
----

Let's get the source and make the Debian package.

.Download *debhello-1.7.tar.gz*
----
include::../examples/debhello-1.7_build-1/step000.slog[]
----

Here, the contents of this source are as follows.

.*src/hello.c* (v=1.7):
----
include::../examples/debhello-1.7_build-1/step101.slog[]
----

.*src/config.h.in* (v=1.7):
----
include::../examples/debhello-1.7_build-1/step102.slog[]
----

.*CMakeLists.txt* (v=1.7):
----
include::../examples/debhello-1.7_build-1/step103.slog[]
----

Let's package this with the *debmake* command.

----
sys::[head -n3 ../examples/debhello-1.7_build-1/step200.slog]
 ...
sys::[grep -A12  '^I: sanity check of parameters' ../examples/debhello-1.7_build-1/step200.slog]
 ...
----

The result is similar to <<configure-single>> but not exactly the same.

Let's inspect the notable template files generated.

// .The source tree after the basic *debmake* execution. (v=1.7)
// ----
// include::../examples/debhello-1.7_build-1/step201.slog[]
// ----

.*debian/rules* (template file, v=1.7):
----
include::../examples/debhello-1.7_build-1/step202.slog[]
----

.*debian/control* (template file, v=1.7):
----
include::../examples/debhello-1.7_build-1/step203.slog[]
----

Let's make this Debian package better as the maintainer.

.*debian/rules* (maintainer version, v=1.7):
----
include::../examples/debhello-1.7_build-1/step301.slog[]
----

.*debian/control* (maintainer version, v=1.7):
----
include::../examples/debhello-1.7_build-1/step302.slog[]
----

There are several other template files under the *debian/* directory.  These also need to be updated.

The rest of the packaging activities are practically the same as the one in <<configure-single>>.