From: "dengke.du@windriver.com" <dengke.du@windriver.com>
To: Paul Eggleton <paul.eggleton@linux.intel.com>,
<openembedded-core@lists.openembedded.org>,
"Burton, Ross" <ross.burton@intel.com>
Subject: Re: [PATCH 1/1] nativesdk-coreutils: a lot of warnings fixed
Date: Thu, 17 Mar 2016 17:35:42 +0800 [thread overview]
Message-ID: <56EA7A6E.70401@windriver.com> (raw)
In-Reply-To: <4132846.MxUMxyiN00@peggleto-mobl.ger.corp.intel.com>
[-- Attachment #1: Type: text/plain, Size: 1234 bytes --]
After a talk with Hongxu jia, we decided to change the
do_install_append_class-target()
to do_install_append(), in this function, added the following:
if [ "${CLASSOVERRIDE}" = "class-native" ]; then
return
fi
in this way, avoid the conflict with the following
do_install_append_class-native function.
//dengke
On 2016年03月17日 05:52, Paul Eggleton wrote:
> On Wed, 16 Mar 2016 21:30:35 Burton, Ross wrote:
>> On 16 March 2016 at 02:49, Dengke Du <dengke.du@windriver.com> wrote:
>>> When we create nativesdk-coreutils, a lot of warnings appear,it
>>> show many files can't find.
>> I don't think anywhere where nativesdk packages are used actually runs the
>> postinst scripts to create the alternative links, so maybe we should be
>> stopping update-alternatives do anything in nativesdk (just like it doesn't
>> do anything for native)?
> Actually I checked this by adding a dummy line which creates a file in $D to
> the dbus postinst and then adding nativesdk-dbus to buildtools-tarball - it
> seems that the postinst does actually get run. As long as the postinst can
> successfully run at SDK construction time then apparently it should work.
>
> Cheers,
> Paul
>
[-- Attachment #2: Type: text/html, Size: 2077 bytes --]
prev parent reply other threads:[~2016-03-17 9:35 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-16 2:49 [PATCH 0/1] nativesdk-coreutils: a lot of warnings fixed Dengke Du
2016-03-16 2:49 ` [PATCH 1/1] " Dengke Du
2016-03-16 21:30 ` Burton, Ross
2016-03-16 21:52 ` Paul Eggleton
2016-03-17 9:35 ` dengke.du [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=56EA7A6E.70401@windriver.com \
--to=dengke.du@windriver.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=paul.eggleton@linux.intel.com \
--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 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.