From: Andrew Pennebaker <andrew.pennebaker@gmail.com>
To: bug-gnulib@gnu.org
Subject: cmake support
Date: Sat, 5 Jan 2019 10:31:35 -0600 [thread overview]
Message-ID: <CAHXt_SW31gP2bZbhLH53y6C6TAjoPuEBeQEAp2F2JyddMySugA@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 381 bytes --]
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.
--
Cheers,
Andrew
[-- Attachment #2: Type: text/html, Size: 589 bytes --]
next reply other threads:[~2019-01-05 16:34 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-05 16:31 Andrew Pennebaker [this message]
2019-01-05 17:49 ` cmake support Paul Eggert
2019-01-05 17:53 ` Bruno Haible
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=CAHXt_SW31gP2bZbhLH53y6C6TAjoPuEBeQEAp2F2JyddMySugA@mail.gmail.com \
--to=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).