From: Lionel Landwerlin <llandwerlin@gmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/3] gtk-doc: add gtk-doc.m4 to satisfy aclocal
Date: Sat, 13 Feb 2010 17:52:08 +0100 [thread overview]
Message-ID: <1266079928.2185.18.camel@coalu.atr> (raw)
In-Reply-To: <61f677cb060732316b41f072210986e97ae9379f.1266074036.git.thomas.petazzoni@free-electrons.com>
Le samedi 13 f?vrier 2010 ? 16:13 +0100, Thomas Petazzoni a ?crit :
> When packages using gtk-doc are autoreconfigured, aclocal complains
> because it cannot find the macros defined in gtk-doc.m4. We could
> compile the gtk-doc package for the host, but it depends on
> gnome-doc-utils, which depends on libxml2, libxslt, and other packages
> as well.
>
> Since we don't care about the documentation, all is needed is in fact
> the gtk-doc.m4, so that the configure script can be generated, and we
> can use the --disable-gtk-doc to not generate the documentation.
>
> To solve this, we include a gtk-doc.m4 file in package/automake/, and
> it gets installed in $(STAGING_DIR)/usr/share/aclocal/ during the
> installation of the host automake (used for autoreconfiguration of
> packages).
>
> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
Acked-by: Lionel Landwerlin <llandwerlin@gmail.com>
next prev parent reply other threads:[~2010-02-13 16:52 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-13 15:13 [Buildroot] [pull request] Pull request for branch misc-fixes1 Thomas Petazzoni
2010-02-13 15:13 ` [Buildroot] [PATCH 1/3] gtk-doc: add gtk-doc.m4 to satisfy aclocal Thomas Petazzoni
2010-02-13 16:52 ` Lionel Landwerlin [this message]
2010-02-13 15:13 ` [Buildroot] [PATCH 2/3] Fix dependencies for TrapProto Thomas Petazzoni
2010-02-13 15:13 ` [Buildroot] [PATCH 3/3] Bump TCL version and switch to the autotools infrastructure Thomas Petazzoni
2010-02-17 10:24 ` [Buildroot] [pull request] Pull request for branch misc-fixes1 Peter Korsgaard
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=1266079928.2185.18.camel@coalu.atr \
--to=llandwerlin@gmail.com \
--cc=buildroot@busybox.net \
/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