summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorEmmanuele Bassi <ebassi@gnome.org>2017-08-14 17:43:40 +0100
committerEmmanuele Bassi <ebassi@gnome.org>2017-08-14 22:23:09 +0100
commitd2af8231836397ebf82a3a3d6457a37fee8de98f (patch)
treee9b059c0882ddd63c8033e9a672689162a8a4a8c
parent0803ee2df463b3a599108b9e111cede16e18ee0a (diff)
downloadgtk+-d2af8231836397ebf82a3a3d6457a37fee8de98f.tar.gz
Rename 'HACKING' to 'CONTRIBUTING'
And remove redundant and obsolete information.
-rw-r--r--CONTRIBUTING.md40
-rw-r--r--HACKING64
2 files changed, 40 insertions, 64 deletions
diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md
new file mode 100644
index 0000000000..d9cb111810
--- /dev/null
+++ b/CONTRIBUTING.md
@@ -0,0 +1,40 @@
+If you want to hack on the GTK+ project, you'll need to have the development
+tools appropriate for your operating system, including:
+
+ - Python (2.7 or 3.x)
+ - Meson
+ - Ninja
+ - Gettext (19.7 or newer)
+ - a C99 compatible compiler
+
+Up-to-date instructions about developing GNOME applications and libraries
+can be found here:
+
+ https://developer.gnome.org
+
+Information about using git with GNOME can be found here:
+
+ https://wiki.gnome.org/Git
+
+In order to get Git GTK+ installed on your system, you need to have the
+required versions of all the GTK+ dependencies; typically, this means a
+recent version of GLib, Cairo, Pango, and ATK.
+
+**Note**: if you plan to push changes to back to the master repository and
+have a GNOME account, you want to use the following instead:
+
+```sh
+$ git clone ssh://<username>@git.gnome.org/git/gtk+
+```
+
+To compile the Git version of GTK+ on your system, you will need to
+configure your build using Meson:
+
+```sh
+$ meson _builddir .
+```
+
+For information about submitting patches and pushing changes to Git, see the
+`README.md` and `README.commits` files. In particular, don't, under any
+circumstances, push anything to Git before reading and understanding
+`README.commmits`.
diff --git a/HACKING b/HACKING
deleted file mode 100644
index 4b20c6b895..0000000000
--- a/HACKING
+++ /dev/null
@@ -1,64 +0,0 @@
-If you want to hack on the GTK+ project, you'll need to have
-the following packages installed:
-
- - GNU autoconf 2.62
- - GNU automake 1.11
- - GNU libtool 2.2
- - indent (GNU indent 1.9.1 is known good)
- - GNU gettext 10.40
-
-These should be available by ftp from ftp.gnu.org or any of the
-fine GNU mirrors. Beta software can be found at alpha.gnu.org.
-
-Up-to-date instructions about developing GNOME applications and libraries
-can be found here:
-
- http://library.gnome.org/devel/
-
-Information about using git with GNOME can be found here:
-
- https://wiki.gnome.org/Git
-
-In order to get GIT GTK+ installed on your system, you need to have
-the most recent GIT versions of GLib, Pango, and ATK installed as well.
-The installation process of these libraries is similar to that of GTK+,
-but needs to be fulfilled prior to installation of GTK+.
-
-If at all possible, please use GIT to get the latest development version of
-gtk+ and glib. You can do the following to get glib and gtk+ from GIT:
-
- $ git clone git://git.gnome.org/glib
- $ git clone git://git.gnome.org/pango
- $ git clone git://git.gnome.org/atk
- $ git clone git://git.gnome.org/gtk+
-
-Note: if you plan to push changes to back to the master repository and
-have a gnome account, you want to use the following instead:
-
- $ git clone ssh://<username>@git.gnome.org/git/gtk+
-
-To compile the GIT version of GTK+ 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:
-
- gtk+$ ./autogen.sh
-
-Basically this does the following for you:
-
- gtk+$ aclocal; automake; autoconf
-
-The above commands create the `configure' script. Now you
-run the `configure' script in `gtk+/' to create all Makefiles.
-More information about that in `INSTALL'.
-
-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 and pushing changes
-to GIT, see the `README' and `README.commits' files. In particular,
-don't, under any circumstances, push anything to GIT before
-reading and understanding `README.commmits'.