[yocto] wrong distro name in toolchain

Marek Słomiany marekslomiany at gmail.com
Mon Dec 18 03:11:45 PST 2017


Hi, I'm having problem while building Qt application inside of yocto and
using generated SDK.
I have bypassed it when using generated SDK, which I describe here.

My setup in short:
I'm using for Qt this layer git://github.com/meta-qt5/meta-qt5.git in rocko
branch
beside Qt, other layers that might be important:
meta-poky (rocko)
meta-oe (morty)
meta-python (morty)
meta-networking (morty)
meta-ti (morty)

The platform is am335x
distro name is "etos"

I had some problems with sdk (at first I added Qt to my build but
applications were developped and build by my coleagues using external
toolchains).
Recently I've added recipes for those apps to my layer.
To test if code I got from my team is building fine, I have generated SDK
using "bitbake <image-name> -c populate_sdk" and deployed it in default
path which is /opt/etos/1.0/. When I have sourced it and tried to configure
I got:

  CMake Error at
/opt/etos/1.0/sysroots/armv7ahf-neon-etos-linux-gnueabi/usr/lib/cmake/Qt5Core/Qt5CoreConfig.cmake:32
(message):
  The imported target "Qt5::Core" references the file

 "/opt/etos/1.0/sysroots/armv7ahf-neon-etos-linux-gnueabi/../x86_64-oesdk-linux/usr/bin/qt5/qmake"
  but this file does not exist.  Possible reasons include:
  * The file was deleted, renamed, or moved to another location.
  * An install or uninstall procedure did not complete successfully.
  * The installation package was faulty and contained

 "/opt/etos/1.0/sysroots/armv7ahf-neon-etos-linux-gnueabi/usr/lib/cmake/Qt5Core/Qt5CoreConfigExtras.cmake"
  but not all the files it references.

To solve that problem I coppied the
/opt/etos/1.0/sysroots/x86_64-etossdk-linux/ to
/opt/etos/1.0/sysroots/x86_64-oesdk-linux/ with all its content.
Even if that's not the right solution, it worked.
But now I wat to add the recipe to my image. I get something similar:

Log data follows:
| DEBUG: Executing python function sysroot_cleansstate
| DEBUG: Python function sysroot_cleansstate finished
| DEBUG: Executing shell function do_configure
| CMake Error at
/home/mslomiany/linux-dev/poky/build/tmp/sysroots/x86_64-linux/usr/lib/cmake/Qt5Core/Qt5CoreConfig.cmake:20
(message):
|   The imported target "Qt5::Core" references the file
|      "/../x86_64-oesdk-linux/usr/bin/qt5/qmake"
|   but this file does not exist.  Possible reasons include:
|   * The file was deleted, renamed, or moved to another location.
|   * An install or uninstall procedure did not complete successfully.
|   * The installation package was faulty and contained
|
 "/home/mslomiany/linux-dev/poky/build/tmp/sysroots/x86_64-linux/usr/lib/cmake/Qt5Core/Qt5CoreConfigExtras.cmake"
|   but not all the files it references.
|
| Call Stack (most recent call first):
|
/home/mslomiany/linux-dev/poky/build/tmp/sysroots/x86_64-linux/usr/lib/cmake/Qt5Core/Qt5CoreConfigExtras.cmake:6
(_qt5_Core_check_file_exists)
|
/home/mslomiany/linux-dev/poky/build/tmp/sysroots/x86_64-linux/usr/lib/cmake/Qt5Core/Qt5CoreConfig.cmake:177
(include)
|
/home/mslomiany/linux-dev/poky/build/tmp/sysroots/x86_64-linux/usr/lib/cmake/Qt5/Qt5Config.cmake:33
(find_package)
|   deps/CMake/Qt.cmake:23 (find_package)
|   deps/GuiCore/src/CMakeLists.txt:3 (include)
|
| -- Configuring incomplete, errors occurred!
| See also
"/home/mslomiany/linux-dev/poky/build/tmp/work/armv7ahf-neon-etos-linux-gnueabi/Gui/0.1-r0/build/CMakeFiles/CMakeOutput.log".
| WARNING: exit code 1 from a shell command.
| ERROR: Function failed: do_configure (log file is located at
/home/mslomiany/linux-dev/poky/build/tmp/work/armv7ahf-neon-etos-linux-gnueabi/Gui/0.1-r0/temp/log.do_configure.11780)

It seems like my aproach is not making any difference. I might be trying to
copy wrong directories in ./build/tmp subdirectories.
Can you tell me if all those problems are caused by my mistake or is it
something wrong in yocto/openembedded scripts?

Kind Regards,
Marek
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.yoctoproject.org/pipermail/yocto/attachments/20171218/f47dbc9c/attachment.html>


More information about the yocto mailing list