| 1 |
=== gtkmm-documentation/examples/book/buildapp/step[1-9] === |
| 2 |
|
| 3 |
== Building the examples == |
| 4 |
|
| 5 |
The examples in this directory are built with 'ninja examples' or 'ninja test' |
| 6 |
alongside the rest of the examples in gtkmm-documentation. |
| 7 |
|
| 8 |
The examples in the step[1-9] directories can also be built separately. |
| 9 |
You can then choose to build with meson and ninja or with make. |
| 10 |
|
| 11 |
$ cd step1 # or step2, step3, etc. |
| 12 |
$ meson build # or another name for the build directory |
| 13 |
$ cd build |
| 14 |
$ ninja |
| 15 |
or |
| 16 |
$ cd step1 # or step2, step3, etc. |
| 17 |
$ make -f Makefile.example |
| 18 |
|
| 19 |
To make gnome-shell use the desktop file and icon for one of the examples |
| 20 |
while running it uninstalled, do the following: |
| 21 |
|
| 22 |
$ cd step1/build # or step2/build, step3/build, etc. |
| 23 |
$ ninja install-desktop-file |
| 24 |
or |
| 25 |
$ cd step1 # or step2, step3, etc. |
| 26 |
$ make -f Makefile.example install-desktop-file |
| 27 |
|
| 28 |
To make Gio::Settings find the preferences in step[5-9], they must be stored |
| 29 |
where they can be found via one of the environment variables XDG_DATA_DIRS, |
| 30 |
XDG_DATA_HOME or GSETTINGS_SCHEMA_DIR. One way to achieve this is: |
| 31 |
|
| 32 |
$ cd step5/build # or step6/build, step7/build, etc. |
| 33 |
$ export GSETTINGS_SCHEMA_DIR=. |
| 34 |
or |
| 35 |
$ cd step5 # or step6, step7, etc. |
| 36 |
$ export GSETTINGS_SCHEMA_DIR=. |
| 37 |
|
| 38 |
But then the program can only be run from that directory. Alternatively, |
| 39 |
set GSETTINGS_SCHEMA_DIR to an absolute path, such as |
| 40 |
|
| 41 |
$ export GSETTINGS_SCHEMA_DIR=~/.local/share/glib-2.0/schemas |
| 42 |
|
| 43 |
and do the following: |
| 44 |
|
| 45 |
$ cd step5/build # or step6/build, step7/build, etc. |
| 46 |
$ ninja install-gschema-file |
| 47 |
or |
| 48 |
$ cd step5 # or step6, step7, etc. |
| 49 |
$ make -f Makefile.example install-gschema-file |