Re: [Development] Nominating Szabolcs David as Approver

2022-09-20 Thread Michal Klocek
+1

definitely well deserved, to be honest I was not aware he is not a approver.

Br

Michal


From: Development  on behalf of Allan 
Sandfeld Jensen 
Sent: Monday, 19 September 2022 16:51
To: development@qt-project.org 
Subject: [Development] Nominating Szabolcs David as Approver

Hi,

I'd like to propose Szabolcs David as an Qt Project Approver.

Dashboard: https://codereview.qt-project.org/dashboard/1002939

Szabolcs has been working for us as an external contributor for at least 8
years now. With that many years of experience contributing to Qt WebEngine, I
think it is about time we grant him approver rights.

Best regards,
Allan Sandfeld Jensen




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


Re: [Development] Merging qtquickcontrols2 into qtdeclarative

2021-07-13 Thread Michal Klocek
Hi

Please note qtpdf repository was merged into qtwebengine, authors wanted to 
keep all the history so it was kept and git blame works nicely. However, 
qtwebengine git repo is anyway big in size so adding extra ~100 commits did not 
have much impact.

https://codereview.qt-project.org/c/qt/qtwebengine/+/270649

Br

Michal

From: Development  on behalf of Elvis 
Stansvik 
Sent: Tuesday, 13 July 2021 13:23
To: Qt development mailing list 
Subject: Re: [Development] Merging qtquickcontrols2 into qtdeclarative

Den tis 13 juli 2021 kl 10:45 skrev Oswald Buddenhagen
:
>
> >On 12 Jul 2021, at 21:19, Thiago Macieira 
> >wrote:
> >> So a full history import MAY have negligible marginal impact over a
> >> squashed import (.git is compressed).
> >
> that might be the case.
>
> but the point remains that the history that didn't exist along the
> merged mainline would live elsewhere (unless we'd import all branches
> and tags as well - we actually did that in qt creator, and it looks
> kinda weird and confusing).
>
> On Mon, Jul 12, 2021 at 11:22:54PM +0200, Elvis Stansvik wrote:
> >Personally I'm always frustrated when I hit a dead end during git
> >blame.
>
> >Even if the original repo will be kept around, it's an added
> >obstacle.
> >
> a rather small obstacle, given that we have a git-qt-grafts script that
> pretty much completely automates the process (it would actually need a
> bit of a revamp by now).

Yea, I just thought it a good idea to follow Thiago's suggestion to
see what the cost would be to do a full history import. But I may have
misunderstood what is even possible and not.

As an outsider doing a sort of drive-by git blame trying to find the
rationale for something, I may not know about special tooling that Qt
has.

But yes, you folks who work day to day on Qt should decide. Just
wanted to chime in with my opinion.

>
> >And at some point, I'm sure it will no longer be available.
> >
> we keep around all repos. the remote may just need an adjustment to
> point to {graveyard}/.

Alright, that's good. In the project I was digging through the other
week, the commit that added the code didn't even say where it came
from, just something like "Code moved from old repo", and after
extensive searching I concluded that "old repo" was no longer online.

Qt being a more serious project, I'm sure you guys will leave a better
commit message and won't start bulldozing over your {graveyard}/ :)

Elvis

>
> (speaking of which, it might be actually time to do that with qt.git,
> rather than only renaming it.)
> ___
> Development mailing list
> Development@qt-project.org
> https://lists.qt-project.org/listinfo/development
___
Development mailing list
Development@qt-project.org
https://lists.qt-project.org/listinfo/development
___
Development mailing list
Development@qt-project.org
https://lists.qt-project.org/listinfo/development


Re: [Development] Nominating Kirill Burtsev as Approver

2019-09-02 Thread Michal Klocek
+1

