|Subject:||Re: cmake support|
|Date:||Sat, 5 Jan 2019 20:22:01 -0600|
On Saturday, January 5, 2019 6:53:06 PM CET Bruno Haible wrote:
> Andrew Pennebaker wrote:
> > Could we improve how gnulib integrates with downstream projects, to make
> > it
> > easier to work with different build tools? In particular, would be helpful
> > for gnulib to easily work with cmake projects.
> > In my case, I have an application that needs openat(), and I already have
> > a
> > complex cmake configuration that would be difficult to rewrite in terms of
> > autotools.
> I don't think we will spend time to make gnulib-tool generate cmake
> 1. Because the GNU build system is based on Autotools.
> 2. Because many people say that cmake is a horror to use. 
That is not an argument. You can find similar horror stories about autotools:
> But gnulib-tool by design creates a subdirectory, and you can yourself
> - add a simple configure.ac to that subdirectory, as outlined in the
> documentation ,
When I needed it 10 years ago, I was able to get around this limitation by
using the --create-testdir option of gnulib-tool. It created a directory
with configure script that (after running make) produced a static library.
I am not sure if this approach had any side effects, like turning on debug
build, but I was at least not forced to create configure.ac etc.
> - integrate this subdirectory with cmake through an 'ExternalProject' .
> If, during this process, you encounter pain points that require (small)
> gnulib-tool changes, please come back to us and report them.
|[Prev in Thread]||Current Thread||[Next in Thread]|