From: Peter Korsgaard <peter@korsgaard.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v2] libgtk2: skip tutorial and faq build
Date: Thu, 26 Feb 2015 22:16:13 +0100 [thread overview]
Message-ID: <87385s74rm.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <20150226163433.340EDE044A@smtp.hushmail.com> (justin swartz's message of "Thu, 26 Feb 2015 18:34:33 +0200")
>>>>> "justin" == justin swartz <justin.swartz@nym.hush.com> writes:
Hi,
> This should have been addressed to "peter at korsgaard.com", but my
> provider claims that the address is invalid.
Really? What error message do you get exactly (perhaps privately to
jacmet at sunsite.dk).
> On 02/26/2015 at 1:17 AM, "Peter Korsgaard" <peter@korsgaard.com> wrote:
>> Why not just pass DB2HTML=false in LIBGTK2_CONF_ENV?
>>
> DB2HTML=false works perfectly, thanks for pointing that out!
Great. I've committed a fix to pass it.
>> > +LIBGTK2_CONF_OPTS = \
>> > + --disable-glibtest \
>> > + --enable-explicit-deps=no \
>> > + --disable-gtk-doc-pdf \
>> > + --disable-gtk-doc-html
>>
>> What does that buy us? gtk-doc is disabled unless --enable-gtk-doc
>> is passed (which we don't), so these shouldn't change anything.
>>
> I hadn't noticed that --disable-gtk-doc was implicitly passed in *_CONF_OPTS.
That and the fact that it defaults to disabled:
./configure --help|grep gtk-doc
--enable-gtk-doc use gtk-doc to build documentation [[default=no]]
--enable-gtk-doc-html build documentation in html format [[default=yes]]
--enable-gtk-doc-pdf build documentation in pdf format [[default=no]]
> Unfortunately there is still documention installed in to /usr/share/gtk-doc/html/,
> but it's eventually removed by target-finalize anyway.
Yes, but the patch you sent didn't change anything about that, right?
--
Bye, Peter Korsgaard
next prev parent reply other threads:[~2015-02-26 21:16 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-24 23:50 [Buildroot] [PATCH v2] libgtk2: skip tutorial and faq build justin.swartz at nym.hush.com
2015-02-25 17:21 ` Yann E. MORIN
2015-02-25 23:17 ` Peter Korsgaard
2015-02-26 16:34 ` justin.swartz at nym.hush.com
2015-02-26 21:16 ` Peter Korsgaard [this message]
2015-02-26 21:50 ` Yann E. MORIN
2015-02-26 22:10 ` Peter Korsgaard
2015-02-26 16:55 ` [Buildroot] [PATCH v3] " justin.swartz at nym.hush.com
2015-02-26 20:04 ` Yann E. MORIN
2015-02-26 22:00 ` Peter Korsgaard
2015-02-26 17:35 ` [Buildroot] [PATCH v2] " Yann E. MORIN
2015-02-26 21:58 ` 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=87385s74rm.fsf@dell.be.48ers.dk \
--to=peter@korsgaard.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