OpenSystemsDevelopment / qpdf

Commit 238996667c07611a75385e0c430df2debc1b3f5f

Authored by Jay Berkenbilt
1 parent 49c7681c

Describe mingw-w64 workaround 

The latest automated mingw-w64 build's libstdc++-6.dll crashes with
qpdf 4.1.0, but libstdc++-6.dll can be replaced with one from a newer
build.
Inline Side-by-side
Showing 1 changed file with 13 additions and 0 deletions
README-windows.txt
  View file @2389966
... ... @@ -33,6 +33,19 @@ mingw-w64-bin_i686-mingw_yyyymmdd.zip. The compiler binaries are
33 33 C:\MinGW-w64, and add C:\MinGW-w64\bin and C:\MinGW-w64\lib\mingw to
34 34 the path.
35 35  
  36 +Starting in version 4.1.0, qpdf uses std::setprecision and std::fixed
  37 +to format floating point numbers, and using one or both of those
  38 +causes a crash with the version of libstdc++-6 that is included with
  39 +mingw-w64-bin_i686-mingw_20111220.zip, which appears to be the latest
  40 +mingw-hosted version of mingw that targets w64 that includes the full
  41 +toolchain including all the DLL creation tools. To work around this,
  42 +for my personal build, I have grabbed
  43 +x86_64-w64-mingw32-gcc-4.7.2-release-win64_rubenvb.7z from the
  44 +personal builds and just extracted libstdc++-6.dll from there and used
  45 +that to replace the one in the 20111220 version, which is based on
  46 +4.7.0. That particular workaround results in a Windows-hosted 64-bit
  47 +targetted mingw that can build a qpdf that passes its test suite.
  48 +
36 49 As of this writing, the image comparison tests confuse ghostscript in
37 50 cygwin, but there's a chance they might work at some point. If you
38 51 want to run them, you need ghostscript and tiff utils as well, and you
... ...