From: Colin Walters <walters@verbum.org>
To: Richard Purdie <richard.purdie@linuxfoundation.org>
Cc: poky@yoctoproject.org
Subject: Re: non-upstreamed patches
Date: Mon, 14 Nov 2011 15:48:36 -0500 [thread overview]
Message-ID: <1321303717.1741.9.camel@lenny> (raw)
In-Reply-To: <1321300592.26881.71.camel@ted>
On Mon, 2011-11-14 at 19:56 +0000, Richard Purdie wrote:
> The number of people who write cross safe autogen.sh scripts which do
> everything we need is unfortunately low.
Can you elaborate on this? What are some common cross-unsafe problems?
So concretely here with gtk-doc, since we don't actually want to build
the documentation (because gtk-doc is native only for the exact same
reasons gobject-introspection is, and we've talked about that one).
The GNOME autogen.sh scripts will run "gtkdocize", which pretty much
just copies in gtk-doc.make and gtk-doc.m4. We could reimplement that
with dummy copies, or build a lobotomized gtk-doc (this will require
perl-native but that's about it I think).
I'm experimenting with this now.
> I do appreciate the gnome
> community may do better than others and things are improving over time.
> I'd not yet at a point where I'd trust even 10% of the autogen.sh
> scripts out there though.
The other thing we could do I guess is make it opt-in, like
OE_RUN_AUTOGEN=1 or something in individual recipes using
autotools.bbclass?
next prev parent reply other threads:[~2011-11-14 20:49 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-13 0:57 non-upstreamed patches Colin Walters
2011-11-13 9:28 ` Koen Kooi
2011-11-13 17:16 ` Colin Walters
2011-11-13 19:51 ` Koen Kooi
2011-11-13 9:47 ` Richard Purdie
2011-11-14 19:06 ` Colin Walters
2011-11-14 19:56 ` Richard Purdie
2011-11-14 20:48 ` Colin Walters [this message]
2011-11-14 22:44 ` Richard Purdie
2011-11-15 0:05 ` Colin Walters
2011-11-15 0:19 ` Richard Purdie
2012-01-03 18:45 ` Colin Walters
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=1321303717.1741.9.camel@lenny \
--to=walters@verbum.org \
--cc=poky@yoctoproject.org \
--cc=richard.purdie@linuxfoundation.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.