Commit 2d0c68735b52d33e071f2895309c4dc6944b464d
1 parent
46728e49
README note about debugging
Showing
1 changed file
with
4 additions
and
0 deletions
README-maintainer.md
| 1 | # Release Reminders | 1 | # Release Reminders |
| 2 | 2 | ||
| 3 | +* For debugging: | ||
| 4 | + ``` | ||
| 5 | + ./configure CFLAGS="-g" CXXFLAGS="-g" --enable-werror --disable-shared | ||
| 6 | + ``` | ||
| 3 | * 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`. | 7 | * 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`. |
| 4 | * 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`. | 8 | * 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`. |
| 5 | * Run tests with sanitize address enabled: | 9 | * Run tests with sanitize address enabled: |