diff options
author | Jay Berkenbilt <ejb@ql.org> | 2020-04-04 03:34:45 +0200 |
---|---|---|
committer | Jay Berkenbilt <ejb@ql.org> | 2020-04-04 03:39:44 +0200 |
commit | 2100b4ce152e9c70b3ce8760112d5a24ead4e52d (patch) | |
tree | 0dc298af6870f9635dd4b52b9ec8a528b01e01f6 /manual/qpdf-manual.xml | |
parent | 6a4117add996eeaaf330bd700e30380295daab93 (diff) | |
download | qpdf-2100b4ce152e9c70b3ce8760112d5a24ead4e52d.tar.zst |
Allow qpdf to be built on systems without wchar_t (fixes #406)
Diffstat (limited to 'manual/qpdf-manual.xml')
-rw-r--r-- | manual/qpdf-manual.xml | 10 |
1 files changed, 10 insertions, 0 deletions
diff --git a/manual/qpdf-manual.xml b/manual/qpdf-manual.xml index e22edc2d..83cb6bf9 100644 --- a/manual/qpdf-manual.xml +++ b/manual/qpdf-manual.xml @@ -240,6 +240,16 @@ make <filename>README-windows.md</filename>. </para> <para> + While <type>wchar_t</type> is part of the C++ standard, qpdf uses + it in only one place in the public API, and it's just in a helper + function. It is possible to build qpdf on a system that doesn't + have <type>wchar_t</type>, and it's also possible to compile a + program that uses qpdf on a system without <type>wchar_t</type> as + long as you don't call that one method. This is a very unusual + situation. For a detailed discussion, please see the top-level + README.md file in qpdf's source distribution. + </para> + <para> There are some other things you can do with the build. Although qpdf uses <application>autoconf</application>, it does not use <application>automake</application> but instead uses a |