Commit aaac7a16 authored by Philip Withnall's avatar Philip Withnall

docs: Update HACKING and README to mention Meson rather than autotools

Signed-off-by: Philip Withnall's avatarPhilip Withnall <>
parent c8797d7a
If you want to hack on the GLib project, you'll need to have the
following packages installed:
- GNU autoconf 2.62
- GNU automake 1.11
- GNU libtool 2.2
- Meson 0.48.0
- GNU gettext 0.10.40
- pkg-config 0.16
- gtk-doc
- libffi 3.0.0
These should be available by ftp from or any of the
fine GNU mirrors. Beta software can be found at
To compile a GIT version of glib on your system, you will need to take
To compile a Git version of glib on your system, you will need to take
several steps to setup the tree for compilation. You can do all these
steps at once by running:
checkout/glib# ./
Basically this does the following for you:
checkout/glib# aclocal; automake; autoconf
The above commands create the "configure" script. Now you
can run the configure script in checkout/glib to create all
the Makefiles.
Before running or configure, make sure you have libtool
in your path.
Note that runs configure for you. If you wish to pass
options like --prefix=/usr to configure you can give those options
to and they will be passed on to configure.
checkout/glib# meson _build
For information about submitting patches see the file. For
information about major design decisions, see the README.rationale file.
......@@ -29,7 +29,7 @@ Note that to just *use* GLib on Windows, there is no need to build it
On Windows setting up a correct build environment can be quite a task,
especially if you are used to just type "./configure; make" on Linux,
especially if you are used to just typing `meson; ninja` on Linux,
and expect things to work as smoothly on Windows.
The following preprocessor macros are to be used for conditional
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment