summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorKjell Ahlstedt <kjellahlstedt@gmail.com>2022-09-12 16:03:39 +0200
committerKjell Ahlstedt <kjellahlstedt@gmail.com>2022-09-12 16:18:18 +0200
commit2f5e345fc08641d0a9b4c35aaa8ff9825f1a7482 (patch)
treeb12c276812323ec98ed4b6189bab4afb6ac12f97
parented7d771f67145fdb8aab427d25313bfc43e1c5a4 (diff)
downloadglibmm-2f5e345fc08641d0a9b4c35aaa8ff9825f1a7482.tar.gz
Convert README to README.md
-rw-r--r--README.md (renamed from README)40
1 files changed, 36 insertions, 4 deletions
diff --git a/README b/README.md
index f13cd66a..c3d5e47d 100644
--- a/README
+++ b/README.md
@@ -1,3 +1,4 @@
+# glibmm
This is glibmm, a C++ API for parts of glib that are useful for C++.
See http://www.gtkmm.org
@@ -13,8 +14,10 @@ See README.win32
## Building from a release tarball
Extract the tarball and go to the extracted directory:
+```
$ tar xf glibmm-@GLIBMM_VERSION@.tar.xz
$ cd glibmm-@GLIBMM_VERSION@
+```
It's easiest to build with Meson, if the tarball was made with Meson,
and to build with Autotools, if the tarball was made with Autotools.
@@ -28,31 +31,46 @@ other subdirectories of untracked/.
Don't call the builddir 'build'. There is a directory called 'build' with
files used by Autotools.
-
+```
$ meson --prefix /some_directory --libdir lib your_builddir .
$ cd your_builddir
+```
If the tarball was made with Autotools, you must enable maintainer-mode:
+```
$ meson configure -Dmaintainer-mode=true
+```
Then, regardless of how the tarball was made:
+```
$ ninja
$ ninja install
+```
You can run the tests like so:
+```
$ ninja test
+```
### Building from a tarball with Autotools
If the tarball was made with Autotools:
+```
$ ./configure --prefix=/some_directory
+```
If the tarball was made with Meson, you must enable maintainer-mode:
+```
$ ./autogen.sh --prefix=/some_directory
+```
Then, regardless of how the tarball was made:
+```
$ make
$ make install
+```
You can build the examples and tests, and run the tests, like so:
+```
$ make check
+```
## Building from git
@@ -60,8 +78,9 @@ Building from git can be difficult so you should prefer building from
a release tarball unless you need to work on the glibmm code itself.
jhbuild can be a good help
- https://gitlab.gnome.org/GNOME/jhbuild
- https://wiki.gnome.org/Projects/Jhbuild
+- https://gitlab.gnome.org/GNOME/jhbuild
+- https://wiki.gnome.org/Projects/Jhbuild
+- https://gnome.pages.gitlab.gnome.org/jhbuild
### Building from git with Meson
@@ -69,24 +88,37 @@ Maintainer-mode is enabled by default when you build from a git clone.
Don't call the builddir 'build'. There is a directory called 'build' with
files used by Autotools.
-
+```
$ meson --prefix /some_directory --libdir lib your_builddir .
$ cd your_builddir
$ ninja
$ ninja install
+```
You can run the tests like so:
+```
$ ninja test
+```
You can create a tarball like so:
+```
$ ninja dist
+```
### Building from git with Autotools
+```
$ ./autogen.sh --prefix=/some_directory
$ make
$ make install
+```
You can build the examples and tests, and run the tests, like so:
+```
$ make check
+```
You can create a tarball like so:
+```
$ make distcheck
+```
or
+```
$ make dist
+```