Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Mike Looijmans <mike.looijmans@topic.nl>
To: Patches and discussions about the oe-core layer
	<openembedded-core@lists.openembedded.org>
Subject: SDK does not contain pkg-config files
Date: Wed, 31 Jul 2019 05:47:06 +0000	[thread overview]
Message-ID: <6ce08045-fb67-aab4-9ff5-9f8d511eeb78@topic.nl> (raw)

I'm trying to get the SDK to work, but no success because the SDK apparently 
does not install any pkg-config file, resulting in autotools and cmake not 
being able to find any library.

Built the SDK using "bitbake -c populate_sdk image"

Install the resulting SDK, and source the shell script.

Building "helloworld" works. Building something slightly more advanced fails, 
because pkg-config isn't working: "pkg-config --list-all" is empty.

The cause is that the pkgconfig files simply aren't in the sysroot:

$ echo $PKG_CONFIG_PATH
/home/mike/p/sysroots/cortexa9t2hf-neon-oe-linux-gnueabi/usr/lib/pkgconfig:/home/mike/p/sysroots/cortexa9t2hf-neon-oe-linux-gnueabi/usr/share/pkgconfig
$ ls /home/mike/p/sysroots/cortexa9t2hf-neon-oe-linux-gnueabi/usr/lib/pkgconfig
ls: cannot access 
'/home/mike/p/sysroots/cortexa9t2hf-neon-oe-linux-gnueabi/usr/lib/pkgconfig': 
No such file or directory
$ ls /home/mike/p/sysroots/cortexa9t2hf-neon-oe-linux-gnueabi/usr/share/pkgconfig
ls: cannot access 
'/home/mike/p/sysroots/cortexa9t2hf-neon-oe-linux-gnueabi/usr/share/pkgconfig': 
No such file or directory


             reply	other threads:[~2019-07-31  5:47 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-07-31  5:47 Mike Looijmans [this message]
2019-07-31 12:37 ` SDK does not contain pkg-config files Ross Burton
2019-07-31 13:22   ` Mike Looijmans
2019-07-31 13:29     ` Ross Burton
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=6ce08045-fb67-aab4-9ff5-9f8d511eeb78@topic.nl \
    --to=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