Bug 8108

Summary: Qt unable to be statically build caused by incorrect plugin path
Product: [Build System, Metadata & Runtime] OE-Core Reporter: Justin <jbauer>
Component: coreAssignee: Otavio Salvador <otavio>
Status: RESOLVED INVALID QA Contact:
Severity: minor    
Priority: Low CC: akuster, bluelightning, meta.mr.watcher, meta.watcher, randy.macleod
Version: unspecified   
Target Milestone: Future   
Hardware: x86   
OS: x86   
Whiteboard:
OS type for building Yocto: --- Type of Regression: ---
Verified: Documentation change: Don't know
Attachments:
Description Flags
Environment and error bitbake error output none

Description Justin 2015-08-05 23:53:55 UTC
Created attachment 2630 [details]
Environment and error bitbake error output

I'm building a static version of Qt by replacing '-shared' with '-static' to qtbase_git.bb. I try to build the SDK with `$ bitbake meta-toolchain-qt5`. I receive a few  'ERROR: QA Issue: qtsvg: Files/directories were installed but not shipped' concerning the generated paths:

  /usr/lib/qt5/plugins
  /usr/lib/qt5/plugins/imageformats
  /usr/lib/qt5/plugins/iconengines
  /usr/lib/qt5/plugins/imageformats/libqsvg.a
  /usr/lib/qt5/plugins/imageformats/libqsvg.prl
  /usr/lib/qt5/plugins/iconengines/libqsvgicon.prl
  ....

Please note that these paths are incorrect and should be prefixed by the cross compile system root path. Subsequent attempts to compile later packages fail when they cannot locate the appropriate libraries since the lib path is incorrect. 

Reinstating '-shared' omits any errors and the SDK is built correctly with a dynamically linked Qt. Is it possible to build Qt that is statically linked?


Build Configuration:
BB_VERSION        = "1.26.0"
BUILD_SYS         = "i686-linux"
NATIVELSBSTRING   = "Ubuntu-14.04"
TARGET_SYS        = "arm-poky-linux-gnueabi"
MACHINE           = "ts4900-quad"
DISTRO            = "poky-systemd"
DISTRO_VERSION    = "1.8"
TUNE_FEATURES     = "arm armv7a vfp thumb neon callconvention-hard cortexa9"
TARGET_FPU        = "vfp-neon"
Comment 1 Paul Eggleton 2015-08-06 15:12:37 UTC
Whilst we haven't been tracking bugs in meta-qt5 in this bugzilla, that may be changing in the near future so I'm leaving this open for now.

Otavio is this something you're prepared to look into? If not feel free to reassign to unassigned.
Comment 2 Otavio Salvador 2015-08-06 16:23:44 UTC
Yes, I can look at it but this will need to be by the end of month as I will be out from August 12th to 25th.
Comment 3 Armin Kuster 2017-09-30 00:24:27 UTC
is this still an issue?
Comment 4 Randy MacLeod 2019-10-03 15:32:11 UTC
We are not tracking meta-qt5 in this bugzilla. See the README for that layer.