aboutsummaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorJay Berkenbilt <ejb@ql.org>2009-10-11 05:22:54 +0200
committerJay Berkenbilt <ejb@ql.org>2009-10-11 05:22:54 +0200
commitffb9db9614743327277f70f11f84d3965e7a510c (patch)
tree7f67ad6ec1a5c2628d2e637a461d498789383fbd
parentfe0944a5125f3cfc9ca046d06a4ed2f4990aca80 (diff)
downloadqpdf-ffb9db9614743327277f70f11f84d3965e7a510c.tar.zst
static runtime didn't work
git-svn-id: svn+q:///qpdf/trunk@788 71b93d88-0707-0410-a8cf-f5a4172ac649
-rw-r--r--README.windows10
1 files changed, 8 insertions, 2 deletions
diff --git a/README.windows b/README.windows
index 23aa52c8..be7de0b3 100644
--- a/README.windows
+++ b/README.windows
@@ -28,14 +28,17 @@ From your MSYS prompt, run
./configure --disable-test-compare-images --enable-build-external-libs --with-buildrules=mingw
make
-When done, you should copy the gcc runtime dll into the libqpdf/build
+When done, you should copy the gcc runtime DLL into the libqpdf/build
directory. You can find the path to it by running
objdump -p qpdf/build/qpdf.exe | grep DLL
type -P libgcc_s_dw2-1.dll
replacing libgcc_s_dw2-1.dll with whatever gcc DLL is shown, if
-different.
+different. For an unknown reason, building with -static-libgcc
+results in executables that fail their test suites. I'm guessing this
+has to do with static data being duplicated between the DLL and the
+executable, but I don't really know.
From your cygwin prompt, add the absolute path to the libqpdf/build
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
to edit msvc.mk to change /MD to /MDd to build a debugging version.
It has also been attempted to build qpdf with /MT, but it does not
pass its test suite in this configuration. I have not investigated.
+Perhaps this is the same issue as with -static-libgcc with mingw. In
+both cases, statically linking the runtime results in non-working
+executables/DLL.