diff options
author | Jay Berkenbilt <ejb@ql.org> | 2019-06-22 01:57:21 +0200 |
---|---|---|
committer | Jay Berkenbilt <ejb@ql.org> | 2019-06-22 04:29:31 +0200 |
commit | ade8e2cd7fd6629cbbb3caf17e21b396e08ac288 (patch) | |
tree | d9e8f810f42564ba900d16b1427927d3201de6e2 /README.md | |
parent | 45dac410b5f427bc8c8ea39cc04cc55ddb825671 (diff) | |
download | qpdf-ade8e2cd7fd6629cbbb3caf17e21b396e08ac288.tar.zst |
Remove unused gcc-linux make rules
I don't want to maintain them or make anyone think they should be used.
Diffstat (limited to 'README.md')
-rw-r--r-- | README.md | 2 |
1 files changed, 1 insertions, 1 deletions
@@ -59,7 +59,7 @@ QPDF is known to build and pass its test suite with mingw (latest version tested # Additional Notes on Build -QPDF's build system, inspired by [abuild](http://www.abuild.org), can optionally use its own built-in rules rather than using libtool and obeying the compiler specified with configure. This can be enabled by passing `--with-buildrules=buildrules` where buildrules corresponds to one of the `.mk` files (other than `rules.mk`) in the make directory. This should never be necessary on a UNIX system, but may be necessary on a Windows system. See [README-windows.md](README-windows.md) for details. There is a `gcc-linux.mk` file enable `gcc-linux` build rules, but it is intended to help test the build system; Linux users should build with the `libtools` rules, which are enabled by default. +QPDF's build system, inspired by [abuild](http://www.abuild.org), can optionally use its own built-in rules rather than using libtool and obeying the compiler specified with configure. This can be enabled by passing `--with-buildrules=buildrules` where buildrules corresponds to one of the `.mk` files (other than `rules.mk`) in the make directory. This should never be necessary on a UNIX system, but may be necessary on a Windows system. See [README-windows.md](README-windows.md) for details. The QPDF package provides some executables and a software library. A user manual can be found in the "doc" directory. The docbook sources to the user manual can be found in the `manual` directory. |