bug-gnulib@gnu.org mirror (unofficial)
 help / color / mirror / Atom feed
From: Bruno Haible <bruno@clisp.org>
To: bug-gnulib@gnu.org
Cc: Andrew Pennebaker <andrew.pennebaker@gmail.com>
Subject: Re: cmake support
Date: Sat, 05 Jan 2019 18:53:06 +0100	[thread overview]
Message-ID: <3784148.CO4aUIPAkI@omega> (raw)
In-Reply-To: <CAHXt_SW31gP2bZbhLH53y6C6TAjoPuEBeQEAp2F2JyddMySugA@mail.gmail.com>

Hi,

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
configurations.
  1. Because the GNU build system is based on Autotools.
  2. Because many people say that cmake is a horror to use. [1][2]

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 [3],
  - integrate this subdirectory with cmake through an 'ExternalProject' [4].

If, during this process, you encounter pain points that require (small)
gnulib-tool changes, please come back to us and report them.

Bruno

[1] https://www.reddit.com/r/cpp/comments/4flb8z/fighting_through_a_cmake_hell/
[2] https://www.reddit.com/r/cpp/comments/7yps20/its_time_to_do_cmake_right/
[3] https://www.gnu.org/software/gnulib/manual/html_node/Initial-import.html
[4] https://stackoverflow.com/questions/5971921/building-a-library-using-autotools-from-cmake



  parent reply	other threads:[~2019-01-05 17:53 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-01-05 16:31 cmake support Andrew Pennebaker
2019-01-05 17:49 ` Paul Eggert
2019-01-05 17:53 ` Bruno Haible [this message]
2019-01-05 18:32   ` Kamil Dudka
2019-01-06  2:22     ` Andrew Pennebaker
2019-01-06  6:54       ` Bruno Haible
2019-01-06  9:38       ` Kamil Dudka
2019-01-08  1:46         ` Andrew Pennebaker
2019-01-08  7:39           ` Kamil Dudka
2019-01-08  8:05           ` Bruno Haible

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://lists.gnu.org/mailman/listinfo/bug-gnulib

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=3784148.CO4aUIPAkI@omega \
    --to=bruno@clisp.org \
    --cc=andrew.pennebaker@gmail.com \
    --cc=bug-gnulib@gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).