Re: [PATCH] glib configure.in patches
- From: James Henstridge <james daa com au>
- To: Owen Taylor <otaylor redhat com>
- Cc: Art Haas <ahaas neosoft com>, gtk-devel-list gnome org
- Subject: Re: [PATCH] glib configure.in patches
- Date: Mon, 08 Jul 2002 09:05:31 +0800
Owen Taylor wrote:
# Process this file with autoconf to produce a configure script.
-AC_INIT(glib/glib.h)
+AC_INIT([glib], [2.0.4])
^^^^^
Not an acceptable change; the version information has to be only in
one place.
The solution to this problem that I use in pygtk is the following:
dnl the pygtk version number
m4_define(pygtk_major_version, 1)
m4_define(pygtk_minor_version, 99)
m4_define(pygtk_micro_version, 10)
m4_define(pygtk_version,
pygtk_major_version.pygtk_minor_version.pygtk_micro_version)
AC_INIT(pygtk, pygtk_version,
[http://bugzilla.gnome.org/enter_bug.cgi?product=gnome-python&component=pygtk])
AC_DEFINE(PYGTK_MAJOR_VERSION, pygtk_major_version, [PyGtk major version])
AC_DEFINE(PYGTK_MINOR_VERSION, pygtk_minor_version, [PyGtk minor version])
AC_DEFINE(PYGTK_MICRO_VERSION, pygtk_micro_version, [PyGtk macro version])
I can then use any of the M4 macros anywhere inside my configure script,
and they get substituted to the correct values. Works very well for me.
James.
--
Email: james daa com au | Linux.conf.au 2003 Call for Papers out
WWW: http://www.daa.com.au/~james/ | http://conf.linux.org.au/cfp.html
[
Date Prev][
Date Next] [
Thread Prev][
Thread Next]
[
Thread Index]
[
Date Index]
[
Author Index]