New: qt5webengine: graph-depends seems producing incorrect output

https://bugs.busybox.net/show_bug.cgi?id=12971

Bug ID: 12971
Summary: qt5webengine: graph-depends seems producing incorrect
output
Product: buildroot
Version: 2020.02.2
Hardware: All
OS: Linux
Status: NEW
Severity: normal
Priority: P5
Component: Other
Assignee: unassigned at buildroot.uclibc.org
Reporter: seems.deviant at gmail.com
CC: buildroot at uclibc.org
Target Milestone: ---

Created attachment 8486
--> https://bugs.busybox.net/attachment.cgi?id=8486&action=edit
The graph-depends of the provided config

This is happening on current master: 3a9261ddd9 (HEAD -> master, origin/master, origin/HEAD) package/libusb-compat: set LIBUSB_1_0_SONAME

Create a following .config:
BR2_TOOLCHAIN_BUILDROOT_GLIBC=y
BR2_TOOLCHAIN_BUILDROOT_CXX=y
BR2_ROOTFS_DEVICE_CREATION_DYNAMIC_EUDEV=y
BR2_PACKAGE_MESA3D=y
BR2_PACKAGE_MESA3D_DRI_DRIVER_SWRAST=y
BR2_PACKAGE_MESA3D_OPENGL_EGL=y
BR2_PACKAGE_MESA3D_OPENGL_ES=y
BR2_PACKAGE_QT5=y
BR2_PACKAGE_QT5WEBENGINE=y

Then call:

$ make graph-depends

And you'll see that qt5quickcontrols and qt5quickcontrols2 packages are not marked as dependant on the qt5webengine package, although the qt5webengine has selected both of them.

I would expect the dependency graph to be "ALL -> qt5webengine -> {qt5quickcontrols,qt5quickcontrols2}" rather than "ALL -> {qt5webengine,qt5quickcontrols,qt5quickcontrols2}"

You are receiving this mail because:
You are on the CC list for the bug.

https://bugs.busybox.net/show_bug.cgi?id=12971

--- Comment #1 from Peter Seiderer <[email protected]> --- qt5quickcontrols and qt5quickcontrols2 seems to be run-time dependencies as the compile-time dependencies (see package/qt5/qt5webengine/qt5webengine.mk) are only given as:

QT5WEBENGINE_DEPENDENCIES = ffmpeg libglib2 libvpx opus webp \
        qt5declarative qt5webchannel host-bison host-flex host-gperf \
        host-pkgconf host-python

You are receiving this mail because:
You are on the CC list for the bug.

https://bugs.busybox.net/show_bug.cgi?id=12971

--- Comment #2 from Peter Seiderer <[email protected]> --- And this ones are the ones shown in the graph-depends output...

You are receiving this mail because:
You are on the CC list for the bug.

https://bugs.busybox.net/show_bug.cgi?id=12971

--- Comment #3 from Thomas Petazzoni <[email protected]> --- Indeed as Peter said, graph-depends draws the graph of build-time dependencies, as listed by the package <pkg>_DEPENDENCIES variable.

However, I find it odd that qt5declarative is only a runtime dependency for qt5webengine, if it is needed, it should also be needed at build time, but qt5webengine builds fine without this. Would it be possible to check if this runtime dependency is really needed ?

You are receiving this mail because:
You are on the CC list for the bug.

https://bugs.busybox.net/show_bug.cgi?id=12971

--- Comment #4 from Peter Seiderer <[email protected]> --- qt5declarative (and with it qt5declarative-quick) is a compile time dependency, only qt5quickcontrols and qt5quickcontrols2 are the runtime dependencies (which is o.k. as the quickcontrols are normally only referenced from qml/runtime and the c++ code/libs by plugin loading)...

You are receiving this mail because:
You are on the CC list for the bug.

https://bugs.busybox.net/show_bug.cgi?id=12971

Yann E. MORIN <[email protected]> changed:

What |Removed |Added
----------------------------------------------------------------------------

                 CC|                            |[email protected]
         Resolution|---                         |MOVED
             Status|NEW                         |RESOLVED

--- Comment #5 from Yann E. MORIN <[email protected]> --- Thank you for your report.

The issue tracker for the Buildroot project has been moved to the Gitlab.com issue tracker:
https://gitlab.com/buildroot.org/buildroot/-/issues

We are taking this opportunity to close old issues in this old tracker. If you believe your issue is still relevant, please open one in the new issue tracker.

Thank you!

You are receiving this mail because:
You are on the CC list for the bug.
_______________________________________________
buildroot mailing list
[email protected]
https://lists.buildroot.org/mailman/listinfo/buildroot