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
|
# Creating installation packages
## Unix-like systems (`Unix Makefiles`)
```sh
mkdir build
cd build
cmake ..
cpack -G RPM -C Release
```
The command `cpack --help` will display the list of generators
that are available on your system.
## Microsoft Windows
In the Microsoft Visual Studio installer, be sure to install the
components for CMake integration.
You will also need the following:
* [Git](https://git-scm.com/download/win)
* [CMake](https://cmake.org/download/)
* [WiX Toolset](https://wixtoolset.org/releases/)
Execute the following in the Visual Studio Developer Command Prompt
(a specially configured `cmd.exe` or Powershell).
```sh
mkdir build
cd build
cmake ..
cmake --build . --config Release
cpack -G WIX
```
## Debian GNU/Linux, Ubuntu, and similar systems
The `cpack` generator will skip `ctest` or the creation of a separate
package for debug information:
```sh
mkdir build
cd build
cmake ..
cpack -G DEB -C Release
sudo dpkg -i cbmconvert*.deb
```
You can also initiate a build, run tests and create and install
more conventional packages using the following commands:
```sh
dpkg-buildpackage --no-sign
sudo dpkg -i ../cbmconvert*.deb
```
If you invoking `dpkg-buildpackage` on an arbitrary source code revision
and not a release, you will have to apply a patch like this in order to
bypass some checks:
```diff
diff --git a/debian/source/format b/debian/source/format
index 163aaf8..89ae9db 100644
--- a/debian/source/format
+++ b/debian/source/format
@@ -1 +1 @@
-3.0 (quilt)
+3.0 (native)
diff --git a/debian/changelog b/debian/changelog
index ffbec85..d4786f2 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,4 +1,4 @@
-cbmconvert (2.1.5-1) unstable; urgency=medium
+cbmconvert (2.1.5) unstable; urgency=medium
* Maintenance release, with regression tests and bug fixes.
```
|
