All of lore.kernel.org
 help / color / mirror / Atom feed
From: Darren Hart <dvhart@linux.intel.com>
To: Richard Purdie <richard.purdie@linuxfoundation.org>
Cc: Yocto Project <yocto@yoctoproject.org>
Subject: Re: Writing do_install_append for target and virtclass-native in a bbappend
Date: Tue, 17 Apr 2012 09:12:05 -0700	[thread overview]
Message-ID: <4F8D9655.9090109@linux.intel.com> (raw)
In-Reply-To: <1334668768.616.92.camel@ted>



On 04/17/2012 06:19 AM, Richard Purdie wrote:
> On Mon, 2012-04-16 at 20:32 -0700, Darren Hart wrote:
>> I'm trying to address a symlink naming issue in the bzip2 package when
>> used with Chrome. Chrome is looking for a specific soname, which the
>> default install of bzip2 doesn't setup. I can address this easily by
>> adding the symlink via a bzip2 bbappend in do_install_append().
>> Unfortunately, this fails for the virtclass-native variant. I tried
>> adding and empty:
>>
>> do_install_append_virtclass-native() {
>> 	:
>> }
>>
>> function to the bbappend, which still failed. I then added an echo
>> statement which appeared in the output, but it still ran non-native
>> do_install_append() and failed. Switching the order of the functions
>> made the echo output disappear, but the native variant still failed.
>>
>> I figure I must be missing something rather fundamental here. Any ideas
>> what it might be?
> 
> _append variables stack so if you do:
> 
> A_append = "x"
> A_append = "y"
> A_append = "z"
> 
> You'll end up with A = "xyz".
> 
> You can do something a little more ugly to work around it like:
> 
> do_install_append () {
> 	${SYMLINK}
> }
> 
> SYMLINK = "ln -s a b"
> SYMLINK_virtclass-native = ":"
> 

Thank you RP, that does the trick.

-- 
Darren Hart
Intel Open Source Technology Center
Yocto Project - Linux Kernel


  reply	other threads:[~2012-04-17 16:12 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-04-17  3:32 Writing do_install_append for target and virtclass-native in a bbappend Darren Hart
2012-04-17  9:32 ` Paul Eggleton
2012-04-17 13:20   ` Richard Purdie
2012-04-17 13:19 ` Richard Purdie
2012-04-17 16:12   ` Darren Hart [this message]
2012-04-17 16:14     ` Darren Hart

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=4F8D9655.9090109@linux.intel.com \
    --to=dvhart@linux.intel.com \
    --cc=richard.purdie@linuxfoundation.org \
    --cc=yocto@yoctoproject.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.