From: Pablo Neira Ayuso <pablo@netfilter.org>
To: Phil Sutter <phil@nwl.cc>, netfilter-devel@vger.kernel.org
Subject: Re: [PATCH libmnl] build: do not build documentation automatically
Date: Sun, 13 Oct 2024 10:21:24 +0200 [thread overview]
Message-ID: <ZwuDBGBiRqw0e2L3@calendula> (raw)
In-Reply-To: <ZwsANQhOyYrEGTip@orbyte.nwl.cc>
On Sun, Oct 13, 2024 at 01:03:17AM +0200, Phil Sutter wrote:
> On Sat, Oct 12, 2024 at 11:26:32PM +0200, Pablo Neira Ayuso wrote:
> > On Sat, Oct 12, 2024 at 09:54:04PM +0200, Phil Sutter wrote:
> > > Hi Pablo,
> > >
> > > On Sat, Oct 12, 2024 at 07:15:21PM +0200, Pablo Neira Ayuso wrote:
> > > > Make it option, after this update it is still possible to build the
> > > > documentation on demand via:
> > > >
> > > > cd doxygen
> > > > make
> > >
> > > This is rather unelegant in an autotools-project. You probably did
> > > consider setting 'with_doxygen=no' in configure.ac line 48, why did you
> > > choose this way?
> >
> > --with-doxygen=no would do try trick, yes.
>
> Not sure if it was clear, but I meant to change the default in
> configure.ac, so users will have to pass --with-doxygen=yes if they
> want to build these docs. I guess that's the most intuitive way for
> users.
Thanks, I will submit a patch to change default.
next prev parent reply other threads:[~2024-10-13 8:21 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-12 17:15 [PATCH libmnl] build: do not build documentation automatically Pablo Neira Ayuso
2024-10-12 19:54 ` Phil Sutter
2024-10-12 21:26 ` Pablo Neira Ayuso
2024-10-12 23:03 ` Phil Sutter
2024-10-13 8:21 ` Pablo Neira Ayuso [this message]
2024-10-14 7:55 ` Duncan Roe
2024-10-14 8:09 ` Pablo Neira Ayuso
2024-10-14 11:12 ` Jan Engelhardt
2024-10-14 11:20 ` Pablo Neira Ayuso
[not found] ` <Zw8UOCbpwSOupUcf@slk15.local.net>
[not found] ` <Zw9qbppRAtX4VbIv@calendula>
2024-10-16 7:26 ` [PATCH libmnl v2] " Pablo Neira Ayuso
2024-10-17 23:59 ` Duncan Roe
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=ZwuDBGBiRqw0e2L3@calendula \
--to=pablo@netfilter.org \
--cc=netfilter-devel@vger.kernel.org \
--cc=phil@nwl.cc \
/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 NNTP newsgroup(s).