From: Stephane Cerveau <scerveau@connected-labs.com>
To: Richard Purdie <richard.purdie@linuxfoundation.org>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [dora][PATCH] vala: should not depend on gtk+
Date: Tue, 01 Jul 2014 10:24:06 +0200 [thread overview]
Message-ID: <53B27026.6050207@connected-labs.com> (raw)
In-Reply-To: <1404165610.6362.45.camel@ted>
Yes, it could be an idea.
On my side i tried with this patch but i could miss some dependency seen
that my build was incremental. Could be better to merge the master patch.
Best regards.
Stéphane
On 07/01/2014 12:00 AM, Richard Purdie wrote:
> On Mon, 2014-06-30 at 16:23 +0200, Stéphane Cerveau wrote:
>> Signed-off-by: Stéphane Cerveau <scerveau@connected-labs.com>
>> ---
>> meta/recipes-devtools/vala/vala.inc | 2 +-
>> 1 file changed, 1 insertion(+), 1 deletion(-)
>>
>> diff --git a/meta/recipes-devtools/vala/vala.inc b/meta/recipes-devtools/vala/vala.inc
>> index a8927d7..a9e5a57 100644
>> --- a/meta/recipes-devtools/vala/vala.inc
>> +++ b/meta/recipes-devtools/vala/vala.inc
>> @@ -1,7 +1,7 @@
>> DESCRIPTION = "Vala is a C#-like language dedicated to ease GObject programming. \
>> Vala compiles to plain C and has no runtime environment nor penalities whatsoever."
>> SECTION = "devel"
>> -DEPENDS = "glib-2.0 dbus gtk+"
>> +DEPENDS = "glib-2.0 dbus"
>> BBCLASSEXTEND = "native"
>> DEPENDS_virtclass-native = "bison-native glib-2.0-native dbus-native"
>> HOMEPAGE = "http://vala-project.org"
> Really we should probably backport:
>
> http://git.yoctoproject.org/cgit.cgi/poky/commit/?id=27c2cbbdb14d65caef1faafbfea063d6744f4e70
>
> ?
>
> Cheers,
>
> Richard
>
prev parent reply other threads:[~2014-07-01 8:24 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-30 14:23 [dora][PATCH] vala: should not depend on gtk+ Stéphane Cerveau
2014-06-30 22:00 ` Richard Purdie
2014-07-01 8:24 ` Stephane Cerveau [this message]
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=53B27026.6050207@connected-labs.com \
--to=scerveau@connected-labs.com \
--cc=openembedded-core@lists.openembedded.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.