mirror of
				https://gitlab.gnome.org/GNOME/glib.git
				synced 2025-11-04 01:58:54 +01:00 
			
		
		
		
	Mon Apr 16 12:04:52 2001 Owen Taylor <otaylor@redhat.com> * configure.in: Remove warnings about conflicts with the stable version. * glib-2.0.m4: Fix some of the error text to be halfway up to date. * README.in INSTALL.in: Add these to generate README, INSTAL (as in the stable branch). Update. * HACKING: Update.
		
			
				
	
	
		
			34 lines
		
	
	
		
			1.1 KiB
		
	
	
	
		
			Plaintext
		
	
	
	
	
	
			
		
		
	
	
			34 lines
		
	
	
		
			1.1 KiB
		
	
	
	
		
			Plaintext
		
	
	
	
	
	
If you want to hack on the GLib project, it will make you life easier
 | 
						|
to have the following packages installed:
 | 
						|
 | 
						|
	- GNU autoconf 2.13
 | 
						|
	- GNU automake 1.4
 | 
						|
	        (Beta releases are at ftp://ftp.cygnus.com/pub/tromey)
 | 
						|
	- GNU libtool 1.2d
 | 
						|
 | 
						|
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.
 | 
						|
 | 
						|
To compile a CVS 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:
 | 
						|
 | 
						|
        cvsroot/glib# ./autogen.sh
 | 
						|
   
 | 
						|
Basically this does the following for you:
 | 
						|
 | 
						|
  	cvsroot/glib# aclocal; automake; autoconf
 | 
						|
 | 
						|
        The above commands create the "configure" script.  Now you
 | 
						|
	can run the configure script in cvsroot/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 README file.
 |