File tree Expand file tree Collapse file tree 1 file changed +10
-0
lines changed Expand file tree Collapse file tree 1 file changed +10
-0
lines changed Original file line number Diff line number Diff line change @@ -13,30 +13,35 @@ cd libdsc
13
13
## Building and Testing
14
14
15
15
### Basic Build
16
+
16
17
``` bash
17
18
./scripts/build.sh
18
19
```
19
20
20
21
### Run Tests
22
+
21
23
``` bash
22
24
./scripts/build.sh
23
25
cd build
24
26
ctest --output-on-failure
25
27
```
26
28
27
29
### Run Linter
30
+
28
31
``` bash
29
32
./scripts/lint.sh
30
33
```
31
34
32
35
### Format Code
36
+
33
37
``` bash
34
38
./scripts/format.sh
35
39
```
36
40
37
41
## Package Management
38
42
39
43
### Official Releases
44
+
40
45
The recommended way to create releases is through GitHub:
41
46
42
47
1 . Tag your version:
@@ -55,9 +60,11 @@ git push origin v0.1.0-alpha
55
60
This ensures consistent, reproducible builds in a clean environment.
56
61
57
62
### Local Package Testing
63
+
58
64
For development and testing, you can build packages locally in the dev container:
59
65
60
66
#### Debian Package
67
+
61
68
``` bash
62
69
./scripts/build-debian.sh
63
70
```
@@ -66,6 +73,7 @@ Outputs:
66
73
- libdsc-dev_ * .deb (development)
67
74
68
75
#### RPM Package
76
+
69
77
``` bash
70
78
./scripts/build-rpm.sh
71
79
```
@@ -78,6 +86,7 @@ Requirements:
78
86
- rpm-build and rpmdevtools packages
79
87
80
88
#### Arch Package
89
+
81
90
``` bash
82
91
./scripts/build-arch.sh
83
92
```
@@ -104,6 +113,7 @@ Note: Local package builds are useful for testing but should not be distributed.
104
113
- Single package with both runtime and development files
105
114
106
115
### Version Numbering
116
+
107
117
- Release tags: v0.1.0-alpha
108
118
- Debian format: 0.1.0~ alpha1
109
119
- RPM format: 0.1.0~ alpha
You can’t perform that action at this time.
0 commit comments