On 8/30/19 11:38 AM, Jüri Valdmann wrote:
> +1
> 
> *From:* Development  on behalf of 
> Alexandru Croitor 
> *Sent:* Thursday, August 29, 2019 4:08 PM
> *To:* Allan Sandfeld Jensen 
> *Cc:* Qt development mailing list 
> *Subject:* Re: [Development] Nominating Kirill Burtsev as Approver
> +1
> 
>> On 29. Aug 2019, at 15:29, Allan Sandfeld Jensen  wrote:
>> 
>> On Thursday, 29 August 2019 14:54:45 CEST Michael Bruning wrote:
>>> Hi all,
>>> 
>>> I would like to nominate Kirill Burtsev as approver for the Qt Project.
>>> Kirill joined the Qt WebEngine team about a year ago and has been mainly
>>> contributing to the web engine module, but also to qtbase and
>>> qtdeclarative. I trust that he will follow Qt guidelines and will use the
>>> approver rights responsibly.
>>> 
>>> Here is his list of changes:
>>> https://codereview.qt-project.org/q/owner:kirill.burtsev%2540qt.io>> odereview.qt-project.org/q/owner:kirill.burtsev%40qt.io>
>>> 
>>> and reviews:
>>> https://codereview.qt-project.org/q/reviewer:kirill.burtsev%2540qt.io>> //codereview.qt-project.org/q/reviewer:kirill.burtsev%40qt.io>
>>> 
>>> Disclaimer: we are working in the same company and the same team.
>>> 
>> 
>> +1 :)
>> 
>> 'Allan
>> 
>> 
>> ___
>> Development mailing list
>> Development@qt-project.org
>> https://lists.qt-project.org/listinfo/development
> 
> ___
> Development mailing list
> Development@qt-project.org
> https://lists.qt-project.org/listinfo/development
> 
> ___
> Development mailing list
> Development@qt-project.org
> https://lists.qt-project.org/listinfo/development
> 
___
Development mailing list
Development@qt-project.org
https://lists.qt-project.org/listinfo/development


Re: [Development] Assistant WebKit/WebEngine support

2019-06-26 Thread Michal Klocek
Could you explain how did you measure web engine memory consumption to 
get 14-20MB of ram ?

