[agl-discussions] wayland-ivi-extension build error?

Takashi Matsuzawa tmatsuzawa at xevo.com
Wed Jan 25 07:28:53 UTC 2017


I am very sorry this was my fault.

One of my weston_%.bbapend was overwriting the base do_install() function.


________________________________
From: automotive-discussions-bounces at lists.linuxfoundation.org <automotive-discussions-bounces at lists.linuxfoundation.org> on behalf of Takashi Matsuzawa <tmatsuzawa at xevo.com>
Sent: Wednesday, January 25, 2017 1:44 PM
To: automotive-discussions at lists.linuxfoundation.org
Subject: [agl-discussions] wayland-ivi-extension build error?


Hello, AGL.
Just in case are you familiar with the following during the chinook based build?

(within wayland-ivi-extension build phase)
| -- Detecting CXX compile features
| -- Detecting CXX compile features - done
| -- Found PkgConfig: /opt/yocto/dev/tmp/imx-agl-wk1/sysroots/x86_64-linux/usr/bin/pkg-config (found version "0.29")
| -- Checking for module 'wayland-client>=1.9.0'
| --   Found wayland-client, version 1.9.0
| -- Checking for module 'wayland-server>=1.9.0'
| --   Found wayland-server, version 1.9.0
| -- Checking for module 'weston>=1.9.0'
| --   Package 'weston>=1.9.0' not found
| CMake Error at /opt/yocto/dev/tmp/imx-agl-wk1/sysroots/x86_64-linux/usr/share/cmake-3.4/Modules/FindPkgConfig.cmake:360 (message):
|   A required package was not found

It seems it is checking for weston.pc (so if pkg-config does not find it, error like above is shown).

I rebuilt weston several times, and what I see is that weston.pc is avaiable only below.
(Not in sysroots/x86_64-linux, etc. where cross-build includes, etc. are.)

>(TMPDIR)work/cortexa9hf-neon-mx6qdl-poky-linux-gnueabi/weston/1.9.0-r0/build/src/weston.pc

I can see weston_1.9.0.bb has 'inherit pkcfong', so it should place weston.pc properly (in cross build toollchain?) and wayland_ivi_extension build should find it?

I think initially my build was OK, no error from wayland_ivi_extension build.

But now it is failing, and I suspect some change in my configuration caused the error to begin happening, but I do not have immediate clue.

Thank you for your advice if you ever notice anything.

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.linuxfoundation.org/pipermail/automotive-discussions/attachments/20170125/e8bcd47f/attachment.html>


More information about the automotive-discussions mailing list