Re: [Development] Problems with QtWebKit 5.6 / Please do not remove QtWebkit from 5.6 official binaries

On domingo, 20 de março de 2016 10:09:26 GMT René J. V. Bertin wrote: > So it might even be that if I check out the repo as "qtwebkit" in the > monolithic source tree, qtwebkit will build just fine as it always did? Yes, very likely. -- Thiago Macieira - thiago.macieira (AT) intel.com

Re: [Development] Problems with QtWebKit 5.6 / Please do not remove QtWebkit from 5.6 official binaries

I think I have a lead on my issue, but I don't really know yet how to follow it. As it turns out, the following sequence succeeds: - checkout qtwebkit.git - (cd qtwebkit.git ; syncqt.pl Source -version 5.6.0) - mkdir build ; cd build - qmake ../qtwebkit.git/WebKit.pro - make -j4 The goal is to

Re: [Development] Problems with QtWebKit 5.6 / Please do not remove QtWebkit from 5.6 official binaries

Giuseppe D'Angelo wrote: > Technically speaking it could also just means getting new tarballs for > qtwebkit 5.6.0 (as it's merely a packaging issue; there are no code > changes required)... Maybe to the some of the build system code, if the build issues I'm seeing are the result of something

Re: [Development] MSVC2012 in CI

On domingo, 20 de março de 2016 12:07:01 GMT Sean Harmer wrote: > Hi, > > Can MSVC 2012 configurations be removed from the CI please? My understanding > is that this compiler was only kept around to support Windows EC but that > this is now removed from 5.7. In particular this compiler is a

Re: [Development] Problems with QtWebKit 5.6 / Please do not remove QtWebkit from 5.6 official binaries

On Sun, Mar 20, 2016 at 6:59 PM, Adrian Jäkel wrote: > Out of curiosity and because it has not been said in the discussion afaik: > Is it planned to correct the current tarball or at least the next one for > the upcoming Qt 5.6.1 ? Technically speaking it could also just means

Re: [Development] Problems with QtWebKit 5.6 / Please do not remove QtWebkit from 5.6 official binaries

Out of curiosity and because it has not been said in the discussion afaik: Is it planned to correct the current tarball or at least the next one for the upcoming Qt 5.6.1 ? It seems like an easy fix to me and im wondering why it hasnt been done yet? Or am i missing something? Regards, Adrian

Re: [Development] Problems with QtWebKit 5.6 / Please do not remove QtWebkit from 5.6 official binaries

Jan Kundrát wrote: > Anyway, this is just another anecdote that it was actually pretty easy to > get QtWebKit from the 5.6 branch (on Linux, though). Great, so if and when I get around to repeating all this on a Linux host it should be easy as cake... Anyway, I've been suspicious at the fact

Re: [Development] Problems with QtWebKit 5.6 / Please do not remove QtWebkit from 5.6 official binaries

Konstantin Tokarev wrote: >> So how am I supposed to invoke generate-forwarding-headers.pl ? > > No, it should be execute as a part of build process Apparently the one from Makefile.WebKit2.DerivedSources hasn't been executed at the time the error occurs. Nor has the one from WebCore, btw.

Re: [Development] Problems with QtWebKit 5.6 / Please do not remove QtWebkit from 5.6 official binaries

20.03.2016, 18:32, "René J. V. Bertin" : > René J.V. Bertin wrote: > >>  On Sunday March 20 2016 15:01:01 Konstantin Tokarev wrote: > >>> Do I understand correctly that you were trying to build QtWebKit in >>> non-shadow >>> way? This is not supported. > >>  But indeed the

Re: [Development] Problems with QtWebKit 5.6 / Please do not remove QtWebkit from 5.6 official binaries

René J.V. Bertin wrote: > On Sunday March 20 2016 15:01:01 Konstantin Tokarev wrote: >>Do I understand correctly that you were trying to build QtWebKit in non-shadow >>way? This is not supported. > But indeed the standalone in-tree build just failed again for me, using the > same git checkout

Re: [Development] Qt Coding Guidelines

I agree with Rich. This isn't documentation our users are facing. We don't need to extract from cpp files or use a particular style sheet. +1 for Kai's initiative. Simon From: Richard Moore Sent: Wednesday, March 16, 2016 22:55 To: Knoll Lars Cc: development@qt-project.org Subject: Re:

Re: [Development] Qt Coding Guidelines

On Friday 18 March 2016 15:37:40 André Somers wrote: > Op 18/03/2016 om 09:24 schreef Rutledge Shawn: > > Forcing it on everyone that way will be controversial, because there > > is still some leeway in formatting, whereas automation would remove > > any chance of personal preference, and probably

Re: [Development] Problems with QtWebKit 5.6 / Please do not remove QtWebkit from 5.6 official binaries

