Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Ming Liu <ming.liu@windriver.com>
To: "Burton, Ross" <ross.burton@intel.com>
Cc: OE-core <openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH 1/2] libcroco: dont package /usr/bin/croco-0.6-config
Date: Fri, 4 Jul 2014 19:08:41 +0800	[thread overview]
Message-ID: <53B68B39.1000801@windriver.com> (raw)
In-Reply-To: <CAJTo0LZYGaHdzEdf_MYV0bre72gD6y6ma0qqs-ZZCTX_kgmL0A@mail.gmail.com>

On 07/04/2014 07:03 PM, Burton, Ross wrote:
> On 4 July 2014 11:54, Ming Liu <ming.liu@windriver.com> wrote:
>> +PACKAGE_PREPROCESS_FUNCS += "croco_package_preprocess"
>> +croco_package_preprocess () {
>> +       if [ -f ${PKGD}/${bindir}/croco-0.6-config ]; then
>> +               rm -f ${PKGD}/${bindir}/croco-0.6-config
>> +       fi
>> +}
> Erm, this is wrong.
>
> So croco-config is broken because the recipe doesn't inherit
> binconfig, to fix the paths and install the binary into libcroco-dev,
> where it belongs.  By not installing it into the package, you've
> broken anything that wants to build using croco-config inside a
> Yocto-generated image, such as the Build Appliance.
>
> Considering that the only recipe to depend on libcroco is librsvg, and
> that uses pkg-config instead of croco-config, then this recipe should
> also inherit binconfig-disabled to turn the config script into a "exit
> 1" no-op.
Yes, you are right! Thanks to correct me, I will send a V2 soon.

the best,
thank you
>
> Ross
>
>



      reply	other threads:[~2014-07-04 11:08 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-07-04 10:54 [PATCH 1/2] libcroco: dont package /usr/bin/croco-0.6-config Ming Liu
2014-07-04 11:03 ` Burton, Ross
2014-07-04 11:08   ` Ming Liu [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=53B68B39.1000801@windriver.com \
    --to=ming.liu@windriver.com \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=ross.burton@intel.com \
    /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