add some notes on building for Windows

feature/tap-sh
William Pitcock 2017-06-16 21:15:23 -05:00
parent 864b14e5b9
commit 037d15210c
1 changed files with 19 additions and 1 deletions

View File

@ -67,7 +67,7 @@ do let us know, but also make sure that the .pc files are valid and follow the r
the [pkg-config tutorial][fd-tut], as most likely fixing them to follow the specified the [pkg-config tutorial][fd-tut], as most likely fixing them to follow the specified
rules will solve the problem. rules will solve the problem.
## compiling `pkgconf` and `libpkgconf` ## compiling `pkgconf` and `libpkgconf` on UNIX
pkgconf is basically compiled the same way any other autotools-based project is pkgconf is basically compiled the same way any other autotools-based project is
compiled: compiled:
@ -88,6 +88,24 @@ flags like so:
$ make $ make
$ sudo make install $ sudo make install
## compiling `pkgconf` and `libpkgconf` with CMake (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.
$ mkdir build
$ cd build
$ cmake ..
$ make
$ sudo make install
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
on path relocation.
## pkg-config symlink
If you want pkgconf to be used when you invoke `pkg-config`, you should install a If you want pkgconf to be used when you invoke `pkg-config`, you should install a
symlink for this. We do not do this for you, as we believe it is better for vendors symlink for this. We do not do this for you, as we believe it is better for vendors
to make this determination themselves. to make this determination themselves.