On Sat, Sep 7, 2024 at 12:16 PM Roger Leigh via Tiff <[email protected]> wrote: > > hum, ok if that's thought to be controversial / risky, I'm leaning to > reverting this merge request and let other people deal with the issues it > tried to solve. I don't care about autoconf builds when I've the chance to be > able to use CMake instead (if that was just me, I would get rid of autoconf > support from libtiff to only keep the CMake one, and just maintain one single > build system, but that's a battle for another time), and I don't want to be > bothered with autoconf related issues and having to do several RCs due to > that. > > I would prefer it if we could drop the autotools at this point and simply use > CMake.
you can also consider using meson: * it's faster * the syntax is so much nicer, easy to read * it supports a lot of systems * few files to look into (only meson.build in some directories) * options are in a specific file * it works without using hacks, e.g. you want to install a dll ? it creates automatically the dll, the import lib and they are installed in the correct directories * there are modules for precompiled headers, coverage, valgrind, and some libraries support like boost, gnome, etc... * Visual Studio and Xcode backends are supported in addition to ninja * based on python3 which is widely available regards Vincent Torri _______________________________________________ Tiff mailing list [email protected] https://lists.osgeo.org/mailman/listinfo/tiff
