summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorKjell Ahlstedt <kjellahlstedt@gmail.com>2020-06-05 16:37:25 +0200
committerKjell Ahlstedt <kjellahlstedt@gmail.com>2020-06-05 16:37:25 +0200
commitf5c77516c441b9491df74a70f4a5f883aca9a22b (patch)
tree6ff9c3e5bbd170c2581d8084c9311d7dfb22ce8f
parent9089997b31fbd489076cc424eb04bce2146150dd (diff)
README: Update with instructions for building cairomm
-rw-r--r--README103
1 files changed, 96 insertions, 7 deletions
diff --git a/README b/README
index 6605a4e..d7cb4b7 100644
--- a/README
+++ b/README
@@ -1,13 +1,102 @@
cairomm
--------------
-
+-------
This library provides a C++ interface to cairo.
-
-Read the file 'INSTALL' for instructions to compile and install the library.
+See https://www.cairographics.org/cairomm/
See the examples directory for example code.
Use pkg-config to discover the necessary include and linker arguments. For instance,
- pkg-config cairomm-1.0 --cflags --libs
-Ideally you would use PKG_CHECK_MODULES in your configure.ac file.
-See http://www.openismus.com for generic help with that.
+ pkg-config cairomm-1.16 --cflags --libs
+If you build with Autotools, ideally you would use PKG_CHECK_MODULES in your
+configure.ac file.
+
+
+# Building
+
+Whenever possible, you should use the official binary packages approved by the
+supplier of your operating system, such as your Linux distribution.
+
+## Building on Windows
+
+See MSVC_NMake/README
+
+## Building from a release tarball
+
+Extract the tarball and go to the extracted directory:
+ $ tar xf cairomm-@CAIROMM_VERSION@.tar.xz
+ $ cd cairomm-@CAIROMM_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.
+Then you don't have to use maintainer-mode.
+
+How do you know how the tarball was made? If it was made with Meson,
+it contains files in untracked/docs/ and other subdirectories
+of untracked/.
+
+### Building from a tarball with Meson
+
+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
+
+Building from git can be difficult so you should prefer building from
+a release tarball unless you need to work on the cairomm code itself.
+
+jhbuild can be a good help
+ https://gitlab.gnome.org/GNOME/jhbuild
+ https://wiki.gnome.org/Projects/Jhbuild
+
+### Building from git with Meson
+
+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