All of lore.kernel.org
 help / color / mirror / Atom feed
From: Anders Darander <anders@chargestorm.se>
To: Olaf Mandel <o.mandel@menlosystems.com>
Cc: yocto@yoctoproject.org
Subject: Re: Question about populate_sdk
Date: Wed, 13 Sep 2017 13:43:56 +0200	[thread overview]
Message-ID: <20170913114356.rpb76i365g5r2vec@ad.chargestorm.se> (raw)
In-Reply-To: <264515b7-d412-2188-ad66-003c0e3d0dd8@menlosystems.com>

Hi, 

* Olaf Mandel <o.mandel@menlosystems.com> [170913 13:16]:

> I hope this is the right place to ask this: I wanted to generate an SDK
> bundle to work on an applications code outside of the bitbake
> environment (also without devtool, if possible). So I selected an image
> containing the application and ran the populate_sdk task of that image.
> But the generated SDK is missing some dependencies of the application.

> Is this expected? Or am I doing something wrong?

No, all the dependencies should be part of the generated SDK.

I've seen this, and unfortunately, not had time to debug it, nor create
a small test example. And when I took time to make a small test, I
didn't immediately find theh issue...

See Yocto #11724, at https://bugzilla.yoctoproject.org/show_bug.cgi?id=11724

> I made a minimal demo layer that shows the problem (see below for the 7
> files making up the demo). I ran "bitbake -c populate_sdk test-image"
> and I expected the file usr/lib/test-lib to be present in the SDK, but
> it is not.

Ah, a small test example? Perfect!
Could you add it the bug above? It would likely make it easier to debug.

Cheers
Anders

-- 
Anders Darander, Senior System Architect
ChargeStorm AB / eStorm AB


  reply	other threads:[~2017-09-13 11:44 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-09-13 11:08 Question about populate_sdk Olaf Mandel
2017-09-13 11:43 ` Anders Darander [this message]
2017-09-13 12:18   ` Olaf Mandel

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=20170913114356.rpb76i365g5r2vec@ad.chargestorm.se \
    --to=anders@chargestorm.se \
    --cc=o.mandel@menlosystems.com \
    --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.