From a03e78210f97a2fba4b0c78d5a5b4c05e20a8779 Mon Sep 17 00:00:00 2001 From: Elijah Newren Date: Sat, 15 Apr 2006 03:35:38 +0000 Subject: [PATCH] Include instructions on setting up a minimal building/testing environment 2006-04-14 Elijah Newren * HACKING: Include instructions on setting up a minimal building/testing environment --- ChangeLog | 5 +++++ HACKING | 22 ++++++++++++++++++++++ 2 files changed, 27 insertions(+) diff --git a/ChangeLog b/ChangeLog index 9c8d0d6a1..032d19bfe 100644 --- a/ChangeLog +++ b/ChangeLog @@ -1,3 +1,8 @@ +2006-04-14 Elijah Newren + + * HACKING: Include instructions on setting up a minimal + building/testing environment + 2006-04-14 Thomas Thurman Add a tabbing function, bound to alt-f6 by default, to cycle diff --git a/HACKING b/HACKING index 6f3bf25fd..5b90e95ba 100644 --- a/HACKING +++ b/HACKING @@ -11,6 +11,7 @@ is nonetheless useful. Overview Administrative issues + Minimal Building/Testing Environment Relevant standards and X properties Debugging and testing Debugging logs @@ -34,6 +35,27 @@ Administrative issues instructions is that the minor version number of a Metacity release should always be a number from the Fibonacci sequence. +Minimal Building/Testing Environment + You do not need to _install_ a development version of Metacity to + build, run and test it; you can run it from some temporary + directory. Also, you do not need to build all of Gnome in order to + build a development version of Metacity -- odds are, you can build + metacity from CVS without building any other modules. + + As long as you have gtk+ >= 2.6 with your distro, you should be able + to install your distro's development packages (e.g. gtk2-devel, + GConf2-devel, and startup-notification-devel on Fedora) and be ready + to build and test Metacity. Steps to do so: + + $ cvs -q -z3 -d :pserver:anonymous@anoncvs.gnome.org:/cvs/gnome \ + checkout metacity + $ cd metacity + $ ./autogen.sh --prefix /usr + $ make + $ ./src/metacity --replace + + Again, note that you do not need to run 'make install'. + Relevant standards and X properties There are two documents that describe some basics about how window managers should behave: the ICCCM (Inter-Client Communication Conventions