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
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
|
gedit installation by building the source code
==============================================
Recommendation to install in a separate prefix
----------------------------------------------
Once you have built gedit from source, you cannot run the application from its
build directory: you need to install it with `ninja install`. For this reason it
is highly recommended that you install in a separate prefix instead of
overwriting your system binaries.
Note however that when running gedit from a custom prefix you will need to set
many environment variables accordingly, for instance `PATH` and `XDG_DATA_DIR`.
There exists several tools that GNOME developers use to take care of all of
this. See the _Tools_ section below.
Installation of the dependencies
--------------------------------
You need to have all gedit dependencies installed, with recent enough versions.
If a dependency is missing or is too old, the build configuration fails (you can
try to run the build configuration command for gedit until it succeeds, see the
procedure below).
You can install the dependencies by installing packages provided by your
operating system, for example on Fedora:
```
# dnf builddep gedit
```
But if your version of gedit provided by the OS differs too much from the
version of gedit you want to build from source, you'll need to install the new
dependencies from source too, and it can become a complicated task if you do it
manually.
Also, during gedit development, gedit may depend on a not-yet-released
development version of a GNOME dependency. So certain GNOME dependencies may
need to be installed from Git.
That's why if you have difficulties installing recent enough versions of the
dependencies, it is usually easier to use one of the tools explained in the next
section.
Tools
-----
There are several tools available that take care of the following:
- Install in a separate prefix.
- Build or install dependencies.
- Plus, for some tools: run in a container/sandbox.
GNOME developers usually use one of these tools:
- [JHBuild](https://developer.gnome.org/jhbuild/unstable/)
- Or [BuildStream](https://buildstream.build/)
- Or [Flatpak](https://flatpak.org/)
JHBuild tips:
- Try `ignore_suggests = True` in your jhbuildrc to have fewer dependencies to
build (see the difference with "jhbuild list gedit"). Another solution is to
put some modules in the skip variable in jhbuildrc.
There is also [Imovo](https://gitlab.gnome.org/swilmet/imovo), a more minimal
tool.
Building the gedit module manually
----------------------------------
If you use one of the above tools, you don't need all the explanations in this
section. But it can be instructive.
gedit uses the [Meson](https://mesonbuild.com/) build system.
Once the dependencies are installed, here are simple procedures to finally build
the gedit module from source.
### Installation onto the system
**Warning**: this procedure doesn't install in a separate prefix, so it may
overwrite your system binaries.
```
$ mkdir build && cd build/
$ meson # Build configuration
$ ninja # Build
[ Become root if necessary ]
$ ninja install # Installation
```
### Installation in a separate prefix
Just change the above `meson` command by:
```
$ meson --prefix /an/other/path
```
|
