@@ -19,7 +19,7 @@ Static binaries building using custom alpine image.
19
19
image defined in [ Dockerfile] ( build/Dockerfile ) . In order to build them you should specify
20
20
` OCTEZ_VERSION ` env variable and run the script:
21
21
```
22
- export OCTEZ_VERSION="v14.1 "
22
+ export OCTEZ_VERSION="v17.3 "
23
23
./docker-static-build.sh
24
24
```
25
25
After that, directory will contain built static binaries.
@@ -29,6 +29,14 @@ Currently supported architectures are: `host` and `aarch64`, so that
29
29
one can build native binaries for current architecture or build ` aarch64 ` binaries on
30
30
` x86_64 ` machine.
31
31
32
+ In order to build only specific binaries, or experimental/dev ones, you should specify
33
+ ` OCTEZ_EXECUTABLES ` env variable:
34
+ ```
35
+ export OCTEZ_VERSION="v17.3"
36
+ export OCTEZ_EXECUTABLES="octez-smart-rollup-wasm-debugger octez-protocol-compiler octez-dal-node"
37
+ ./docker-static-build.sh
38
+ ```
39
+
32
40
### Compiling for ` aarch64 ` on ` x86_64 ` prerequisites
33
41
34
42
Docker image defined in [ ` Dockerfile.aarch64 ` ] ( build/Dockerfile.aarch64 ) uses qemu for
@@ -84,7 +92,7 @@ To see all available options, run:
84
92
In order to build binary ` .deb ` packages specify ` OCTEZ_VERSION ` and
85
93
run the following command:
86
94
```
87
- export OCTEZ_VERSION="v14.1 "
95
+ export OCTEZ_VERSION="v17.3 "
88
96
cd .. && ./docker/package.py --os ubuntu --type binary
89
97
```
90
98
@@ -93,14 +101,14 @@ It is also possible to specify packages to build with `-p` or `--packages` optio
93
101
```
94
102
# cd .. && ./docker/package.py -os ubuntu --type binary --packages <tezos-binary-1> <tezos-binary-2>
95
103
# Example for baker
96
- export OCTEZ_VERSION="v14.1 "
104
+ export OCTEZ_VERSION="v17.3 "
97
105
cd .. && ./docker/package.py --os ubuntu --type binary -p tezos-client tezos-node
98
106
```
99
107
100
108
In order to choose specific ubuntu distribution to build for (see [ support policy] ( ../docs/support-policy.md ) ),
101
109
use ` -d ` or ` --distributions ` option:
102
110
```
103
- export OCTEZ_VERSION="v14.1 "
111
+ export OCTEZ_VERSION="v17.3 "
104
112
cd .. && ./docker/package.py --os ubuntu --type binary -d focal jammy -p tezos-client tezos-node
105
113
```
106
114
@@ -118,7 +126,7 @@ sudo apt install <path to deb file>
118
126
119
127
In order to build source packages run the following commands:
120
128
```
121
- export OCTEZ_VERSION="v14.1 "
129
+ export OCTEZ_VERSION="v17.3 "
122
130
cd .. && ./docker/package.py --os ubuntu --type source
123
131
# you can also build single source package
124
132
cd .. && ./docker/package.py --os ubuntu --type source --packages tezos-client
@@ -137,7 +145,7 @@ the submitter info and signed.
137
145
138
146
If you want to sign resulted source packages automatically, you can provide signer identity through ` --gpg-sign ` or ` -s ` option:
139
147
```
140
- export OCTEZ_VERSION="v14.1 "
148
+ export OCTEZ_VERSION="v17.3 "
141
149
cd .. && ./docker/package.py --os ubuntu --type source -d focal jammy -p tezos-client -s <signer_info>
142
150
```
143
151
For example,
` signer_info ` can be the following:
` Roman Melnikov <[email protected] > `
@@ -211,22 +219,22 @@ To see all available options, run:
211
219
In order to build binary ` .rpm ` packages specify ` OCTEZ_VERSION ` and
212
220
run the following command:
213
221
```
214
- export OCTEZ_VERSION="v14.1 "
222
+ export OCTEZ_VERSION="v17.3 "
215
223
cd .. && ./docker/package.py --os fedora --type binary
216
224
```
217
225
218
226
It is also possible to specify packages to build with ` -p ` or ` --packages ` option. In order to do that run the following:
219
227
```
220
228
# cd .. && ./docker/package.py --os fedora --type binary --packages <tezos-binary-1> <tezos-binary-2>
221
229
# Example for baker
222
- export OCTEZ_VERSION="v14.1 "
230
+ export OCTEZ_VERSION="v17.3 "
223
231
cd .. && ./docker/package.py --os fedora --type binary -p tezos-client tezos-node
224
232
```
225
233
226
234
In order to build packages for specific Fedora distribution (see [ support policy] ( ../docs/support-policy.md ) ),
227
235
use ` -d ` or ` --distributions ` option:
228
236
```
229
- export OCTEZ_VERSION="v14.1 "
237
+ export OCTEZ_VERSION="v17.3 "
230
238
cd .. && ./docker/package.py --os fedora -d 38 --type binary -p tezos-baking
231
239
```
232
240
@@ -247,15 +255,15 @@ sudo dnf install <path to rpm file>
247
255
248
256
In order to build source packages run the following commands:
249
257
```
250
- export OCTEZ_VERSION="v14.1 "
258
+ export OCTEZ_VERSION="v17.3 "
251
259
cd .. && ./docker/package.py --os fedora --type source
252
260
# you can also build single source package
253
261
cd .. && ./docker/package.py --os fedora --type source -p tezos-client
254
262
```
255
263
256
264
If you want to sign resulted source packages automatically, you can provide signer identity through ` --gpg-sign ` or ` -s ` option:
257
265
```
258
- export OCTEZ_VERSION="v14.1 "
266
+ export OCTEZ_VERSION="v17.3 "
259
267
cd .. && ./docker/package.py --os fedora --type source -p tezos-client -s <signer_info>
260
268
```
261
269
For example,
` signer_info ` can be the following:
` Roman Melnikov <[email protected] > `
0 commit comments