From: Karel Zak <kzak@redhat.com>
To: linux-hotplug@vger.kernel.org
Subject: Re: more fixes for out of tree builds
Date: Mon, 09 Nov 2009 22:43:56 +0000 [thread overview]
Message-ID: <20091109224356.GR5610@nb.net.home> (raw)
In-Reply-To: <20091109034609.GA28618@bongo.bofh.it>
On Mon, Nov 09, 2009 at 04:46:09AM +0100, Marco d'Itri wrote:
> These are needed to support out of tree builds, but I do not know the
> correct way to properly fix the bugs in Makefile.am.
>
> --
> ciao,
> Marco
> --- a/extras/gudev/docs/Makefile.in
> +++ b/extras/gudev/docs/Makefile.in
> @@ -300,6 +300,7 @@ GPATH = $(srcdir)
> TARGET_DIR = $(HTML_DIR)/$(DOC_MODULE)
>
> # This includes the standard gtk-doc make rules, copied by gtkdocize.
> +srcdir := $(builddir)
From my point of view gtk-doc.make is broken by design for people who
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.
I have spent one evening to fix gtk-doc.make for util-linux-ng, see
http://git.kernel.org/?p=utils/util-linux-ng/util-linux-ng.git;a=commitdiff;hä2b25eb1536697ba283772f5452e7495cb4024b;hp•9ac815b67a43f9b5f70a1dc294d2cf3a61fc2c
.. it's not perfect, but works for me.
Karel
--
Karel Zak <kzak@redhat.com>
next prev parent reply other threads:[~2009-11-09 22:43 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 [this message]
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
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=20091109224356.GR5610@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).