1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
|
: #-*- Perl -*-
eval 'exec perl -w -S $0 ${1+"$@"}' # Portability kludge
if 0;
# config.values.sh --- create config.values.in from ../configure
# Author: Martin Buchholz
# Maintainer: Martin Buchholz
# Keywords: configure elisp report-xemacs-bugs
# This file is part of XEmacs.
# XEmacs is free software; you can redistribute it and/or modify it
# under the terms of the GNU General Public License as published by
# the Free Software Foundation; either version 2, or (at your option)
# any later version.
# XEmacs is distributed in the hope that it will be useful, but
# WITHOUT ANY WARRANTY; without even the implied warranty of
# MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU
# General Public License for more details.
# You should have received a copy of the GNU General Public License
# along with XEmacs; see the file COPYING. If not, write to
# the Free Software Foundation, Inc., 59 Temple Place - Suite 330,
# Boston, MA 02111-1307, USA.
### Commentary:
## Extract all the @foo@ configuration symbols from ../configure
## to make them available to elisp later (see util/config.el)
## Primarily useful for creating ridiculously verbose bug reports.
##
## See lisp/config.el, ../configure.in,
## and the Autoconf documentation on AC_OUTPUT, for more details.
##
## This script needs only to be run occasionally (before a Net release)
## by an XEmacs Maintainer (consider yourself so blessed, if you are
## actually reading this commentary).
##
if (! -r "./configure") {
chdir ".." or die "Can't chdir: $!";
if (! -r "./configure") {
die "Can't find configure!";
}
}
sub FileContents {
local $/ = undef; # Slurp mode
open (FILE, "< $_[0]") or die "$_[0]: $!";
my $contents = <FILE>;
close FILE or die "$_[0]: $!";
return $contents;
}
my $configure_contents = FileContents "./configure";
my $cvi_contents = FileContents "lib-src/config.values.in";
my $new_cvi_contents =
";;; Do not edit this file!
;;; This file was automatically generated, by the config.values.sh script,
;;; from configure, which was itself automatically generated from configure.in.
;;;
;;; See lisp/config.el for details on how this file is used.
;;;
;;; You are trapped in a twisty maze of strange-looking files, all autogenerated...
;;; configure is created, from configure.in, by autoconf
;;; config.values.in is created, from configure, by config.values.sh
;;; config.values is created, from config.values.in, by configure
;;; config.values is read by lisp/config.el,
;;; to create the (Lisp object) config-value-hash-table
;;; Variables defined in configure by AC_SUBST follow:
;;; (These are used in Makefiles)
";
my %done;
for my $var (sort { $a cmp $b }
$configure_contents =~
/^s\%\@([A-Za-z0-9_]+)\@\%\$[A-Za-z0-9_]+\%g/mg) {
$new_cvi_contents .= "$var \"\@$var\@\"\n" unless exists $done{$var};
$done{$var} = 1;
}
$new_cvi_contents .= "
;;; Variables defined in configure by AC_DEFINE and AC_DEFINE_UNQUOTED follow:
;;; (These are used in C code)
";
if ($cvi_contents ne $new_cvi_contents) {
unlink "lib-src/config.values.in";
open (CVI, "> lib-src/config.values.in")
or die "lib-src/config.values.in: $!";
print CVI $new_cvi_contents;
close CVI
or die "lib-src/config.values.in: $!";
}
|
