docs: mention Meson instead of CMake for Win build

Fixes #233
master
Andrea Pappacoda 2021-12-11 14:49:05 +01:00
parent 1044bb57ca
commit 6109e06089
Signed by untrusted user: tachi
GPG Key ID: A8A128A8AB1CEE49
2 changed files with 8 additions and 11 deletions

View File

@ -111,17 +111,15 @@ flags like so:
$ make
$ sudo make install
## compiling `pkgconf` and `libpkgconf` with CMake (usually for Windows)
## compiling `pkgconf` and `libpkgconf` with Meson (usually for Windows)
pkgconf is compiled using CMake on Windows. In theory, you could also use CMake to build
on UNIX, but this is not recommended at this time as it pkgconf is typically built much earlier
than CMake.
pkgconf is compiled using [Meson](https://mesonbuild.com) on Windows. In theory, you could also use
Meson to build on UNIX, but this is not recommended at this time as it pkgconf is typically built
much earlier than Meson.
$ mkdir build
$ cd build
$ cmake ..
$ make
$ sudo make install
$ meson setup build -Dtests=false
$ meson compile -C build
$ meson install -C build
There are a few defines such as SYSTEM_LIBDIR, PKGCONFIGDIR and SYSTEM_INCLUDEDIR.
However, on Windows, the default PKGCONFIGDIR value is usually overridden at runtime based

View File

@ -2,8 +2,7 @@
#define LIBPKGCONF_LIBPKGCONF_API_H
/* Makefile.am specifies visibility using the libtool option -export-symbols-regex '^pkgconf_'
* Unfortunately, that is not available when building with cmake, so use attributes instead,
* in a way that doesn't depend on any cmake magic.
* Unfortunately, that is not available when building with meson, so use attributes instead.
*/
#if defined(PKGCONFIG_IS_STATIC)
# define PKGCONF_API