2014-05-16 15:49:13 +00:00
|
|
|
#! /bin/sh
|
|
|
|
# Merge pkg-config macros into Emacs sources.
|
|
|
|
# Typical usage:
|
|
|
|
#
|
|
|
|
# admin/merge-pkg-config
|
|
|
|
|
2021-01-01 09:13:56 +00:00
|
|
|
# Copyright 2014-2021 Free Software Foundation, Inc.
|
2014-05-16 15:49:13 +00:00
|
|
|
|
|
|
|
# This file is part of GNU Emacs.
|
|
|
|
|
|
|
|
# GNU Emacs 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 3 of the License, or
|
|
|
|
# (at your option) any later version.
|
|
|
|
|
|
|
|
# GNU Emacs 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
|
2017-09-13 22:52:52 +00:00
|
|
|
# along with GNU Emacs. If not, see <https://www.gnu.org/licenses/>.
|
2014-05-16 15:49:13 +00:00
|
|
|
|
|
|
|
# written by Paul Eggert
|
|
|
|
|
|
|
|
{
|
|
|
|
# Maybe ACLOCAL_PATH is already set-up.
|
|
|
|
oIFS=$IFS
|
|
|
|
IFS=:
|
|
|
|
for dir in $ACLOCAL_PATH ''; do
|
|
|
|
test -n "$dir" && test -r "$dir/pkg.m4" && break
|
|
|
|
done
|
|
|
|
IFS=$oIFS
|
|
|
|
|
|
|
|
test -n "$dir"
|
|
|
|
} || {
|
|
|
|
# Use the pkg.m4 installed where aclocal knows about it.
|
|
|
|
# Maybe we are running our own aclocal, which doesn't know where
|
|
|
|
# the standard pkg.m4 is installed, so try running all the
|
|
|
|
# aclocal programs in our PATH.
|
|
|
|
oIFS=$IFS
|
|
|
|
IFS=:
|
|
|
|
for dir in $PATH ''; do
|
|
|
|
if test -n "$dir" && test -x "$dir/aclocal"; then
|
|
|
|
dir=$("$dir/aclocal" --print-ac-dir) && test -r "$dir/pkg.m4" && break
|
|
|
|
fi
|
|
|
|
done
|
|
|
|
IFS=$oIFS
|
|
|
|
|
|
|
|
test -n "$dir"
|
|
|
|
} || {
|
Use ‘echo’ safely with ‘\’ or leading ‘-’
POSIX says that ‘echo FOO’ produces implementation-defined output
if FOO contains leading ‘-’, or ‘\’ anywhere, so don’t assume GNU
behavior in that case.
* Makefile.in (removenullpaths): Remove.
(epaths-force): Rewrite to avoid the need for ‘echo’.
(install-etc): Be clearer about escaping the shell metacharacters
‘\’ and ‘$’.
* Makefile.in (install-arch-indep, install-etcdoc):
* admin/charsets/mapconv, admin/merge-gnulib, admin/merge-pkg-config:
* admin/quick-install-emacs, build-aux/gitlog-to-emacslog:
* configure.ac, lib-src/rcs2log, make-dist:
* src/Makefile.in (lisp.mk):
Don’t assume ‘echo’ outputs ‘\’ and leading ‘-’ unscathed.
For example, use ‘printf '%s\n' "$foo"’ rather than ‘echo "$foo"’
if $foo can contain arbitrary characters.
* lisp/Makefile.in (TAGS): Use ‘ls’, not ‘echo’, to avoid ‘\’ issues.
* doc/lispref/two-volume.make (vol1.pdf):
* test/etags/make-src/Makefile (web ftp publish):
Use ‘printf’ rather than ‘echo -e’.
2015-10-11 01:03:49 +00:00
|
|
|
printf >&2 '%s\n' "$0: cannot find pkg.m4"
|
2014-05-16 15:49:13 +00:00
|
|
|
exit 1
|
|
|
|
}
|
|
|
|
|
|
|
|
test -d m4 || {
|
Use ‘echo’ safely with ‘\’ or leading ‘-’
POSIX says that ‘echo FOO’ produces implementation-defined output
if FOO contains leading ‘-’, or ‘\’ anywhere, so don’t assume GNU
behavior in that case.
* Makefile.in (removenullpaths): Remove.
(epaths-force): Rewrite to avoid the need for ‘echo’.
(install-etc): Be clearer about escaping the shell metacharacters
‘\’ and ‘$’.
* Makefile.in (install-arch-indep, install-etcdoc):
* admin/charsets/mapconv, admin/merge-gnulib, admin/merge-pkg-config:
* admin/quick-install-emacs, build-aux/gitlog-to-emacslog:
* configure.ac, lib-src/rcs2log, make-dist:
* src/Makefile.in (lisp.mk):
Don’t assume ‘echo’ outputs ‘\’ and leading ‘-’ unscathed.
For example, use ‘printf '%s\n' "$foo"’ rather than ‘echo "$foo"’
if $foo can contain arbitrary characters.
* lisp/Makefile.in (TAGS): Use ‘ls’, not ‘echo’, to avoid ‘\’ issues.
* doc/lispref/two-volume.make (vol1.pdf):
* test/etags/make-src/Makefile (web ftp publish):
Use ‘printf’ rather than ‘echo -e’.
2015-10-11 01:03:49 +00:00
|
|
|
printf >&2 '%s\n' "$0: please run this command in the main source directory"
|
2014-05-16 15:49:13 +00:00
|
|
|
exit 1
|
|
|
|
}
|
|
|
|
|
Use ‘echo’ safely with ‘\’ or leading ‘-’
POSIX says that ‘echo FOO’ produces implementation-defined output
if FOO contains leading ‘-’, or ‘\’ anywhere, so don’t assume GNU
behavior in that case.
* Makefile.in (removenullpaths): Remove.
(epaths-force): Rewrite to avoid the need for ‘echo’.
(install-etc): Be clearer about escaping the shell metacharacters
‘\’ and ‘$’.
* Makefile.in (install-arch-indep, install-etcdoc):
* admin/charsets/mapconv, admin/merge-gnulib, admin/merge-pkg-config:
* admin/quick-install-emacs, build-aux/gitlog-to-emacslog:
* configure.ac, lib-src/rcs2log, make-dist:
* src/Makefile.in (lisp.mk):
Don’t assume ‘echo’ outputs ‘\’ and leading ‘-’ unscathed.
For example, use ‘printf '%s\n' "$foo"’ rather than ‘echo "$foo"’
if $foo can contain arbitrary characters.
* lisp/Makefile.in (TAGS): Use ‘ls’, not ‘echo’, to avoid ‘\’ issues.
* doc/lispref/two-volume.make (vol1.pdf):
* test/etags/make-src/Makefile (web ftp publish):
Use ‘printf’ rather than ‘echo -e’.
2015-10-11 01:03:49 +00:00
|
|
|
printf >&2 '%s\n' "$0: copying $dir/pkg.m4 to m4/pkg.m4"
|
2014-05-16 15:49:13 +00:00
|
|
|
|
2020-12-31 11:11:31 +00:00
|
|
|
cp "$dir"/pkg.m4 m4
|