OpenSystemsDevelopment / qpdf

Commit ffb9db9614743327277f70f11f84d3965e7a510c

Authored by Jay Berkenbilt
1 parent fe0944a5

static runtime didn't work 


git-svn-id: svn+q:///qpdf/trunk@788 71b93d88-0707-0410-a8cf-f5a4172ac649
Inline Side-by-side
Showing 1 changed file with 8 additions and 2 deletions
README.windows
  View file @ffb9db9
... ... @@ -28,14 +28,17 @@ From your MSYS prompt, run
28 28 ./configure --disable-test-compare-images --enable-build-external-libs --with-buildrules=mingw
29 29 make
30 30  
31   -When done, you should copy the gcc runtime dll into the libqpdf/build
  31 +When done, you should copy the gcc runtime DLL into the libqpdf/build
32 32 directory. You can find the path to it by running
33 33  
34 34 objdump -p qpdf/build/qpdf.exe | grep DLL
35 35 type -P libgcc_s_dw2-1.dll
36 36  
37 37 replacing libgcc_s_dw2-1.dll with whatever gcc DLL is shown, if
38   -different.
  38 +different. For an unknown reason, building with -static-libgcc
  39 +results in executables that fail their test suites. I'm guessing this
  40 +has to do with static data being duplicated between the DLL and the
  41 +executable, but I don't really know.
39 42  
40 43 From your cygwin prompt, add the absolute path to the libqpdf/build
41 44 directory to your PATH. Make sure you can run the qpdf command by
... ... @@ -92,3 +95,6 @@ A release version of qpdf is built by default. You will probably have
92 95 to edit msvc.mk to change /MD to /MDd to build a debugging version.
93 96 It has also been attempted to build qpdf with /MT, but it does not
94 97 pass its test suite in this configuration. I have not investigated.
  98 +Perhaps this is the same issue as with -static-libgcc with mingw. In
  99 +both cases, statically linking the runtime results in non-working
  100 +executables/DLL.
... ...