blob: 4d2bf133d8a6c0977145ad6a1012f0f061f5cd78 (
plain)
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
|
# macOS build pipeline
This folder contains the scripts that make up the build pipeline for Inkscape on macOS.
## Requirements
- Use a __dedicated, clean macOS installation__ as build machine. "clean" as in "freshly installed + Xcode CLI tools". Nothing more, nothing less.
- Especially no MacPorts, no Fink, no Homebrew, ... because they could interfere with the build system we're using.
- macOS 10.13.6 with Xcode 10.1.
- Other versions might work but haven't been tested.
- A full Xcode installation won't hurt, but is not required.
- __Use a dedicated user account__ unless you're prepared that these scripts will delete and overwrite your data in the following locations:
_(comments based on default configuration)_
```bash
$HOME/.cache # will be symlinked to $HOME/work/tmp
$HOME/.local # will be symlinked to $HOME/work/opt
$HOME/.profile # will be overwritten
$HOME/Source # will be symlinked to $HOME/work/opt/src
```
- __16 GiB RAM__, since we're using a 10 GiB ramdisk to build everything.
- Using a ramdisk speeds up the process significantly and avoids wearing out your ssd.
- You can choose to not use a ramdisk by overriding `RAMDISK_ENABLE=false` in a e.g. `011-custom.sh` file.
- The build environment takes up ~6.5 GiB of disk space, the Inkscape Git repository ~1.8 GiB. Subject to change and YMMV.
- somewhat decent __internet connection__ for all the downloads
## Usage
### standalone
> TODO: These scripts were initially designed as part of a dedicated repository, not the Inkscape repository itself. Therefore they contain a step that shallow-clones the Inkscape repository to build. This behaviour will be improved upon in a future version.
Run:
```bash
./build_everything.sh
```
This will run all the `nnn-*.sh` scripts consecutively.
### GitLab CI
#### manual task: setup build environment
For now, the CI pipeline is designed to be run on a persistent machine since it does not setup the required build environment itself. This is a manual task you have to perform beforehand by running
```bash
./create_buildenv.sh
````
This will setup the build environment in `$HOME/work` as a ramdisk.
#### configuration example `.gitlab-runner/config.toml`
```toml
[[runners]]
name = "<YOUR RUNNER'S NAME>"
url = "https://gitlab.com/"
token = "<YOUR TOKEN>"
executor = "shell"
builds_dir = "/Users/<YOUR DEDICATED USER>/work/builds"
cache_dir = "/Users/<YOUR DEDICATED USER>/work/cache"
```
#### configuration example `.gitlab-ci.yml`
```yaml
buildmacos:
script:
- packaging/macos/210-inkscape.sh
```
## Status
This is still a work in progress and actively being worked on. Use at your own risk.
|
