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
|
# Static extractor executable build
For use e.g. as part of Nextcloud it can be useful to build a fully static executable binary.
This is done by the `static-extractor` Gitlab job, the scripts in this folder are the implementation detail of that job.
## Supported platforms
Anything x86_64 with GLIBC 2.17 or newer.
## Deployment
When using the iCal output format, the extractor needs external translation catalogs. Those are provided
in the same archive as the binary, and need to be placed in the same relative location to the binary to be found.
Alternatively, they can be placed in a path listed in the `XDG_DATA_DIRS` environment variable.
Translations are done using Gettext and thus follows the
environment variables that influence that (`LANG`, `LANGUAGE`, `LC_ALL`, etc).
This also implies that Glibc locale data has to be installed on the system, Gettext will not work without those.
## CD builds
CD builds are published to https://cdn.kde.org/ci-builds/pim/kitinerary/.
## Local builds
If you want to locally reproduce the same build, this can be done by running the commands from the build scripts in the
order specified in `.gitlab-ci.yml` in an environment set up like follows:
```
docker run -it --rm centos:centos7
export CI_PROJECT_PATH=pim/kitinerary
export BUILD_ROOT=/builds
export STAGING_ROOT=/builds/staging
export CI_PROJECT_DIR=$BUILD_ROOT/$CI_PROJECT_PATH
```
Optionally, map a local folder into `/builds` in the Docker image to retain the checkouts and build results. This
is particularly useful when debugging/optimizing the build itself.
## Future Work
Ideally this would reuse the static build artifacts produced by the CI already anyway, and reuse the
existing dependency mechanism of the CI.
|