On 6/26/19 1:12 PM, Simon Hausmann wrote:
> 
> Am 25.06.19 um 23:53 schrieb Konrad Rosenbaum:
>> Option 4: convert to WebEngine
>> Pros: looks great; currently supported browser engine, only little
>> porting work
>> Cons: horrible memory footprint; acute terminal featuritis; adds lots of
>> dependencies (disqualifies it for most/many people redistributing it);
>> does not work on all platforms supported by Qt (makes assistant less
>> useful or even useless to those users); embedding in IDEs becomes much
>> more difficult (dependencies and #ifdef's for unsupported platforms)
> 
> 
> I'd really like to eliminate this myth of a "horrible memory footprint".
> I sent an email earlier in this thread regarding this and presented
> numbers that suggest otherwise for documentation content.
> 
> 
> 
> Simon
> 
> 
> ___
> Development mailing list
> Development@qt-project.org
> https://lists.qt-project.org/listinfo/development
> 
___
Development mailing list
Development@qt-project.org
https://lists.qt-project.org/listinfo/development


Re: [Development] QtWebEngine file path too long

2019-03-13 Thread Michal Klocek
See https://bugreports.qt.io/browse/QTBUG-59769, patch (workaround) is 
included in bug report.

Br

Michal


On 3/12/19 11:44 PM, Samuel Gaist wrote:
> Hi,
> 
> I’ve been hit by this surprising error when building QtWebEngine.
> 
> Luckily (well…) I was recently facing the same issue while trying to build a 
> conda package. Searching how to fix that gave me a solution that is also 
> working for the build of QtWebEngine.
> 
> As it turns out, it was due to me building this stuff on an encrypted 
> partition.
> 
> The solution currently is to move the build out of the encrypted partition.
> 
> Best regards
> 
> Samuel
> ___
> Development mailing list
> Development@qt-project.org
> https://lists.qt-project.org/listinfo/development
> 
___
Development mailing list
Development@qt-project.org
https://lists.qt-project.org/listinfo/development


Re: [Development] HEADS-UP: Branching from '5.12' to '5.12.1' started

2019-01-30 Thread Michal Klocek
This suggestion is already in JIRA see

https://bugreports.qt.io/browse/QTBUG-71579

Br

Michal


On 01/30/2019 11:29 AM, Kai Koehne wrote:
>> -Original Message-
>> From: Development  On Behalf Of
>> Mark De Wit
>> Sent: Wednesday, January 30, 2019 11:13 AM
>> To: development@qt-project.org
>> Subject: Re: [Development] HEADS-UP: Branching from '5.12' to '5.12.1' 
>> started
>>
>> Selecting MSVC 2015 64-bit + Qt WebEngine for 5.12.1 in the installer does 
>> not
>> give me WebEngine.  Is that intentional?  
> 
> Yes, this is intentional. Qt WebEngine in 5.12 only supports MSVC 2017, that 
> was the case already for Qt 5.12.0.
> 
>> Should the installer perhaps warn
>> that the selected combination is unsupported?
> 
> Maybe, though getting a warning every time might be a bit too much, too. 
> Also, I'm not sure how and whether such a warning can be implemented ...
> 
> At least the description of the Qt WebEngine module says
> 
>   On Windows, the module is only available under MSVC 2017
> 
> Kai 
> ___
> Development mailing list
> Development@qt-project.org
> https://lists.qt-project.org/listinfo/development
> 
___
Development mailing list
Development@qt-project.org
https://lists.qt-project.org/listinfo/development


Re: [Development] Qt 5.12 beta2 released

2018-10-17 Thread Michal Klocek
I am sorry for delay, I know it is important issue so marked it for
5.11.3 now. Patches have to go though coin still, which may take a while.

Br

Michal

On 10/17/2018 09:10 AM, Mark De Wit wrote:
> What is the criteria for blocker?   It would be great if WebEngine were 
> usable again for people behind proxies (my last usable Qt release is 5.9)...
> 
> https://bugreports.qt.io/browse/QTBUG-69281  is marked as P1 but not targeted 
> at 5.12?
> 
> Kind regards,
> Mark
> 
> -Original Message-
> From: Development  
> On Behalf Of Jani Heikkinen
> Sent: 16 October 2018 11:49
> To: releas...@qt-project.org
> Cc: development@qt-project.org
> Subject: [Development] Qt 5.12 beta2 released
> 
> Hi all,
> 
> We have published Qt 5.12 beta2 today. As earlier you can get it via online 
> installer. Delta to beta1 attached.
> 
> Please test the packages now & report all findings to Jira. Also make sure 
> all release blockers can be found from release blocker list 
> (https://bugreports.qt.io/issues/?filter=19961). It is really time to test 
> the packages now; plan is to release Qt 5.12.0 final at the end of November.
> 
> br,
> Jani
> ___
> 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] Nominating Jüri Valdmann for Approver status

2018-04-27 Thread Michal Klocek
Hi

I would like to nominate Jüri Valdmann for Approver.

He joined The Qt Company more than one year ago and he's been doing most
of his excellent work for QtWebEngine.

You can see his contributions here:

https://codereview.qt-project.org/#/q/owner:%22J%C3%BCri%20Valdmann%22,n,z

Br

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


Re: [Development] ERROR: Feature 'webengine-system-libwebp' was enabled, but the pre-condition 'libs.webengine-webp' failed.

2018-03-12 Thread Michal Klocek
Hi

With 'system-webengine-webp' option you are trying to force qwebenigne
to use system webp. WebEngine uses pkg-config for webp, there is no
separate test, you can check it yourself with:

pkg-config --libs libwebp libwebpmux libwebpdemux

Br

Michal

On 03/12/2018 11:07 AM, YuGiOhJCJ Mailing-List via Development wrote:
> Hello,
> 
> I am trying to build Qt 5.10.1 on Slackware64 14.2 with the 
> "-system-webengine-webp" option and libwebp 0.6.1:
> ---
> $ ./configure -v \
> [...]
>   -system-assimp \
>   -system-doubleconversion \
>   -system-freetype \
>   -system-harfbuzz \
>   -system-libjpeg \
>   -system-libpng \
>   -system-pcre \
>   -system-sqlite \
>   -system-xcb \
>   -system-webengine-icu \
>   -system-webengine-ffmpeg \
>   -system-webengine-opus \
>   -system-webengine-webp \
>   -system-zlib \
> [...]
>   -pulseaudio
> [...]
> Note: Also available for Linux: linux-clang linux-icc
> 
> Note: -headerdir is not a subdirectory of -prefix.
> Note: -libdir is not a subdirectory of -prefix.
> Note: -docdir is not a subdirectory of -prefix.
> 
> Note: -optimized-tools is not useful in -release mode.
> 
> Note: Dropped compiler flags '-pthread' when detecting library 'glib'.
> 
> Note: Dropped compiler flags '-pthread' when detecting library 'gtk3'.
> 
> Note: No wayland-egl support detected. Cross-toolkit compatibility disabled.
> 
> Note: Dropped compiler flags '-pthread' when detecting library 'gstreamer'.
> 
> Note: Dropped compiler flags '-pthread' when detecting library 
> 'gstreamer_app'.
> 
> Note: Dropped compiler flags '-pthread' when detecting library 
> 'webengine-protobuf'.
> 
> ERROR: Feature 'webengine-system-libwebp' was enabled, but the pre-condition 
> 'libs.webengine-webp' failed.
> 
> ERROR: Feature 'webengine-system-ffmpeg' was enabled, but the pre-condition 
> 'libs.webengine-ffmpeg && features.webengine-system-opus && 
> features.webengine-system-libwebp' failed.
> ---
> 
> As you can see in the output above, the error is about the libwebp library 
> that is not found (or at least that is not working correctly).
> 
> However, I found the test file that is checking the libwebp library and I 
> tried it manually:
> ---
> $ cd qtimageformats/config.tests/libwebp
> $ qmake libwebp.pro
> $ make
> g++ -c -pipe -O2 -Wall -W  -I/usr/lib64/qt/mkspecs/linux-g++ -I. -o libwebp.o 
> libwebp.cpp
> libwebp.cpp: In function ‘int main(int, char**)’:
> libwebp.cpp:40:20: warning: unused variable ‘output_buffer’ 
> [-Wunused-variable]
>  WebPDecBuffer *output_buffer = 
> ^
> libwebp.cpp:41:28: warning: unused variable ‘bitstream’ [-Wunused-variable]
>  WebPBitstreamFeatures *bitstream = 
> ^
> libwebp.cpp:42:17: warning: variable ‘picture’ set but not used 
> [-Wunused-but-set-variable]
>  WebPPicture picture;
>  ^~~
> libwebp.cpp:44:16: warning: variable ‘config2’ set but not used 
> [-Wunused-but-set-variable]
>  WebPConfig config2;
> ^~~
> libwebp.cpp:47:18: warning: unused variable ‘demuxer’ [-Wunused-variable]
>  WebPDemuxer *demuxer = WebPDemux();
>   ^~~
> libwebp.cpp:48:18: warning: variable ‘iter’ set but not used 
> [-Wunused-but-set-variable]
>  WebPIterator iter;
>   ^~~~
> ---
> 
> So, the test file is working.
> I am able to build it manually.
> 
> Why the Qt build system is complaining about this library installed on my 
> system please?
> 
> Thank you.
> Best regards.
> ___
> 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


Re: [Development] CI infra broken

2018-01-31 Thread Michal Klocek
Hi

Please let us know if we can use ci already or not.

I also get:

"Timeout while creating source archives. Probably Coin issue, you can
re-stage and ping Coin admin."

Br

Michal

On 01/31/2018 05:42 AM, Tony Sarajärvi wrote:
> Hi
> 
> Now that seems to be a bug in Coin. It doesn't even begin to retry it. The 
> log is still from last night the first time I launched it. Sigh... I'll try 
> to force it somehow.
> 
> -Tony
> 
> -Original Message-
> From: Allan Jensen 
> Sent: keskiviikko 31. tammikuuta 2018 0.17
> To: Tony Sarajärvi 
> Cc: development@qt-project.org
> Subject: Re: CI infra broken
> 
> On Dienstag, 30. Januar 2018 23:13:08 CET Tony Sarajärvi wrote:
>> Hi
>>  
>> We worked around the bug, but it took hours to move all data involved here.
>> The system is back up and running now. 
> 
> It appears to still be broken just like it was before everything went 
> offline, half the CIs can't provision and fail with messages like:
> 
> E: Failed to fetch http://security.ubuntu.com/ubuntu/pool/main/p/python3.5/
> libpython3.5_3.5.2-2ubuntu0~16.04.4_amd64.deb  Could not connect to
> proxy.intra.qt.io:3128 (10.215.0.6). - connect (113: No route to host)
> 
> 
> 
> 'Allan
> 
> 
> ___
> 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


Re: [Development] 32bit linux build of qt5.10.0 w/ webengine

2017-12-18 Thread Michal Klocek
Hi

It looks like the build can not proceed because of lack of working
ninja. Qt configure detects system ninja, and in case it does not work
builds internal one. In case for some reason this failed you can
still force the build to use internal ninja with configure option:

-no-feature-webengine-system-ninja

Br

Michal

On 12/18/2017 06:53 PM, Toan Pham wrote:
> Thiago,
> 
> 
> I am running two parallel builds at the moment, and they are:
> 
> 
> 1.  32 bit LXC container (ubuntu 16.04 32bit)
>  The build is still compiling chronium web-engine for the last an hr
> and a half.  So far, I haven't had much problem w/ this one except that
> I had to comment out a few lines in qtwebengine/qtwebengine.pro
>  to get the build started.
> 
> 
> 
> 2.  32bit inside T2SDE sandbox (ref. http://t2sde.org)
> 
>   This build stopped here:
> 
> make[4]: Entering directory
> `/TOOLCHAIN/loop/target/nicebox/sandbox/qt-everywhere-src-5.10.0/qtwebengine/src/buildtools'
> make[4]: Nothing to be done for `first'.
> make[4]: Leaving directory
> `/TOOLCHAIN/loop/target/nicebox/sandbox/qt-everywhere-src-5.10.0/qtwebengine/src/buildtools'
> ( test -e Makefile.configure_target ||
> /TOOLCHAIN/loop/target/nicebox/sandbox/qt-everywhere-src-5.10.0/qtbase/bin/qmake
> -o Makefile.configure_target
> /TOOLCHAIN/loop/target/nicebox/sandbox/qt-everywhere-src-5.10.0/qtwebengine/src/buildtools/configure_target.pro
>  ) && make -f Makefile.configure_target
> make[4]: Entering directory
> `/TOOLCHAIN/loop/target/nicebox/sandbox/qt-everywhere-src-5.10.0/qtwebengine/src/buildtools'
> make[4]: Nothing to be done for `first'.
> make[4]: Leaving directory
> `/TOOLCHAIN/loop/target/nicebox/sandbox/qt-everywhere-src-5.10.0/qtwebengine/src/buildtools'
> ( test -e Makefile.gn ||
> /TOOLCHAIN/loop/target/nicebox/sandbox/qt-everywhere-src-5.10.0/qtbase/bin/qmake
> -o Makefile.gn
> /TOOLCHAIN/loop/target/nicebox/sandbox/qt-everywhere-src-5.10.0/qtwebengine/src/buildtools/gn.pro
>  ) && make -f Makefile.gn
> Building gn manually in a temporary directory for bootstrapping...
> Traceback (most recent call last):
>   File
> "/TOOLCHAIN/loop/target/nicebox/sandbox/qt-everywhere-src-5.10.0/qtwebengine/src/3rdparty/chromium/tools/gn/bootstrap/bootstrap.py",
> line 855, in 
> sys.exit(main(sys.argv[1:]))
>   File
> "/TOOLCHAIN/loop/target/nicebox/sandbox/qt-everywhere-src-5.10.0/qtwebengine/src/3rdparty/chromium/tools/gn/bootstrap/bootstrap.py",
> line 127, in main
> return run_build(build_dir, options)
>   File
> "/TOOLCHAIN/loop/target/nicebox/sandbox/qt-everywhere-src-5.10.0/qtwebengine/src/3rdparty/chromium/tools/gn/bootstrap/bootstrap.py",
> line 74, in run_build
> build_gn_with_ninja_manually(tempdir, options)
>   File
> "/TOOLCHAIN/loop/target/nicebox/sandbox/qt-everywhere-src-5.10.0/qtwebengine/src/3rdparty/chromium/tools/gn/bootstrap/bootstrap.py",
> line 220, in build_gn_with_ninja_manually
> check_call(cmd)
>   File
> "/TOOLCHAIN/loop/target/nicebox/sandbox/qt-everywhere-src-5.10.0/qtwebengine/src/3rdparty/chromium/tools/gn/bootstrap/bootstrap.py",
> line 45, in check_call
> subprocess.check_call(cmd, cwd=GN_ROOT, **kwargs)
>   File "/usr/lib/python2.7/subprocess.py", line 535, in check_call
> retcode = call(*popenargs, **kwargs)
>   File "/usr/lib/python2.7/subprocess.py", line 522, in call
> return Popen(*popenargs, **kwargs).wait()
>   File "/usr/lib/python2.7/subprocess.py", line 709, in __init__
> errread, errwrite)
>   File "/usr/lib/python2.7/subprocess.py", line 1326, in _execute_child
> raise child_exception
> OSError: [Errno 2] No such file or directory
> Project ERROR: GN build error!
> make[3]: *** [sub-gn-pro-make_first] Error 3
> make[3]: Leaving directory
> `/TOOLCHAIN/loop/target/nicebox/sandbox/qt-everywhere-src-5.10.0/qtwebengine/src/buildtools'
> make[2]: *** [sub-buildtools-make_first] Error 2
> make[2]: Leaving directory
> `/TOOLCHAIN/loop/target/nicebox/sandbox/qt-everywhere-src-5.10.0/qtwebengine/src'
> make[1]: *** [sub-src-make_first] Error 2
> make[1]: Leaving directory
> `/TOOLCHAIN/loop/target/nicebox/sandbox/qt-everywhere-src-5.10.0/qtwebengine'
> 
> 
> 
> Please let me know if you know what went wrong w/ the second build. 
> 
> 
> thanks,
> 
> TP
> 
> 
> On Mon, Dec 18, 2017 at 11:39 AM, Thiago Macieira
> > wrote:
> 
> On Monday, 18 December 2017 07:46:24 PST Toan Pham wrote:
> > Hi,
> >
> > I am having multiple problems w/ building qt5.10 w/ webengine support 
> for
> > linux 32bit.  Before I proceed further down that road, I would like to 
> know
> > if there's a pre-built version of qt5.10.0 w/ webengine for linux 32bit
> > somewhere?
> 
> There isn't. Linux 32-bit is uncommon enough these days that it's
> not worth
> spending CPU time building for it.
> 
> Please report your build issues. I did check a few 

Re: [Development] Nominating Viktor Engelmann for Approver Status

2017-07-20 Thread Michal Klocek
+1

Br

Michal

On 07/13/2017 05:07 PM, Allan Sandfeld Jensen wrote:
> On Dienstag, 11. Juli 2017 13:25:21 CEST Simon Hausmann wrote:
>> Hi,
>>
>>
>> I'd like to propose Viktor for approver status. Since August last year he's
>> been contributing to QtWebEngine full-time. Based on my experience talking
>> to him and working with him, I trust him to review changes thoroughly and
>> approve or reject changes responsively.
>>
> +1 :)
> 
> ' Allan
> 
> ___
> 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


Re: [Development] QTWebEngine Compilation failure

2017-07-20 Thread Michal Klocek
Hi

What is the output of "cl -Bv" ?

Br

Michal

On 07/20/2017 11:56 AM, Sudhir Sharma wrote:
> Hi,
> 
>  
> 
> I am not able to compile QtWebEngine.
> 
> Upon compilation of entite source I notice the QtWebEngine has not been
> builit.
> 
>  
> 
> If I try to compile it separately, I get following error.
> 
>  
> 
> C:\Qt\Qt5\5.9.1\Src\qtwebengine>qmake
> 
> Running configure tests
> 
> Checking for alsa... no
> 
> Checking for khr... no
> 
> Checking for libvpx... no
> 
> Checking for snappy... no
> 
> Checking for srtp... no
> 
> Checking for winversion... no
> 
> Configurable features:
> 
>   Proprietary codecs (H264, MP3) . Not enabled (Default,
> enable with -proprietary-codecs)
> 
>   Geolocation  Enabled
> 
>  
> 
> Needs VS 2015 Update 3 with Cumulative Servicing Release or higher
> 
> QtWebEngine will not be built.
> 
>  
> 
> Looking at bugreports.qt, it appears to have been resolved. But no idea
> about the solution.
> 
>  
> 
> My Environment Details:
> 
>  
> 
> Qt 5.9.1
> 
> Platform: windows 2012 server
> 
> Microsoft Visual Studio Community 2015
> 
> Version 14.0.25431.01 Update 3
> 
>  
> 
>  
> 
> Regards,
> 
> Sudhir
> 
> 
> 
> 
> http://www.mindtree.com/email/disclaimer.html
> 
> 
> ___
> 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


Re: [Development] abi breakage for qtwebengine libraries in 5.9

2017-05-08 Thread Michal Klocek
Thanks Thiago for the hint, I only tried to make symbols as weak alias, but 
that did not do the job. Now when you mentioned about default version I checked 
and symbols indeed were exported as 'default', I will try later today to see if 
this can be fixed as you suggested.


Br


Michal


From: Development  on 
behalf of Thiago Macieira 
Sent: Monday, May 8, 2017 9:03 AM
To: development@qt-project.org
Subject: Re: [Development] abi breakage for qtwebengine libraries in 5.9

On Sunday, 7 May 2017 23:38:33 PDT Lars Knoll wrote:
> Hi,
>
> why can't we just keep these symbols around without exporting them through a
> header file and make them simply forward to the global new/delete
> operators? If we don't export them in a header at least newly compiled code
> would stop using them, and old code would continue working like that.

The problem is not related to compilation and thus headers.

The problem is that the symbols *exist*. Since they exist, the linker will
link to them.

Now, the problem is that they exist under an ELF version, so when we remove
them, the dynamic linker will no longer find the plain unversioned ones in
libstdc++.so.6. I *think* it's possible to provide them under as special type
of version that allows the previous uses to be found, but no longer allow new
linking to them (non-default version). But since I don't have qtwebengine
around, I need information:

Does _Znwm appear with one or two @ ?

--
Thiago Macieira - thiago.macieira (AT) intel.com
  Software Architect - Intel Open Source Technology Center

___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development
Development Info Page - 
Qt
lists.qt-project.org
To see the collection of prior postings to the list, visit the Development 
Archives. Using Development: To post a message to all the list members ...


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


[Development] abi breakage for qtwebengine libraries in 5.9

2017-05-05 Thread Michal Klocek

Hi

With 5.8.0 we released web engine libs which export operator new , new[] 
, delete, delete[] globally, unfortunately the issue was not spotted in 
time.


https://bugreports.qt.io/browse/QTBUG-60565

With 5.9.0 we plan to correct the issue, unfortunately everything which
was compiled against qtwebengine 5.8.0 will be broken when used with 
5.9.0 libraries due to missing symbols and needs to be recompiled.


Br

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


Re: [Development] Nominating Paolo Angelelli for Approver status

2016-08-26 Thread Michal Klocek

+1

On 08/26/2016 01:35 PM, Eirik Aavitsland wrote:


+1

- Eirik Aa.

On 26. aug. 2016 11:34, Laszlo Agocs wrote:


+1. Besides fixes he's been doing quite some new features as well. Keep
them coming.


Cheers,

Laszlo




*From:* Development
 on behalf of
Eskil Abrahamsen Blomfeldt 
*Sent:* Friday, August 26, 2016 11:31 AM
*To:* development@qt-project.org
*Subject:* Re: [Development] Nominating Paolo Angelelli for Approver
status



Den 26.08.2016 10:17, skrev Alexander Blasche:

Hi,

I'd like to nominate Paolo Angelelli for Approver status. He joined
The Qt Company at the end of 2015, and has been working full time on
Qt since. Paolo has been actively involved fixing and improving
QtPositioning and QtLocation.


+1

Paolo has been and is doing great work on Qt Location :)

--
Eskil Abrahamsen Blomfeldt
Senior Manager, R

The Qt Company
Sandakerveien 116
0484 Oslo, Norway
eskil.abrahamsen-blomfe...@qt.io
http://qt.io

___
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 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


Re: [Development] Programs crashing left and right in the CI

2016-07-28 Thread Michal Klocek

Hi

It seems to happen in different modules (here qttools and qtlocation)
and in different branches (here dev and 5.6), but on mac/clang and 
during moc compilation.



http://testresults.qt.io/logs/qt/qttools/19be2439dce662a3c2cfee15bce24f8b399c7a45/OSXOSX_10_09x86_64OSXOSX_10_09x86_64Clangqtci-osx-10.9-x86_64Release_NoFramework/f7cbe1e5f2b918c36be693265f81e0e4da6e5658/buildlog.txt.gz

http://testresults.qt.io/coin/logview/qt/qtlocation/4215524eedd8aca38b749b3baba5301d7b5f8745/OSXOSX_10_10x86_64OSXOSX_10_10x86_64Clangqtci-osx-10.10-x86_64DebugAndRelease_Release/26d001a8dcaf69e4e44fec119fe4c103605013df/buildlog.txt.gz

Br

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


Re: [Development] Nominating Alexandru Croitor for Approver status

2016-05-11 Thread Michal Klocek


+1

cheers

Mike
On 05/11/2016 01:14 PM, Michael Brüning wrote:

Hi all,

I would like to nominate Alexandru Croitor for Approver status. 
Alexandru joined The Qt Company about 6 months ago and has been 
working full time on Qt since then and especially on the Qt WebEngine 
module.


Here is his Gerrit dashboard:
https://codereview.qt-project.org/#/q/owner:"Alexandru Croitor 
"status:merged,n,z


And a list of his reviews:
https://codereview.qt-project.org/#/q/reviewer:"Alexandru Croitor 
",n,z


Cheers,
Michael
___
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


Re: [Development] Approver status for Michal Klocek

2016-03-01 Thread Michal Klocek
Hi,

Thanks a lot !


Michal

On 1 March 2016 at 09:16, Blasche Alexander
<alexander.blas...@theqtcompany.com> wrote:
> Approver rights have been granted. Congratulations to Michal.
>
> --
>
> Alex
>
> 
> From: Blasche Alexander
> Sent: Monday, February 8, 2016 15:18
> To: development@qt-project.org
> Subject: Approver status for Michal Klocek
>
> Hello,
>
> I would like to nominate Michal Klocek for Approver status in the Qt Project. 
> Throughout the last year he has been working on QtLocation and QtWebEngine:
>
> https://codereview.qt-project.org/#/q/owner:michal.klocek,n,z
>
> --
> Alex
> ___
> 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