On 20 February 2013 23:13, Martin Jansa wrote:
>> But we can cherry-pick any libjpeg fixes until we've bitten the bullet
>> and integrated ruby.
>
> ruby-native is already in meta-ruby
Yes, "biting the bullet" means either committing to building WebKit in
oe-core or not.
Ross
__
On Wed, Feb 20, 2013 at 03:50:09PM +, Burton, Ross wrote:
> On 20 February 2013 15:06, Constantin Musca
> wrote:
> >> Have you tried to build webkit-gtk against this? At one point I had
> >> similar jpeg update in my tree causing webkit-gtk build failure.
> >
> > You are right. The problem
On 20 February 2013 15:06, Constantin Musca wrote:
>> Have you tried to build webkit-gtk against this? At one point I had
>> similar jpeg update in my tree causing webkit-gtk build failure.
>
> You are right. The problem is that I can't upgrade webkit-gtk because the
> new version requires ruby.
On 02/18/2013 06:04 PM, Marko Lindqvist wrote:
On 18 February 2013 17:47, Constantin Musca wrote:
License checksum change due to:
- version modification
- links modification
- additional license explanations
fix_for_automake_1.12.1.patch: not needed anymore
fix-jmorecfg-boolean-enum.patch: ad
On 18 February 2013 17:47, Constantin Musca wrote:
> License checksum change due to:
> - version modification
> - links modification
> - additional license explanations
>
> fix_for_automake_1.12.1.patch: not needed anymore
>
> fix-jmorecfg-boolean-enum.patch: added
> - we have to undef TRUE & FALS
License checksum change due to:
- version modification
- links modification
- additional license explanations
fix_for_automake_1.12.1.patch: not needed anymore
fix-jmorecfg-boolean-enum.patch: added
- we have to undef TRUE & FALSE in order to define
the boolean enum
Signed-off-by: Constantin Mus
