From: Karel Zak <kzak@redhat.com>
To: Ruediger Meier <sweet_f_a@gmx.de>
Cc: util-linux@vger.kernel.org
Subject: Re: build-sys: minor issues
Date: Mon, 2 Jun 2014 11:48:26 +0200 [thread overview]
Message-ID: <20140602094826.GN9000@x2.net.home> (raw)
In-Reply-To: <201406020233.39094.sweet_f_a@gmx.de>
On Mon, Jun 02, 2014 at 02:33:38AM +0200, Ruediger Meier wrote:
> On Monday 02 June 2014, Ruediger Meier wrote:
> > I have two minor issues with our build-sys:
>
> Another issue:
>
> 3. --enable-gtk-doc does not work in out-of-tree build:
I'll try to fix it (it worked time ago if I good remember). Frankly,
the way how is gtk-doc designed to work with autotools sucks...
BTW, our TODO:
* use something better than gtk-doc for libmount and libblkid (doxyden?)
;-)
> BTW maybe we could consider about adding these docs to dist tarball to
> not bother users with gtk-doc deps? (But I know then it's even more
Hmm... not sure, I guess the number of people who care about libs
docs is pretty small and for mainstream distros is the dependence on
gtk-doc no issue.
> complicated to rebuild cleanly in builddir when the existing one in
> dist srcdir is outdated.)
Karel
--
Karel Zak <kzak@redhat.com>
http://karelzak.blogspot.com
next prev parent reply other threads:[~2014-06-02 9:48 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-01 22:56 build-sys: minor issues Ruediger Meier
2014-06-02 0:33 ` Ruediger Meier
2014-06-02 9:48 ` Karel Zak [this message]
2014-06-02 11:05 ` Ruediger Meier
2014-06-03 10:42 ` Karel Zak
2014-06-04 9:33 ` Ruediger Meier
2014-06-02 9:42 ` Karel Zak
2014-06-02 10:33 ` Ruediger Meier
2014-06-03 11:27 ` Karel Zak
2014-06-03 19:46 ` Benno Schulenberg
2014-06-04 8:38 ` Karel Zak
2014-06-03 13:09 ` Ruediger Meier
2014-06-04 9:26 ` Karel Zak
2014-06-04 9:48 ` Ruediger Meier
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=20140602094826.GN9000@x2.net.home \
--to=kzak@redhat.com \
--cc=sweet_f_a@gmx.de \
--cc=util-linux@vger.kernel.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