luc14n0/glib
1
0
Fork 0
mirror of https://gitlab.gnome.org/GNOME/glib.git synced 2024-12-25 06:56:14 +01:00
Code Issues Packages Projects Releases Wiki Activity

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

Browse Source 
Signed-off-by: Philip Withnall <withnall@endlessm.com>
This commit is contained in:
Philip Withnall 2019-01-09 11:40:29 +00:00
parent c8797d7a42
commit aaac7a166f
2 changed files with 4 additions and 24 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

26
HACKING
View File

@ -1,37 +1,17 @@
If you want to hack on the GLib project, you'll need to have the If you want to hack on the GLib project, you'll need to have the
following packages installed: following packages installed:
- GNU autoconf 2.62 - Meson 0.48.0
- GNU automake 1.11
- GNU libtool 2.2
- GNU gettext 0.10.40 - GNU gettext 0.10.40
- pkg-config 0.16 - pkg-config 0.16
- gtk-doc - gtk-doc
- libffi 3.0.0 - libffi 3.0.0
These should be available by ftp from ftp.gnu.org or any of the To compile a Git version of glib on your system, you will need to take
fine GNU mirrors. Beta software can be found at alpha.gnu.org.
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 several steps to setup the tree for compilation. You can do all these
steps at once by running: steps at once by running:
checkout/glib# ./autogen.sh checkout/glib# meson _build
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 autogen.sh or configure, make sure you have libtool
in your path.
Note that autogen.sh runs configure for you. If you wish to pass
options like --prefix=/usr to configure you can give those options
to autogen.sh and they will be passed on to configure.
For information about submitting patches see the CONTRIBUTING.md file. For For information about submitting patches see the CONTRIBUTING.md file. For
information about major design decisions, see the README.rationale file. information about major design decisions, see the README.rationale file.

2
README.win32
View File

@ -29,7 +29,7 @@ Note that to just *use* GLib on Windows, there is no need to build it
yourself. yourself.
On Windows setting up a correct build environment can be quite a task, 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. and expect things to work as smoothly on Windows.
The following preprocessor macros are to be used for conditional The following preprocessor macros are to be used for conditional