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
Le vendredi 31 juillet 2015 à 09:01 -0700, Thiago Macieira a écrit :
thiago.macie...@intel.com wrote:
In this particular case, it was reasoned that the API was inconsistent and
broken. So the behaviour was changed intentionally.
TBH, it looks like it's still inconsistent (an empty
On Monday 10. August 2015 16.34.49 Oswald Buddenhagen wrote:
On Mon, Aug 10, 2015 at 02:36:34PM +0200, Paul Olav Tvete wrote:
So what we are talking about here is the platform plugin for Mir servers,
together with a Qt Quick plugin for writing a Mir compositor.
i'm confused ... what is
Hi,
i would like to request a new qt module repository for QtGeniviExtras.
The current code can be found here:
https://github.com/Pelagicore/qtgeniviextras
The goal of QtGeniviExtras is similar to QtWinExtras or QtMacExtras and
provides Platform dependent Qt additions. In this case for the
On Monday 10. August 2015 16.34.49 Oswald Buddenhagen wrote:
would the repository be imported as-is (git fast-import from bzr),
filter-branched, or re-created?
I think fast-import is the simplest. There are probably some packaging related
configuration files that are not relevant in the Qt
On Tuesday 11 August 2015 10:38:27 Julien Blanc wrote:
That point is certainly valid, but i would like to raise the point that
string nullness is a *required* feature for QtSQL (a null QString is
converted to a NULL SQL, whereas a non-null empty QString is converted
That's a misfeature. QtSql
On Tuesday 11 August 2015 09:59:19 Dominik Holland wrote:
Hi,
i would like to request a new qt module repository for QtGeniviExtras.
The current code can be found here:
https://github.com/Pelagicore/qtgeniviextras
The goal of QtGeniviExtras is similar to QtWinExtras or QtMacExtras and
Le mardi 11 août 2015 à 08:46 -0700, Thiago Macieira a écrit :
On Tuesday 11 August 2015 10:38:27 Julien Blanc wrote:
That point is certainly valid, but i would like to raise the point that
string nullness is a *required* feature for QtSQL (a null QString is
converted to a NULL SQL,
On Tuesday 11 August 2015 19:09:22 Allan Sandfeld Jensen wrote:
I would second that. We can argue that the null vs empty is a misfeature we
like to discourage because it is likely to break in some corner-cases, but
until we get rid of it (Qt6), there is no reason to not try to be
consistent,
On Tuesday 11 August 2015, Julien Blanc wrote:
Le mardi 11 août 2015 à 08:46 -0700, Thiago Macieira a écrit :
On Tuesday 11 August 2015 10:38:27 Julien Blanc wrote:
That point is certainly valid, but i would like to raise the point that
string nullness is a *required* feature for QtSQL (a
On Tuesday 11 August 2015 18:45:10 Julien Blanc wrote:
Le mardi 11 août 2015 à 08:46 -0700, Thiago Macieira a écrit :
On Tuesday 11 August 2015 10:38:27 Julien Blanc wrote:
That point is certainly valid, but i would like to raise the point that
string nullness is a *required* feature for
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
12 matches
Mail list logo
