[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: qtwenengine anybody?
From: |
mike . rosset |
Subject: |
Re: qtwenengine anybody? |
Date: |
Wed, 18 Dec 2019 13:24:05 -0800 |
User-agent: |
Gnus/5.13 (Gnus v5.13) Emacs/26.3 (gnu/linux) |
Hartmut Goebel <address@hidden> writes:
> Am 16.12.19 um 18:09 schrieb address@hidden:
>> I'm currently brushing up my latest qtwebengine build. Will resubmit
>> this patch. I will also see if I can inherit qtsvg again to put this
>> back on par with other module packages. From there I'll put a simple
>> test example together demonstrating the locale and translation problem.
>
> Sounds good
I've resubmitted the patch it can be found here
https://lists.gnu.org/archive/html/guix-patches/2019-12/msg00530.html. My
ML patch workflow is probably not all that correct so I apologize if
there is any issues.
To summarize the package now inherits from qtsvg. The locales issues
have been resolved by substituting qtwebengine's output instead of using
qtbase.
Some dynamically loaded libraries like udev and nss have been
substituted using corresponding inputs.
Some known issues, when building with pulseaudio support. There is some
issues finding pulseaudio socket. I've disabled support for pulseaudio
until I can resolve this.
Additionally on my system when using hardware accelerated OpenGL
neuveau drivers, qtwebengine crashes this does not happen when using the
monolithic qt package. This can avoided by setting the
QT_XCB_FORCE_SOFTWARE_OPENGL to 1.
I have a simple CPP for testing it can be found
here. https://github.com/mrosset/testqt.
for testing I use this enviroment.
--8<---------------cut here---------------start------------->8---
./pre-inst-env guix environment --ad-hoc qtbase qtwebengine qtdeclarative
qtwebchannel coreutils gcc-toolchain nss-certs
--8<---------------cut here---------------end--------------->8---
and then I test with
--8<---------------cut here---------------start------------->8---
cd testqt
qmake
make
./main
--8<---------------cut here---------------end--------------->8---
or there are hardware acceleration problems
--8<---------------cut here---------------start------------->8---
QT_XCB_FORCE_SOFTWARE_OPENGL=1 ./main
--8<---------------cut here---------------end--------------->8---
I can also a substitute if anyone needs them for testing. Since this
build can take some time.
Mike
- qtwenengine anybody?, Hartmut Goebel, 2019/12/16
- Re: qtwenengine anybody?, Pierre Neidhardt, 2019/12/16
- Re: qtwenengine anybody?, mike . rosset, 2019/12/16
- Re: qtwenengine anybody?, Hartmut Goebel, 2019/12/16
- Re: qtwenengine anybody?, mike . rosset, 2019/12/16
- Re: qtwenengine anybody?, Hartmut Goebel, 2019/12/16
- Re: qtwenengine anybody?, mike . rosset, 2019/12/16
- Re: qtwenengine anybody?, Hartmut Goebel, 2019/12/16
- Re: qtwenengine anybody?,
mike . rosset <=
- Re: qtwenengine anybody?, Pierre Neidhardt, 2019/12/18
- Re: qtwenengine anybody?, mike . rosset, 2019/12/18
- Re: qtwenengine anybody?, Pierre Neidhardt, 2019/12/19
- Re: qtwenengine anybody?, mike . rosset, 2019/12/19
- Re: qtwenengine anybody?, Pierre Neidhardt, 2019/12/19
- Re: qtwenengine anybody?, mike . rosset, 2019/12/19
- Re: qtwenengine anybody?, Pierre Neidhardt, 2019/12/20
- Re: qtwenengine anybody?, Pierre Neidhardt, 2019/12/20
- Re: qtwenengine anybody?, Ricardo Wurmus, 2019/12/18
- Re: qtwenengine anybody?, Pierre Neidhardt, 2019/12/20