"checkit_tiff" is an incredibly fast conformance checker for baseline TIFFs (with various extensions), see http://andreas-romeyke.de
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.

71 lines
3.7KB

  1. Q: "make" reports "usage: git rev-list [OPTION] …"
  2. A: the Makefile uses version.mk to build a version information for the tool.
  3. In that case you should comment out the lines in version.mk and set
  4. REPO_REVISION manually
  5. Q: I did not have "peg" and my config_dsl.grammar.c has zero size and there are
  6. compile errors.
  7. A: remove that file and use "git checkout config_dsl.grammar.c" to restore it
  8. from repository. Try to avoid "make distclean", because it erases the file.
  9. Q: My C-compiler reports error-messages like "cc: error: unrecognized command
  10. line option '-fsanitize=undefined'"
  11. A: You use an older GCC variant. Try 'SANITIZE="" make'
  12. Q: How can I compile a windows version of your program?
  13. A: I have only tested creating Windows executables using the crosscompiler
  14. minGW under Debian Jessie. You need the installed mingw-w64-x86-32 packages,
  15. also you need to download and extract libpcre. in
  16. libpcre (pcre-8.37), call "./configure --host=i686-w64-mingw32
  17. --disable-win32-io --disable-shared -enable-static" and "make -j 4". Change
  18. into checkit-tiff/build, call:
  19. "cmake -DCMAKE_TOOLCHAIN_FILE=toolchain-mingw32.cmake ../src/
  20. -DPCRE_LIBRARY=~/Downloads/pcre-8.37/.libs/libpcre.a
  21. -DPCRE_INCLUDE_DIR=~/Downloads/pcre-8.37/ ../src/" and "make -j 4"
  22. A2: I have only tested creating Windows executables using the crosscompiler
  23. minGW under Debian Jessie. You need the installed mingw-w64-x86-64 packages,
  24. also you need to download and extract libtiff and libpcre. in
  25. libpcre (pcre-8.37), call "./configure --host=x86_64-w64-mingw32
  26. --disable-win32-io --disable-shared -enable-static" and "make -j 4". Change
  27. into checkit-tiff/build, call:
  28. "cmake -DCMAKE_TOOLCHAIN_FILE=toolchain-mingw64.cmake ../src/
  29. -DPCRE_LIBRARY=~/Downloads/pcre-8.37/.libs/libpcre.a
  30. -DPCRE_INCLUDE_DIR=~/Downloads/pcre-8.37/ ../src/" and "make -j 4"
  31. Q: How to compile to Javascript?
  32. A: Use emscripten, do same steps as above but with "emconfigure
  33. ./configure...". Compile checkit_tiff with ff. options:
  34. $> emcmake cmake
  35. -DCMAKE_C_COMPILER=$(which emcc)
  36. -DPCRE_LIBRARY=~/Downloads/pcre-8.37/.libs/libpcre.a
  37. -DPCRE_INCLUDE_DIR=~/Downloads/pcre-8.37/ -DCMAKE_C_FLAGS="-Oz -s
  38. TOTAL_MEMORY=400000000" ../src/"
  39. $> make -j 4
  40. $> js checkit_tiff.js -c ../tiffs_should_pass/minimal_valid.tiff ../example_configs/cit_tiff6_baseline_SLUB.cfg
  41. Q: Where are older TIFF specs?
  42. A: take a look to:
  43. TIFF 4: https://web.archive.org/web/20050323073243/http://palimpsest.stanford.edu/bytopic/imaging/std/tiff4.html
  44. TIFF 5: https://web.archive.org/web/20050323073243/http://palimpsest.stanford.edu/bytopic/imaging/std/tiff5.html
  45. Q: I am using cmake, but it fails with "CMake Error: your CXX compiler:
  46. "CMAKE_CXX_COMPILER-NOTFOUND" was not found. Please set CMAKE_CXX_COMPILER
  47. to a valid compiler path or name". But your program is C only, why I need a
  48. C++compiler then?
  49. A: cmake uses C++-compiler for its checks. Sorry, you need a C++ then.
  50. Q: Your tool processes very slow, why?
  51. A: No, the tool is optimized for very fast processing. On a NVME-based SSD it
  52. processes 550 TIFF files (2,9GB) in less 3 seconds. We have tested it also
  53. on our NFS based filesystem with similar fast results. There is only one
  54. cornercase, if you have a broken TIFF with very large IFDs. Because
  55. checkit_tiff tries to find all errors in a given TIFF file it does not use
  56. early aborts than some other tools.
  57. Q: I have a fully destroyed TIFF because checkit_tiff reports IFD errors. Is
  58. there any chance to repair the file?
  59. A: You could give "fixit_tiff" a try:
  60. http://andreas-romeyke.de/software.html#_fixit_tiff
  61. This project comes with some helper tools to find lost IFDs and could
  62. fix some typical errors in broken TIFF files.