Re: [Development] QtWebEngine unbundled of third-party libraries on Linux

2015-09-16 Thread Lisandro Damián Nicanor Pérez Meyer
On Friday 11 September 2015 19:26:22 Allan Sandfeld Jensen wrote:
[snip]
> > [Exactly one month later...]
> > 
> > I'll try to check this during the weekend. I'm terribly sorry for not
> > doing
> > it sooner, but life gets in the middle too much lately :-/

As it happened again, I'm trying to catch up now.

I failed to see relevant changes between 5.5 and 5.6 in the qtwebengine 
submodule git repo. Maybe I should look somewhere else?

[snip]
> Btw. If you know the people packaging Chromium, you could point them my way,
> we could probably share patches.

Not really, only thing I know is that their mailing list is

 https://lists.alioth.debian.org/mailman/listinfo/pkg-chromium-maint

and the git repository is

 http://anonscm.debian.org/cgit/pkg-chromium/pkg-chromium.git

Check for patches in debian/patches subdir.

We used to have a patch tracker but sadly it's not working anymore :(

-- 
http://xkcd.com/162/

Lisandro Damián Nicanor Pérez Meyer
http://perezmeyer.com.ar/
http://perezmeyer.blogspot.com/

___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development


Re: [Development] QtWebEngine unbundled of third-party libraries on Linux

2015-09-11 Thread Allan Sandfeld Jensen
On Friday 11 September 2015, Lisandro Damián Nicanor Pérez Meyer wrote:
> On Tuesday 11 August 2015 23:17:31 Allan Sandfeld Jensen wrote:
> > Hello Qt
> > 
> > QtWebEngine and Chromium in the Qt 5.6 branch have been patched to allow
> > linking with system libraries on Linux instead of bundled libraries. For
> > most libraries the system library will be used if development files are
> > detected on the system. ICU and FFMPEG however defaults to using the
> > bundled copies and requires using qmake arguments to configure to use
> > system versions. The required arguments are listed in qmake configure
> > status (just delete .qmake.cache and run qmake to run the configure step
> > again). Note that for FFMPEG, the libav libraries from the FFMPEG project
> > are required, the libraries from the libav project does not work.
> > 
> > I have so far only tested on Debian. If more people could test it we
> > could also get better detection and set proper minimal versions.
> > 
> > If you are a packager and more is required before QtWebEngine can be
> > packaged on your distribution, please let me know.
> 
> [Exactly one month later...]
> 
> I'll try to check this during the weekend. I'm terribly sorry for not doing
> it sooner, but life gets in the middle too much lately :-/
> 
> Do you think it would be possible to build it against Qt 5.5? Just for
> testing purposes, of course.

Yes it does, and I intend to to keep it that way :D It is not a supported 
configuration, but to the extend it is possible, I will try to make Qt 
WebEngine build with one version older Qt. With QtWebKit I kept it working 
with two version older, but WebEngine moves much faster and has a tight 
integration with the scene graph, so let's see. 

Btw. If you know the people packaging Chromium, you could point them my way, 
we could probably share patches.

