- 2015.06.16 17:51 "Re: [Tiff] CMake support for building libtiff", by Lee Howard
- 2015.06.17 03:16 "Re: [Tiff] CMake support for building libtiff", by Bob Friesenhahn
-
2015.06.17 22:38 "Re: [Tiff] CMake support for building libtiff", by Roger Leigh
-
2015.06.18 22:08 "Re: [Tiff] CMake support for building libtiff", by Roger Leigh
-
2015.06.19 11:54 "Re: [Tiff] CMake support for building libtiff", by Roger Leigh
-
2015.07.02 07:10 "[Tiff] [patch] Additional CMake fixes", by Roger Leigh
- 2015.07.04 22:10 "Re: [Tiff] [patch] Additional CMake fixes", by Bob Friesenhahn
-
2015.08.29 11:34 "[Tiff] [patch] Docs for cmake build and some minor tweaks", by Roger Leigh
- 2015.08.29 15:36 "Re: [Tiff] [patch] Docs for cmake build and some minor tweaks", by Bob Friesenhahn
-
2015.08.31 15:12 "[Tiff] [patch] cmake fixes", by
- 2015.08.31 15:34 "Re: [Tiff] [patch] cmake fixes", by Bob Friesenhahn
-
2015.07.02 07:10 "[Tiff] [patch] Additional CMake fixes", by Roger Leigh
- 2015.06.19 13:53 "Re: [Tiff] CMake support for building libtiff", by Rhys Thomas
-
2015.06.19 11:54 "Re: [Tiff] CMake support for building libtiff", by Roger Leigh
-
2015.06.19 13:41 "Re: [Tiff] 4.0.4beta: Symbol differences on Unix and Windows", by Bob Friesenhahn
- 2015.06.18 21:56 "[Tiff] 4.0.4beta: Symbol differences on Unix and Windows", by Roger Leigh
-
2015.06.18 22:08 "Re: [Tiff] CMake support for building libtiff", by Roger Leigh
- 2015.06.25 02:32 "Re: [Tiff] CMake support for building libtiff", by Bob Friesenhahn
2015.06.17 22:38 "Re: [Tiff] CMake support for building libtiff", by Roger Leigh
On 16/06/2015 14:39, Roger Leigh wrote:
Would there be any interest in having support for building libtiff with CMake? This would allow for easier building on Windows and other platforms since it can generate build files for a whole host of different build tools and IDEs. For example, on Windows it generates project files for specific visual studio versions. On Unix it generates standard Makefiles. It also allows seamless integration of libtiff into libtiff-using projects (embedded directly or downloaded and build as a "superbuild"), and is quite a bit simpler to manage and use than the autotools (I switched after 15 years of autotools use).
I'm happy to do the work and submit this for inclusion. I just wanted to check if this was something which was of interest for others as well, and which wasn't totally objectionable to the maintainers.
Thanks all for the responses. I'll do this over the next few days. [It's not just for the sake of it; I need the support for a work project, in particular better Windows support.]
Just to give you an idea of what this will look like, I've attached the fruits of my days' labour, made against the 4.0.4 beta release. This is a conversion of
- configure.ac including all the portability checks and retaining exact compatibility WRT the header generation
- port/Makefile.am
- libtiff/Makefile.am
- tools/Makefile.am
- In other words, sufficient to build libtiff (shared and static) plus the tools. It doesn't have install rules yet, so "make install" does nothing.
To try out:
- apply the patch
- make a build directory and change into it
- run "cmake /path/to/libtiff/source"
- run "make"
- Any comments would be useful at this stage. It's obviously not fully functional, but the lion's share of the work is done; I'll get the rest of the Makefile.ams converted tomorrow and test on a series of different platforms (all work on FreeBSD so far)
Regards,
Roger