Qt5-GUI now gets compiled with support for OpenGL,
however only links against GL stubs provided by the
2d software renderer.
That way we can decide at runtime, whether we want to
use GL or not - with almost no overhead, if not.
This also enables QtQuick2 being built correctly,
which depends on GL support and provides the
possibility of using QtQuick2 with the 2d-sw-renderer
even on hardware without native support for GL.
Both packages share the same source and I'd prefer handling
them in the very same Makefile, but unfortunately that would
create a circular dependency:
`qt5base` depends on `qt5quick2-2d-sw-renderer-GLstubs`, but
`qt5quick2-2d-sw-renderer` depends on `qt5quick2` which
depends on `qt5base`.
`qt5quick2-2d-sw-renderer` and `qt5quick2-2d-sw-renderer-GLstubs`
sharing the same Makefile results in `qt5base` depending on
`qt5quick2` which is meh.
Do not explicitly specify mkspec file when invoking qmake.
qmake itself is aware of the cross mkspec file (compiled in)
AND of the mkspec file for host builds.
Specifying it explicitly doesn't let qmake choose the
correct one and always tries to cross-compile everything.
Do not use strip any more when it is selected because plugin loading
does not work for plugins build stripped with sstrip, use normal strip
instead.
Signed-off-by: Hauke Mehrtens <hauke@hauke-m.de>
Instead of hard coding the dependency to libiconv-full use the macros
provided by OpenWrt. In the gnu iconv library the second parameter of
iconv(), often called inbuf, is not const, but qt5 assumes that it is
in the gnu version of libiconv. If we make qt5 use the code for the
posix version of libiconv it does not add the -liconv link parameter.
This patch adds the -liconv link parameter.
Signed-off-by: Hauke Mehrtens <hauke@hauke-m.de>
When OpenWrt normally uses the mips dps extensions it adds this to the
CFLAGS which are also given to qt5base. When we configure qt5base
without dsp extension, but give the mdsp in the CFLAGS the compilation
will fail.
Signed-off-by: Hauke Mehrtens <hauke@hauke-m.de>
There's some minor changes, especially to seperate
an qt4 from an qt5 installation (Host and target).
Also the x11 support got dropped - framebuffer only.
Some obvious and trivial bug fixes got applied as well,
however, apart from that, it basically is, what it was.
The Xorg feed is totally unmaintained currently,
also the early approach of running an Xserver on
embedded devices - hence the feed's name - thankfully
didn't really become the standard either.
So let's reorganise some of the stuff from the Xorg
feed worth keeping within the new Video feed.
Qt5Quick1 features QML1 and provides
the QDeclarative* implementations.
Don't confuse that with the QtDeclarative
submodule which provides support for QML2
and exports the QQml* interface (also known
as QtQuick(2)).
QtQuick(2)/QML2 by the way has a hard
dependency on GL, hence without GL support
you're stuck on QtQuick1/QML1.
Crosscompile and package Qt5 (base) and setup an
environment to easily crosscompile and package
other qmake based projects.
Please see the comments within the Makefiles
(Makefile / qmake.mk) for current limitations and
known issues.
Packaged from the "base" submodule herewith are:
- qt5base-concurrent
- qt5base-core
- qt5base-gui
- qt5base-network
- qt5base-printSupport
- qt5base-sql
- qt5base-test
- qt5base-widgets
- qt5base-xml
- qt5base-plugin-bearer-generic
- qt5base-plugin-input-evdevkeyboard
- qt5base-plugin-input-evdevmouse
- qt5base-plugin-input-evdevtablet
- qt5base-plugin-input-evdevtouch
- qt5base-plugin-imageformats-gif
- qt5base-plugin-imageformats-ico
- qt5base-plugin-imageformats-jpeg
- qt5base-plugin-platforms-linuxfb
- qt5base-plugin-platforms-minimal
- qt5base-plugin-platforms-offscreen
- qt5base-plugin-sqldrivers-sqlite
- qt5base-examples
