: Sunday, March 20, 2016 7:00 PM
To: development@qt-project.org
Subject: 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
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
So, it is as I feared. When I execute qmake and then make manually from a
terminal generate-forwarding-headers.pl is called as it apparently shou
> -Original Message-
> From: Development [mailto:development-
> bounces+kai.koehne=theqtcompany@qt-project.org] On Behalf Of
> Adrian Jakel
> Sent: Sunday, March 20, 2016 7:00 PM
> To: development@qt-project.org
> Subject: Re: [Development] Problems with QtWebKi
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
Softwar
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 r
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 wr
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 getting new tarball
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
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 th
On Sunday, 20 March 2016 17:55:23 CET, René J. V. Bertin wrote:
Why on earth does this have to be so difficult
For the record, this is how my CI system builds its copy of Qt 5.6:
git clone https://code.qt.io/qt/qt5.git
cd qt5
git checkout ${QT5_TAG:-${QT5_BRANCH}}
git submodule update --init
.
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.
Wh
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 standalone in-tree bui
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 :-
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 Qt
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 this look OK?
>>
>> It's output from syncqt,
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
> generate-forwarding-head
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 qt-everywhere-opensource-src-
> 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)
=
/Users/bertin/work/src/new/Qt/qt-everywhere-opensource-s
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 header
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 of
On Saturday 19 March 2016, René J. V. Bertin wrote:
> Thiago Macieira wrote:
> > mkdir .git; qmake
>
> Followed by make -j4 at least I now get a different error (about 37 min in,
> at a stage that used to build AFAICT):
>
> Platform/CoreIPC/Connection.cpp:29:10: fatal error: 'WebCore/RunLoop.h'
>
20.03.2016, 00:25, "René J. V. Bertin" :
> Thiago Macieira wrote:
>
>> It should not be necessary, if the tarball were correct. The includes should
>> not be missing.
>
> Yeah, and I guess errors like the one I keep getting (following your
> instructions) shouldn't occur either...
>
> Platform/
Thiago Macieira wrote:
> It should not be necessary, if the tarball were correct. The includes should
> not be missing.
Yeah, and I guess errors like the one I keep getting (following your
instructions) shouldn't occur either...
Platform/CoreIPC/Connection.cpp:29:10: fatal error: 'WebCore/RunL
On sábado, 19 de março de 2016 13:50:54 CDT René J. V. Bertin wrote:
> Thiago Macieira wrote:
> > On sábado, 19 de março de 2016 09:58:34 PDT René J. V. Bertin wrote:
> >> Can you please post the correct way to invoke syncqt? The incantations I
> >
> >> tried didn't change my errors :
> > mkdir .g
Thiago Macieira wrote:
> mkdir .git; qmake
>
Followed by make -j4 at least I now get a different error (about 37 min in, at
a
stage that used to build AFAICT):
Platform/CoreIPC/Connection.cpp:29:10: fatal error: 'WebCore/RunLoop.h' file
not
found
#include
^
1 error generated.
Thiago Macieira wrote:
> On sábado, 19 de março de 2016 09:58:34 PDT René J. V. Bertin wrote:
>> Can you please post the correct way to invoke syncqt? The incantations I
>> tried didn't change my errors :
>
> mkdir .git; qmake
Should I understand that when using the qtwebkit 5.6.0 tarball from
On sábado, 19 de março de 2016 09:58:34 PDT René J. V. Bertin wrote:
> Can you please post the correct way to invoke syncqt? The incantations I
> tried didn't change my errors :
mkdir .git; qmake
--
Thiago Macieira - thiago.macieira (AT) intel.com
Software Architect - Intel Open Source Technol
Just wanted to second (third?) that.
I tried to adapt the webkit package for mxe to Qt 5.6 but ran into the
known errors. Which is the "official" source package we are about to use
when building webkit for/against Qt 5.6?
Regards,
Adrian
Am 19.03.2016 um 09:58 schrieb René J. V. Bertin:
Kon
Konstantin Tokarev wrote:
>
>
> 06.03.2016, 21:40, "Dmitry Shachnev" :
>> Hi all,
>>
>> I am currently packaging Qt 5.6 release candidate for Debian and I have
>> encountered some problems with QtWebKit.
>>
>> 1. Looks like the tarballs were build without calling syncqt. That issue was
>> easy t
On domingo, 6 de março de 2016 21:40:38 PST Dmitry Shachnev wrote:
> 2. There is a linking error when building libQt5WebKit.so on some
> architectures (arm, mipsel and s390x): it reports undefined reference to
> pthread_*, even though -lpthread is present in the command line.
>
>I compared it
On Sun, 06 Mar 2016 21:45:49 +0300, Konstantin Tokarev wrote:
>> 2. There is a linking error when building libQt5WebKit.so on some
>> architectures
>>(arm, mipsel and s390x): it reports undefined reference to pthread_*, even
>>though -lpthread is present in the command line.
>
> This patch
06.03.2016, 21:40, "Dmitry Shachnev" :
> Hi all,
>
> I am currently packaging Qt 5.6 release candidate for Debian and I have
> encountered some problems with QtWebKit.
>
> 1. Looks like the tarballs were build without calling syncqt. That issue was
> easy to work-around and we are now calling
Hi all,
I am currently packaging Qt 5.6 release candidate for Debian and I have
encountered some problems with QtWebKit.
1. Looks like the tarballs were build without calling syncqt. That issue was
easy to work-around and we are now calling syncqt before the build. However
it would be nice
33 matches
Mail list logo
