Details
-
Bug
-
Resolution: Done
-
P1: Critical
-
None
-
5.15
-
None
-
2020wk32, 2020wk34
Description
The current way that 3rd party HW integrations (such as Renesas) are done for Boot2Qt yocto environment, no longer works. A fix was made to the Google's repo tools that now prevent the initialization using the manifest.xml from the meta repo itself.
repo init -u git://code.qt.io/yocto/meta-boot2qt-renesas -m conf/manifest.xml -b warrior ... error.ManifestInvalidPathError: <linkfile> invalid "dest": .repo/local_manifests/boot2qt.xml: bad component: .repo
The workaround is to use a separate manifest repository, which is the proper way of using the repo tool.
repo init -u git://code.qt.io/yocto/boot2qt-manifest -b renesas -m warrior.xml
This will need to be addressed in the documentations.
Attachments
Issue Links
- mentioned in
-
Page Loading...
For Gerrit Dashboard: QTBUG-85889 | ||||||
---|---|---|---|---|---|---|
# | Subject | Branch | Project | Status | CR | V |
309484,4 | Update guide how to add new BSP layers | 5.15 | tqtc-boot2qt/doc | Status: MERGED | +2 | 0 |
310136,2 | Remove manifest | zeus | yocto/meta-boot2qt-renesas | Status: MERGED | +2 | 0 |
311882,2 | jenkins: use boot2qt-manifest repo for renesas builds | dev | tqtc-boot2qt/build-scripts | Status: MERGED | +2 | 0 |