Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Ross Burton <ross.burton@intel.com>
To: Mike Looijmans <mike.looijmans@topic.nl>,
	"openembedded-core@lists.openembedded.org"
	<openembedded-core@lists.openembedded.org>
Subject: Re: SDK does not contain pkg-config files
Date: Wed, 31 Jul 2019 14:29:47 +0100	[thread overview]
Message-ID: <487ea47b-1db4-8c95-c0ad-661a56ccc07a@intel.com> (raw)
In-Reply-To: <63da8199-4e73-70e2-bcea-60f7e53a2e16@topic.nl>

On 31/07/2019 14:22, Mike Looijmans wrote:
> Well, that's at least good to know.
> 
> I'm on the "thud" branch currently, so I hope this isn't something that got
> fixed only recently.
> 
> I'll try some simple images first. I gather there's no particular magic
> incantation I need to put into my image recipe to get the pkg-config files
> into the SDK sysroot?

Right, they're just in the -dev packages.  I'd try building a 
core-image-minimal SDK to verify that works, as I suspect you've done 
something in your image to break the SDK.

Ross
---------------------------------------------------------------------
Intel Corporation (UK) Limited
Registered No. 1134945 (England)
Registered Office: Pipers Way, Swindon SN3 1RJ
VAT No: 860 2173 47

This e-mail and any attachments may contain confidential material for
the sole use of the intended recipient(s). Any review or distribution
by others is strictly prohibited. If you are not the intended
recipient, please contact the sender and delete all copies.

  reply	other threads:[~2019-07-31 13:29 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-07-31  5:47 SDK does not contain pkg-config files Mike Looijmans
2019-07-31 12:37 ` Ross Burton
2019-07-31 13:22   ` Mike Looijmans
2019-07-31 13:29     ` Ross Burton [this message]
2019-08-01 11:17       ` Mike Looijmans
2019-08-02  5:17         ` Khem Raj

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=487ea47b-1db4-8c95-c0ad-661a56ccc07a@intel.com \
    --to=ross.burton@intel.com \
    --cc=mike.looijmans@topic.nl \
    --cc=openembedded-core@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