On Sunday March 20 2016 15:01:01 Konstantin Tokarev wrote: >> Anyway, a legacy-style monolithic *shadow* build with qtwebkit alongside the >> other Qt5 components just completed OK so at least now we know that this is >> still possible. > >Do I understand correctly that you were trying to build

Re: [Development] Qt Coding Guidelines

Thiago Macieira said: > We have a qdoc generator. We don't have a markdown generator. > > More importantly, we know how to write qdoc syntax. There is also an "eat our own dog-food" argument somewhere here: we ask developers to document their code in qdoc, so we should be happy to use it

[Development] MSVC2012 in CI

Hi, Can MSVC 2012 configurations be removed from the CI please? My understanding is that this compiler was only kept around to support Windows EC but that this is now removed from 5.7. In particular this compiler is a blocker to using a using declaration such as: template using

Re: [Development] Problems with QtWebKit 5.6 / Please do not remove QtWebkit from 5.6 official binaries

20.03.2016, 14:48, "René J. V. Bertin" : > Konstantin Tokarev wrote: > >>  20.03.2016, 13:13, "René J.V. Bertin" :  Look in build log for generate-forwarding-headers.pl invocation. Does it  produce any errors? >>> >>> >>> >>>  Does

Re: [Development] Problems with QtWebKit 5.6 / Please do not remove QtWebkit from 5.6 official binaries

Konstantin Tokarev wrote: > > > 20.03.2016, 13:13, "René J.V. Bertin" : >>> Look in build log for generate-forwarding-headers.pl invocation. Does it >>> produce any errors? >> >>> >> >>> >> >> Does this look OK? > > > It's output from syncqt, and I've asked you about >

Re: [Development] Problems with QtWebKit 5.6 / Please do not remove QtWebkit from 5.6 official binaries

20.03.2016, 13:13, "René J.V. Bertin" : >> Look in build log for generate-forwarding-headers.pl invocation. Does it >> produce any errors? > >> > >> > > Does this look OK? It's output from syncqt, and I've asked you about generate-forwarding-headers.pl > > %> (cd

Re: [Development] Problems with QtWebKit 5.6 / Please do not remove QtWebkit from 5.6 official binaries

> Look in build log for generate-forwarding-headers.pl invocation. Does it > produce any errors? > > Does this look OK? %> (cd qt-everywhere-opensource-src-5.6.0/qtwebkit ; /opt/local/libexec/qt5/bin/syncqt.pl Source -version 5.6.0) =

Re: [Development] Problems with QtWebKit 5.6 / Please do not remove QtWebkit from 5.6 official binaries

Konstantin Tokarev wrote: >> #include >> ^ >> 1 error generated. > > Look in build log for generate-forwarding-headers.pl invocation. Does it > produce any errors? I don't think I noticed any errors in the output from syncqt, but I'll double check. I'm not seeing this kind of errors on

Re: [Development] Problems with QtWebKit 5.6 / Please do not remove QtWebkit from 5.6 official binaries

Allan Sandfeld Jensen wrote: >> Has qtwebkit been test-built on OS X at all? >> > Yes, it is automatically build on several OS X versions in different > configurations as part of the CI system, but that is from git, not from the > source packages. I don't think anyone tested the final packages

Re: [Development] Qt Coding Guidelines

> On 16 Mar 2016, at 22:43, Knoll Lars wrote: > > We should actually consider having a section about contributing to Qt in our > documentation. Coding guidelines would fit nicely into that. But I think the > .qdoc files should rather live in qtdoc instead of

Re: [Development] Qt Coding Guidelines

On Friday, March 18, 2016 10:46:41 AM Koehne Kai wrote: > > -Original Message- > > From: Development [mailto:development- > > [...] > > It remains that this document is expected to be quite stable, so there > > would be some sense to having a stable URL to which we routinely copy the > >

Re: [Development] [OS X] next Qt 5.6.0 question : Freetype (building with -fontconfig)?

On Friday, March 18, 2016 02:52:42 PM René J. V. Bertin wrote: > Till Oliver Knoll wrote: > > According to > > > > https://wiki.qt.io/New_Features_in_Qt_5.6 > > > > "Optional support for using FreeType on Mac OS X" is now available. > > Yeah, but apparently not exactly as planned: Where was

Re: [Development] [Releasing] HEADS UP: Updates to Qt 5.7 (and Qt 5.8) tool versions

> > Visual Studio 2015 Update 1 to Windows 10 > > Please let’s keep in mind that Visual Studio 2015 Update 2 is coming out, > I don’t think that it will be ready for Qt 5.7, but we should be prepared > for Qt 5.8 indeed. > > Regards, > Diego > +1 --charley