From: Kamil Dudka <kdudka@redhat.com>
To: Andrew Pennebaker <andrew.pennebaker@gmail.com>
Cc: Bruno Haible <bruno@clisp.org>, bug-gnulib@gnu.org
Subject: Re: cmake support
Date: Sun, 06 Jan 2019 10:38:02 +0100 [thread overview]
Message-ID: <6589477.oZLneipaSj@kdudka-nb> (raw)
In-Reply-To: <CAHXt_SVikVT7qCuo+=NKJf45qp49boEoTzBYUtx_KKNQDUmVHw@mail.gmail.com>
On Sunday, January 6, 2019 3:22:01 AM CET Andrew Pennebaker wrote:
> Ach, I've made a career out of not having to know autotools! ./configure &&
> make && [sudo] make install were black boxes as far as I was concerned.
>
> So be it, I'll spend some time reading up this weekend and see how far I
> get. MSVC integration will become more interesting, but I suppose I can
> disable Gnulib for targets that don't actually need it. This is what I get
> for dipping my toes in CloudABI and introducing dprintf(), openat() to my
> projects :P
>
> Would be nice to offer NetBSD-style packages for MINIX and SmartOS, in
> order to make Gnulib easier to install to a standard include path like with
> other development libraries.
I am afraid that there is no OS distribution that would install Gnulib to
a standard include (and library) path and this is most likely not going to
change because gnulib's developers do not want gnulib to be used this way:
https://www.gnu.org/software/gnulib/manual/html_node/Library-vs-Reusable-Code.html#Library-vs-Reusable-Code
Kamil
> On Sat, Jan 5, 2019 at 12:31 PM Kamil Dudka <kdudka@redhat.com> wrote:
> > On Saturday, January 5, 2019 6:53:06 PM CET Bruno Haible wrote:
> > > 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]
> >
> > That is not an argument. You can find similar horror stories about
> >
> > autotools:
> > http://voices.canonical.com/jussi.pakkanen/2011/09/13/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 [3],
> >
> > 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.
> >
> > Kamil
> >
> > > - 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-autot
> > o
> >
> > > ols-from-cmake
next prev parent reply other threads:[~2019-01-06 9:37 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
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 [this message]
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=6589477.oZLneipaSj@kdudka-nb \
--to=kdudka@redhat.com \
--cc=andrew.pennebaker@gmail.com \
--cc=bruno@clisp.org \
--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).