2024.02.03 15:00 "[Tiff] www.libtiff.org is restored", by Bob Friesenhahn
-
2024.02.03 15:20 "Re: [Tiff] www.libtiff.org is restored", by Even Rouault
-
2024.02.03 16:15 "Re: [Tiff] www.libtiff.org is restored", by Bob Friesenhahn
- 2024.02.03 16:31 "Re: [Tiff] www.libtiff.org is restored", by Miguel Medalha
-
2024.02.03 23:21 "Re: [Tiff] www.libtiff.org is restored", by Patrice Fournier
- 2024.02.03 23:36 "Re: [Tiff] www.libtiff.org is restored", by Paul Hemmer
- 2024.02.04 13:59 "Re: [Tiff] www.libtiff.org is restored", by Bob Friesenhahn
- 2024.02.04 14:48 "Re: [Tiff] www.libtiff.org is restored", by Bob Friesenhahn
-
2024.02.03 16:15 "Re: [Tiff] www.libtiff.org is restored", by Bob Friesenhahn
- 2024.02.07 03:15 "Re: [Tiff] www.libtiff.org is restored", by Edward Lam
- 2024.03.15 18:34 "Re: [Tiff] libtiff | tiffcrop produces wrong output when 'raw' and 'rgb' parameters are used with jpeg compression (parameters have reverse effect) (#228)", by Miguel Medalha
- 2024.04.09 15:49 "[Tiff] www.libtiff.org is restored", by Michael Vetter
2024.02.04 16:11 "Re: [Tiff] www.libtiff.org is restored", by William Bader
>If the utilities are again maintained by the libtiff project, they need to be in a separate repository, with its own build process
Shouldn't the build for the utilities be simpler than the build for libtiff because the utilities only use tiffconf.h instead of generating it?
The utilities should be best use examples for libtiff, and something might be wrong if they end up needing a massively complicated build process.
William