Best regards
`Allan

___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development


Re: [Development] QtWebEngine unbundled of third-party libraries on Linux

2015-09-11 Thread Lisandro Damián Nicanor Pérez Meyer
On Tuesday 11 August 2015 23:17:31 Allan Sandfeld Jensen wrote:
> Hello Qt
> 
> QtWebEngine and Chromium in the Qt 5.6 branch have been patched to allow
> linking with system libraries on Linux instead of bundled libraries. For
> most libraries the system library will be used if development files are
> detected on the system. ICU and FFMPEG however defaults to using the
> bundled copies and requires using qmake arguments to configure to use
> system versions. The required arguments are listed in qmake configure
> status (just delete .qmake.cache and run qmake to run the configure step
> again). Note that for FFMPEG, the libav libraries from the FFMPEG project
> are required, the libraries from the libav project does not work.
> 
> I have so far only tested on Debian. If more people could test it we could
> also get better detection and set proper minimal versions.
> 
> If you are a packager and more is required before QtWebEngine can be
> packaged on your distribution, please let me know.

[Exactly one month later...]

I'll try to check this during the weekend. I'm terribly sorry for not doing it 
sooner, but life gets in the middle too much lately :-/

Do you think it would be possible to build it against Qt 5.5? Just for testing 
purposes, of course.

-- 
Hacer algo siempre te llevará más tiempo del que esperabas, incluso si
tienes en cuenta la ley de Hofstadter.
  Douglas Hofstadter
  http://mundogeek.net/archivos/2009/09/05/la-ley-de-hofstadter/

Lisandro Damián Nicanor Pérez Meyer
http://perezmeyer.com.ar/
http://perezmeyer.blogspot.com/

___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development


Re: [Development] QtWebEngine unbundled of third-party libraries on Linux

2015-08-12 Thread Lisandro Damián Nicanor Pérez Meyer
On Tuesday 11 August 2015 23:17:31 Allan Sandfeld Jensen wrote:
> Hello Qt
> 
> QtWebEngine and Chromium in the Qt 5.6 branch have been patched to allow
> linking with system libraries on Linux instead of bundled libraries. For
> most libraries the system library will be used if development files are
> detected on the system. ICU and FFMPEG however defaults to using the
> bundled copies and requires using qmake arguments to configure to use
> system versions. The required arguments are listed in qmake configure
> status (just delete .qmake.cache and run qmake to run the configure step
> again). Note that for FFMPEG, the libav libraries from the FFMPEG project
> are required, the libraries from the libav project does not work.
> 
> I have so far only tested on Debian. If more people could test it we could
> also get better detection and set proper minimal versions.
> 
> If you are a packager and more is required before QtWebEngine can be
> packaged on your distribution, please let me know.

I will of course take a look, but I highly doubt I'll be able to build it for 
a couple of weeks at least.

And really *thank you* for this :)


-- 

Lisandro Damián Nicanor Pérez Meyer
http://perezmeyer.com.ar/
http://perezmeyer.blogspot.com/


signature.asc
Description: This is a digitally signed message part.
___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development


Re: [Development] QtWebEngine unbundled of third-party libraries on Linux

2015-08-12 Thread Allan Sandfeld Jensen
On Wednesday 12 August 2015, Robert Knight wrote:
> > QtWebEngine and Chromium in the Qt 5.6 branch have been patched to
> > allow linking with system libraries on Linux instead of bundled
> > libraries.
> 
> What upstream changes have the Chromium team made to the bundled libraries
> compared to the system ones and are Chromium upstream supportive of taking
> patches to facilitate using system libraries?
> 
> I'm concerned that unbundling the libraries will break things - either via
> bugs, features that stop working or security fixes that are missing from
> system libs.
> 
Most of the libraries we have unbundled are semi-officially supported as 
unbundled upstream. Chromium provides scripts that replaces and patches the 
build scripts before building Chromium. These are used by some Linux distros 
to unbundle libraries already. The scripts are however not well maintained, 
and we do not want to change source-files as part of the build process, so 
instead we have integrated the code-paths from the replacements into the 
original build-script files, and fixed and updated them where necessary.

There are two libraries not unbundled: sqlite3 and leveldatabase, due to 
Chromium having modified these adding new Chromium specific APIs. Chromium 
also use internal/draft API of FFMPEG and ICU each in one place, which is why 
these are not unbundled by default.  For ICU it should not be a problem 
however, they appear to be using draft API due to them misunderstanding how 
the normal API works. For FFMPEG, it seems to be some specific patching of 
synchronization, I haven't encountered any issues from just disabling that 
code though.

As for security fixes, the idea is to get faster security updates, as the 
system libraries are fixed much faster than both Chromium and QtWebEngine.

Best regards
`Allan
___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development


Re: [Development] QtWebEngine unbundled of third-party libraries on Linux

2015-08-11 Thread Robert Knight
> QtWebEngine and Chromium in the Qt 5.6 branch have been patched to
> allow linking with system libraries on Linux instead of bundled libraries.

What upstream changes have the Chromium team made to the bundled libraries
compared to the system ones and are Chromium upstream supportive of taking
patches to facilitate using system libraries?

I'm concerned that unbundling the libraries will break things - either via
bugs, features that stop working or security fixes that are missing from
system libs.

On 11 August 2015 at 22:17, Allan Sandfeld Jensen  wrote:

> Hello Qt
>
> QtWebEngine and Chromium in the Qt 5.6 branch have been patched to allow
> linking with system libraries on Linux instead of bundled libraries. For
> most
> libraries the system library will be used if development files are
> detected on
> the system. ICU and FFMPEG however defaults to using the bundled copies and
> requires using qmake arguments to configure to use system versions. The
> required arguments are listed in qmake configure status (just delete
> .qmake.cache and run qmake to run the configure step again). Note that for
> FFMPEG, the libav libraries from the FFMPEG project are required, the
> libraries from the libav project does not work.
>
> I have so far only tested on Debian. If more people could test it we could
> also get better detection and set proper minimal versions.
>
> If you are a packager and more is required before QtWebEngine can be
> packaged
> on your distribution, please let me know.
>
> Best regards
> `Allan Jensen
>
> --
>
> The Qt Company
> Rudower Chausse 13, 12489 D-Berlin
>
> The Qt Company is a group company of Digia Plc,
> Valimotie 21, FI-00380 Helsinki Finland
> ___
> Development mailing list
> Development@qt-project.org
> http://lists.qt-project.org/mailman/listinfo/development
>
___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development


[Development] QtWebEngine unbundled of third-party libraries on Linux

2015-08-11 Thread Allan Sandfeld Jensen
Hello Qt

QtWebEngine and Chromium in the Qt 5.6 branch have been patched to allow 
linking with system libraries on Linux instead of bundled libraries. For most 
libraries the system library will be used if development files are detected on 
the system. ICU and FFMPEG however defaults to using the bundled copies and 
requires using qmake arguments to configure to use system versions. The 
required arguments are listed in qmake configure status (just delete 
.qmake.cache and run qmake to run the configure step again). Note that for 
FFMPEG, the libav libraries from the FFMPEG project are required, the 
libraries from the libav project does not work.

I have so far only tested on Debian. If more people could test it we could 
also get better detection and set proper minimal versions.

If you are a packager and more is required before QtWebEngine can be packaged 
on your distribution, please let me know.

Best regards
`Allan Jensen

-- 
 
The Qt Company
Rudower Chausse 13, 12489 D-Berlin
 
The Qt Company is a group company of Digia Plc, 
Valimotie 21, FI-00380 Helsinki Finland
___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development