Re: [Interest] Building QTWebEngine

[Thiago Macieira]

On Thursday, 10 October 2019 10:54:45 PDT Simon Matthews wrote:
> Is it possible to use an older version of Chromium that will work with
> Glibc 2.12 (that's what is installed in CentOS 6)?

You don't want that. This is a browser engine, which means you really, really 
want the fixes to security issues and possibly the HTML compatibility updates.

-- 
Thiago Macieira - thiago.macieira (AT) intel.com
  Software Architect - Intel System Software Products



___
Interest mailing list
Interest@qt-project.org
https://lists.qt-project.org/listinfo/interest

Re: [Interest] No 5.12.5 for OSX?

[Andy]

I have - but I'm not sure when. I don't recall having any issues.

---
Andy Maloney  //  https://asmaloney.com
twitter ~ @asmaloney 



On Thu, Oct 10, 2019 at 2:48 PM Jason H  wrote:

> Has any Mac user updated via the Maintenance tool to use 5.12.5?
>
> I'm getting "No update
> available."___
> Interest mailing list
> Interest@qt-project.org
> https://lists.qt-project.org/listinfo/interest
>
___
Interest mailing list
Interest@qt-project.org
https://lists.qt-project.org/listinfo/interest

[Interest] No 5.12.5 for OSX?

[Jason H]

Has any Mac user updated via the Maintenance tool to use 5.12.5?

I'm getting "No update available."___
Interest mailing list
Interest@qt-project.org
https://lists.qt-project.org/listinfo/interest

Re: [Interest] Building QTWebEngine

[Simon Matthews]

On 10/9/19 5:54 PM, Thiago Macieira wrote:
> On Wednesday, 9 October 2019 16:07:46 PDT Simon Matthews wrote:
>> [simon@UserBuild qtwebengine]$ make
>> make: Nothing to be done for 'first'.
> That indicates it did not configure itself to build. I ran into this issue
> today: one of my colleagues is workng to remove Python2 from the distribution
> and then he realised that the package for qtwebengine was successfully
> compiled, but ended up empty.
>
> There's a dependency missing. Take a look at the config.summary and possibly
> config.log files to see what it was looking for and missed. Search for "will
> not be built".
>
> If you configure qtwebengine alone you'll find out more easily.
>
> I've found the following error rmessages in the source, so it may help guide
> you on what you require:
>
> QtWebEngine requires QtGui.
> Submodule qtwebengine-chromium does not exist. Run 'git submodule update --
> init'.
> QtWebEngine cannot be built in a path that contains whitespace characters.
> pkg-config is required
> Required gperf could not be found.
> Required bison could not be found.
> Required flex could not be found.
> A suitable version of python2 could not be found.
> A suitable version >= 2.27 of libc could not be found.
> khronos development headers appear to be missing (mesa/libegl1-mesa-dev)
> A suitable version of $$package could not be found. [nss dbus fontconfig]
> Could not find all necessary libraries for qpa-xcb support
>
> My money is on glibc: 2.27 is from 2018. CentOS 6 comes with 2.12.
>
Below is the fragment of the transcript of the configuration for
qtwebengine. I can probably fix most of the issues,  but the glibc
version issue isn't something that can be worked around.

Is it possible to use an older version of Chromium that will work with
Glibc 2.12 (that's what is installed in CentOS 6)?

Also, how do I configure qtwebengine on its own?

Checking for libclang...
test config.qttools_qdoc.tests.libclang FAILED
Checking for embedded...
test config.qtwebengine_core.tests.webengine-embedded-build FAILED
Checking for bison...
Found bison from path: /usr/bin/bison
test config.qtwebengine_core.tests.webengine-bison succeeded
Checking for GCC 6 or newer...
test config.qtwebengine_core.tests.webengine-extensions-gcc-version
succeeded
Checking for flex...
Found flex from path: /usr/bin/flex
test config.qtwebengine_core.tests.webengine-flex succeeded
Checking for gperf...
Found gperf from path: /usr/bin/gperf
test config.qtwebengine_core.tests.webengine-gperf succeeded
Checking for host pkg-config...
Found host pkg-config: /usr/bin/pkg-config
test config.qtwebengine_core.tests.webengine-host-pkg-config gave result
/usr/bin/pkg-config
Checking for linker supports -z noexecstack...
+ cd /home/simon/rpms/sources/qt-everywhere-src-5.13.1/config.tests &&
g++ -pipe -Wl,-z,noexecstack -o conftest-out conftest.cpp
test config.qtwebengine_core.tests.webengine-noexecstack succeeded
Checking for x11...
Trying source 0 (type pkgConfig) of library webengine-x11 ...
+ /usr/bin/pkg-config --exists --silence-errors x11
+ /usr/bin/pkg-config --modversion x11
 > 1.6.4
+ /usr/bin/pkg-config --libs-only-L x11
 >
+ /usr/bin/pkg-config --libs-only-l x11
 > -lX11
+ /usr/bin/pkg-config --cflags x11
 >
  => source accepted.
test config.qtwebengine_core.libraries.webengine-x11 succeeded
Checking for libdrm...
Trying source 0 (type pkgConfig) of library webengine-libdrm ...
+ /usr/bin/pkg-config --exists --silence-errors libdrm
+ /usr/bin/pkg-config --modversion libdrm
 > 2.4.65
+ /usr/bin/pkg-config --libs-only-L libdrm
 >
+ /usr/bin/pkg-config --libs-only-l libdrm
 > -ldrm
+ /usr/bin/pkg-config --cflags libdrm
 > -I/usr/include/libdrm
  => source accepted.
test config.qtwebengine_core.libraries.webengine-libdrm succeeded
Checking for xcomposite...
Trying source 0 (type pkgConfig) of library webengine-xcomposite ...
+ /usr/bin/pkg-config --exists --silence-errors xcomposite
+ /usr/bin/pkg-config --modversion xcomposite
 > 0.4.3
+ /usr/bin/pkg-config --libs-only-L xcomposite
 >
+ /usr/bin/pkg-config --libs-only-l xcomposite
 > -lXcomposite
+ /usr/bin/pkg-config --cflags xcomposite
 >
  => source accepted.
test config.qtwebengine_core.libraries.webengine-xcomposite succeeded
Checking for xcursor...
Trying source 0 (type pkgConfig) of library webengine-xcursor ...
+ /usr/bin/pkg-config --exists --silence-errors xcursor
+ /usr/bin/pkg-config --modversion xcursor
 > 1.1.14
+ /usr/bin/pkg-config --libs-only-L xcursor
 >
+ /usr/bin/pkg-config --libs-only-l xcursor
 > -lXcursor
+ /usr/bin/pkg-config --cflags xcursor
 >
  => source accepted.
test config.qtwebengine_core.libraries.webengine-xcursor succeeded
Checking for xi...
Trying source 0 (type pkgConfig) of library webengine-xi ...
+ /usr/bin/pkg-config --exists --silence-errors xi
+ /usr/bin/pkg-config --modversion xi
 > 1.7.8
+ /usr/bin/pkg-config --libs-only-L xi
 >
+ /usr/bin/pkg-config --libs-only-l xi
 > -lXi
+ /usr/bin/pkg-config --cflags xi
 >
  => source accepted.

Re: [Interest] Can I open QT sources in Qt Creator?

[Thiago Macieira]

On Thursday, 10 October 2019 08:03:10 PDT Oleg Gavrilchenko wrote:
> Hi! I want to open Qt sources in Qt Creator. I do not want build it,
> only navigation and see help.

You need to build first. Then you can open.

> And project is not opened. What am I doing with this?

I also recommend opening the src/src.pro files at worst. Don't open the qt.pro 
and don't open the top-level files like qtbase.pro.

-- 
Thiago Macieira - thiago.macieira (AT) intel.com
  Software Architect - Intel System Software Products



___
Interest mailing list
Interest@qt-project.org
https://lists.qt-project.org/listinfo/interest

[Interest] Can I open QT sources in Qt Creator?

[Oleg Gavrilchenko]

Hi! I want to open Qt sources in Qt Creator. I do not want build it, 
only navigation and see help.


If I open qt.pro and press "Configure" button in Qt Creator, I get some 
errors:


...

/home/oleg/src/qt-everywhere-src-5.13.1/qtbase/configure.pri(111): 
Function 'prompt' is not implemented.


/home/oleg/src/qt-everywhere-src-5.13.1/qtbase/configure.pri(111): 
Function 'prompt' is not implemented.


/home/oleg/src/qt-everywhere-src-5.13.1/qtbase/configure.pri(111): 
Function 'prompt' is not implemented.


/home/oleg/src/qt-everywhere-src-5.13.1/qtbase/configure.pri(111): 
Function 'prompt' is not implemented.


/home/oleg/src/qt-everywhere-src-5.13.1/qtbase/configure.pri(111): 
Function 'prompt' is not implemented.


/home/oleg/src/qt-everywhere-src-5.13.1/qtbase/configure.pri(119): Ran 
into infinite loop (> 1000 iterations).


Error: Qt license file was not found!

Error while parsing file /home/oleg/src/qt-everywhere-src-5.13.1/qt.pro. 
Giving up.


And project is not opened. What am I doing with this?

___
Interest mailing list
Interest@qt-project.org
https://lists.qt-project.org/listinfo/interest

[Interest] Change in open-source licensing of Qt Wayland Compositor, Qt Application Manager and Qt PDF

[Tuukka Turunen]

Hi,

Open-source licensing of Qt Wayland Compositor, Qt Application Manager and Qt 
PDF is to be changed from LGPLv3/Commercial to GPLv3/Commercial. Change becomes 
in effect with Qt 5.14 release. Going forward, these modules are no longer 
available under LGPLv3 license option. The key rationale for this is to 
increase the amount of GPLv3/Commercial licensed Qt add-ons. Blog post 
announcement of this is at: 
https://www.qt.io/blog/change-in-open-source-licensing-of-qt-wayland-compositor-qt-application-manager-and-qt-pdf

Qt Wayland Compositor and Application Manager are mainly used in complex multi 
process embedded systems. The Wayland Compositor is a special purpose module 
and is not used on desktop and mobile platforms. The module does require 
significant ongoing investments and licensing it under GPLv3 will help cover 
those expenses. The Application Manager is using the Wayland Compositor. It is 
currently not part of Qt and only available through the Automotive Suite, but 
being developed on qt-project.org. Qt PDF is a new 
module, which has not been released earlier despite the pre-release code being 
available. Changing the license to GPLv3 will allow The Qt Company to support 
the module going forward.

Since January 2016 many of the completely new Qt add-on modules developed by 
The Qt Company have been licensed under GPLv3 license for open-source users in 
addition to the commercial licensing option. We use GPLv3 license for the 
selected Qt Add-Ons in order for those making closed-source applications or 
devices to pick the commercial option when using these add-on modules, while 
still providing the functionality under an open-source license for open-source 
applications.

In addition to developers from The Qt Company, the main contributors of these 
modules are from Luxoft and KDAB. We have discussed the license change 
beforehand with both of them and they accept making this license change.

The change in licensing of Qt Wayland Compositor, Qt Application Manager and Qt 
PDF is implemented in the coming days to be in effect by Qt 5.14 release 
timeframe and later releases.

Yours,

Tuukka Turunen
The Qt Company




___
Interest mailing list
Interest@qt-project.org
https://lists.qt-project.org/listinfo/interest

Re: [Interest] Building QTWebEngine

[Allan Sandfeld Jensen]

On Thursday, 10 October 2019 01:07:46 CEST Simon Matthews wrote:
> On 10/9/19 3:52 PM, Thiago Macieira wrote:
> 
> > On Wednesday, 9 October 2019 15:18:33 PDT Simon Matthews wrote:
> > 
> >> However, it appears that files such as "Qt5WebEngineConfig.cmake" are
> >> not included in my build.
> >>
> >>
> >>
> >> Is it necessary to build QtWebEngine as a separate build?
> > 
> > No.
> >
> >
> >
> > Are you sure the build completed without errors? To be sure, go into
> > qtwebengine and type "make".
> >
> >
> 
> $ cd qt-everywhere-src-5.13.1/qtwebengine/
> /home/simon/rpms/sources/qt-everywhere-src-5.13.1/qtwebengine
> [simon@UserBuild qtwebengine]$ make
> make: Nothing to be done for 'first'.
> 
That means QtWebEngine is being skipped due to a missing dependency. If you 
clean the build dir, you can run "make qmake" there and see what fails.

'Allan


___
Interest mailing list
Interest@qt-project.org
https://lists.qt-project.org/listinfo/interest