diff options
author | Jay Berkenbilt <ejb@ql.org> | 2017-08-26 01:58:18 +0200 |
---|---|---|
committer | Jay Berkenbilt <ejb@ql.org> | 2017-08-26 01:58:18 +0200 |
commit | 2d0c68735b52d33e071f2895309c4dc6944b464d (patch) | |
tree | f138732412cc772dc063940a07890a0a9f979909 | |
parent | 46728e49cc4b9c151f14d66708dbfcb069f44874 (diff) | |
download | qpdf-2d0c68735b52d33e071f2895309c4dc6944b464d.tar.zst |
README note about debugging
-rw-r--r-- | README-maintainer.md | 4 |
1 files changed, 4 insertions, 0 deletions
diff --git a/README-maintainer.md b/README-maintainer.md index 41e1e903..6d237fbd 100644 --- a/README-maintainer.md +++ b/README-maintainer.md @@ -1,5 +1,9 @@ # Release Reminders +* For debugging: + ``` + ./configure CFLAGS="-g" CXXFLAGS="-g" --enable-werror --disable-shared + ``` * Test for binary compatibility. The easiest way to do this is to check out the last release, run the test suite, check out the new release, run `make build_libqpdf`, check out the old release, and run `make check NO_REBUILD=1`. * When making a release, always remember to run large file tests and image comparison tests (`--enable-test-compare-images` `--with-large-file-test-path=/path`). For Windows, use a Windows style path, not an MSYS path for large files. For a major release, consider running a spelling checker over the source code to catch errors in variable names, strings, and comments. Use `ispell -p ispell-words`. * Run tests with sanitize address enabled: |