From: Paul Eggert <eggert@cs.ucla.edu>
To: Andrew Pennebaker <andrew.pennebaker@gmail.com>, bug-gnulib@gnu.org
Subject: Re: cmake support
Date: Sat, 5 Jan 2019 09:49:59 -0800 [thread overview]
Message-ID: <cfd3c4fc-c1bb-a79f-fb1c-7d726e1a1256@cs.ucla.edu> (raw)
In-Reply-To: <CAHXt_SW31gP2bZbhLH53y6C6TAjoPuEBeQEAp2F2JyddMySugA@mail.gmail.com>
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.
It would also be helpful for Gnulib to work better with GNU Make, while we're
thinking about what to add to our to-do list. (I contributed some changes in
that area, but I'm sure more improvements would be helpful.) The problem here
mainly is a shortage of volunteers to do the work.
next prev parent reply other threads:[~2019-01-05 17:50 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 [this message]
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=cfd3c4fc-c1bb-a79f-fb1c-7d726e1a1256@cs.ucla.edu \
--to=eggert@cs.ucla.edu \
--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).