Include libglnx-config.h instead of config.h
This avoids colliding with a config.h generated by a parent Meson
project.
In the Meson build system, we generate libglnx-config.h by doing our
own checks, so we want to avoid it colliding.
In the Autotools build system, we assume that the parent project will
generate its own config.h that contains the results of LIBGLNX_CONFIGURE,
and create a forwarding header libglnx-config.h in the $(top_builddir)
(so that it is next to config.h).
Note that after updating libglnx in an Autotools non-recursive-Make
project (libostree, flatpak, flatpak-builder) it will be necessary to
re-run autogen.sh.
Signed-off-by:
Simon McVittie <smcv@collabora.com>
Showing
- .gitignore 2 additions, 0 deletions.gitignore
- Makefile-libglnx.am 5 additions, 1 deletionMakefile-libglnx.am
- glnx-backports.c 1 addition, 1 deletionglnx-backports.c
- glnx-console.c 1 addition, 1 deletionglnx-console.c
- glnx-dirfd.c 1 addition, 1 deletionglnx-dirfd.c
- glnx-errors.c 1 addition, 1 deletionglnx-errors.c
- glnx-fdio.c 1 addition, 1 deletionglnx-fdio.c
- glnx-local-alloc.c 1 addition, 1 deletionglnx-local-alloc.c
- glnx-lockfile.c 1 addition, 1 deletionglnx-lockfile.c
- glnx-missing-syscall.h 1 addition, 1 deletionglnx-missing-syscall.h
- glnx-shutil.c 1 addition, 1 deletionglnx-shutil.c
- glnx-xattrs.c 1 addition, 1 deletionglnx-xattrs.c
- meson.build 1 addition, 1 deletionmeson.build
- tests/libglnx-testlib.c 1 addition, 1 deletiontests/libglnx-testlib.c
- tests/test-libglnx-errors.c 1 addition, 1 deletiontests/test-libglnx-errors.c
- tests/test-libglnx-fdio.c 1 addition, 1 deletiontests/test-libglnx-fdio.c
- tests/test-libglnx-macros.c 1 addition, 1 deletiontests/test-libglnx-macros.c
- tests/test-libglnx-shutil.c 1 addition, 1 deletiontests/test-libglnx-shutil.c
- tests/test-libglnx-xattrs.c 1 addition, 1 deletiontests/test-libglnx-xattrs.c
Loading
Please register or sign in to comment