Openembedded Devel Discussions
 help / color / mirror / Atom feed
From: Alex J Lennon <ajlennon@dynamicdevices.co.uk>
To: openembedded-devel@lists.openembedded.org
Subject: Re: [PATCH] Backported libgdiplus 2.10 from meta-mono
Date: Sun, 11 Mar 2012 19:17:20 +0000	[thread overview]
Message-ID: <4F5CFA40.80208@dynamicdevices.co.uk> (raw)
In-Reply-To: <20120311165527.GA24330@rhein.zuhause.netz>

Hi Henning,

>I tought this is handled by the pkgconfigi.bbclass which you inherit.

It seems not, in that if I remove that stanza I get QA staging errors on 
the .pc file generated by libgdiplus.

What I don't understand is why the original recipe in meta-mono, which 
is presumably used by oe-core,
does not generate the error (I would guess). Is there a substantive 
difference between pkgconfig.bbclass
in oe-classic and oe-core? Or maybe I'm just not understanding something....

Regards,

Alex

On 11/03/2012 16:55, Henning Heinold wrote:
> On Sun, Mar 11, 2012 at 12:01:17PM +0000, ajlennon@dynamicdevices.co.uk wrote:
>> From: Alex J Lennon<ajlennon@gmail.com>
>> +SRC_URI[md5sum] = "451966e8f637e3a1f02d1d30f900255d"
>> +SRC_URI[sha256sum] = "2d9e0397ef5583ed855eaafcdac8cabbe1d58463ed1e4b545be6dde5b63712a4"
>> +
>> +
>> +FILES_${PN} += "${libdir}/libgdiplus.so"
>> +INSANE_SKIP_${PN} += "dev-so"
>> +
>> +do_install_append() {
>> +  # fix pkgconfig .pc file
>> +  sed -i -e s#I${STAGING_DIR_HOST}#I#g ${D}${libdir}/pkgconfig/*.pc
>> +}
> ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
>
> I tought this is handled by the pkgconfigi.bbclass which you inherit.
>
> Bye Henning
>
> _______________________________________________
> Openembedded-devel mailing list
> Openembedded-devel@lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel




      reply	other threads:[~2012-03-11 19:26 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-03-11 12:01 [PATCH] Backported libgdiplus 2.10 from meta-mono ajlennon
2012-03-11 16:55 ` Henning Heinold
2012-03-11 19:17   ` Alex J Lennon [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=4F5CFA40.80208@dynamicdevices.co.uk \
    --to=ajlennon@dynamicdevices.co.uk \
    --cc=openembedded-devel@lists.openembedded.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox