From: Karel Zak <kzak@redhat.com>
To: linux-hotplug@vger.kernel.org
Subject: Re: more fixes for out of tree builds
Date: Tue, 10 Nov 2009 10:36:57 +0000 [thread overview]
Message-ID: <20091110103657.GA12196@nb.net.home> (raw)
In-Reply-To: <20091109034609.GA28618@bongo.bofh.it>
On Tue, Nov 10, 2009 at 10:01:32AM +0100, Martin Pitt wrote:
> Karel Zak [2009-11-09 23:43 +0100]:
> > need to support out-of-tree builds and who don't want to store
> > generated stuff (docs/{tmpl,xml,html}) in the source code repository.
>
> Well, not quite "by design", but gtk-doc.make is indeed broken for
> this. The Ubuntu package does
I don't think so. For example gtkdoc-scan assumes all files in the
output directory (see /usr/bin/gtkdoc-scan, lines 100-110).
This is problem, because for example sections are defined in the
$(srcdir)/$(DOC_MODULE)-sections.txt.
> # fix gtk-doc breakage with separate build tree
> sed -i 's/srcdir/builddir/g' gtk-doc.make
Is it correct? All your setting in $(srcdir) (for example lits of sections,
some extra xml files, ...) will be invisible for gtk-doc.
> before autoreconf, which does the trick.
>
> Please also see
>
> https://bugzilla.gnome.org/show_bug.cgi?idH5806
pretty old bug, it seems we all depend on unmaintained tool :-(
Karel
--
Karel Zak <kzak@redhat.com>
next prev parent reply other threads:[~2009-11-10 10:36 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-09 3:46 more fixes for out of tree builds Marco d'Itri
2009-11-09 11:18 ` Kay Sievers
2009-11-09 14:03 ` Dan Nicholson
2009-11-09 14:19 ` Marco d'Itri
2009-11-09 22:43 ` Karel Zak
2009-11-09 23:13 ` Karel Zak
2009-11-10 5:40 ` Kay Sievers
2009-11-10 9:01 ` Martin Pitt
2009-11-10 10:36 ` Karel Zak [this message]
2009-11-10 11:12 ` Martin Pitt
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=20091110103657.GA12196@nb.net.home \
--to=kzak@redhat.com \
--cc=linux-hotplug@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;
as well as URLs for NNTP newsgroup(s).