Re: [Interest] Qt6 CMake Windows VS Debug Build Issues

2020-06-29 Thread Oliver Niebuhr 
Am 30/06/2020 um 06:34 schrieb Thiago Macieira:
> On Monday, 29 June 2020 20:18:16 PDT Oliver Niebuhr wrote:
>> clangTooling.lib(Tooling.cpp.obj) : error LNK2038: mismatch detected for
>> 'RuntimeLibrary': value 'MD_DynamicRelease' doesn't match value
>> 'MDd_DynamicDebug' in numerus.cpp.obj
> 
> Is there a clangToolingd.lib, a debug-build equivalent of clangTooling.lib?
> 
No. This is a pure Release Build. But that was never a Problem with Qt
5.15 and QMake (at least not for me). I will do more testing with Qt
5.15 and see if everything else is broken.



signature.asc
Description: OpenPGP digital signature
___
Interest mailing list
Interest@qt-project.org
https://lists.qt-project.org/listinfo/interest

Re: [Interest] Qt6 CMake Windows VS Debug Build Issues

2020-06-29 Thread Thiago Macieira 
On Monday, 29 June 2020 20:18:16 PDT Oliver Niebuhr wrote:
> clangTooling.lib(Tooling.cpp.obj) : error LNK2038: mismatch detected for
> 'RuntimeLibrary': value 'MD_DynamicRelease' doesn't match value
> 'MDd_DynamicDebug' in numerus.cpp.obj

Is there a clangToolingd.lib, a debug-build equivalent of clangTooling.lib?

-- 
Thiago Macieira - thiago.macieira (AT) intel.com
  Software Architect - Intel System Software Products



___
Interest mailing list
Interest@qt-project.org
https://lists.qt-project.org/listinfo/interest

Re: [Interest] Qt6 CMake Windows VS Debug Build Issues

2020-06-29 Thread Oliver Niebuhr 
Quick answer to Issue Number 1: I had to shorten the Out-Of-Source
Directory Name a little. Need to test multiple Variants - I just
reorganized the Naming Scheme and would hate redo everything again :(
Interestingly enough: The same Name / Directory Length works with QMAKE
and JOM (Qt 5.15 and Qt 6).

Am 30/06/2020 um 05:18 schrieb Oliver Niebuhr:
> Hello List.
> 
> I keep running into some Issues when trying to build a Debug Build with
> * Clang 10.0.1, build from Git, with VS 2019, Release build
> * CMake 3.17.3
> * Ninja 1.10
> * VS 2019 16.6.2
> * Qt 6 Dev Branch: latest Git
> 
> Issue Number 1 is a too long Input Line. No problem with Release builds
> though.
> "[1/1547] Automatic QML type registration for target
> qmlfolderlistmodelplugin
> FAILED:
> qtdeclarative/src/imports/folderlistmodel/qmlfolderlistmodelplugin_qmltyperegistrations.cpp
> 
> cmd.exe /C "cd /D
> C:\Dev\QtSrcx86DevMSVC\qtdeclarative\src\imports\folderlistmodel && set
> "PATH=C:\Dev\QtSrcx86DevMSVC\qtdeclarative\bin;C:\Dev\Qtx86DevDebugMSVC\bin;%PATH%"
> && C:\Dev\QtSrcx86DevMSVC\qtbase\bin\qmltyperegistrar.exe
> --generate-qmltypes=C:/Dev/QtSrcx86DevMSVC/qtdeclarative/src/imports/folderlistmodel/plugins.qmltypes
> --import-name=Qt.labs.folderlistmodel --major-version=6
> --minor-version=0
> @C:/Dev/QtSrcx86DevMSVC/qtdeclarative/src/imports/folderlistmodel/qmltypes/foreign_types.txt
> -o
> C:/Dev/QtSrcx86DevMSVC/qtdeclarative/src/imports/folderlistmodel/qmlfolderlistmodelplugin_qmltyperegistrations.cpp
> C:/Dev/QtSrcx86DevMSVC/qtdeclarative/src/imports/folderlistmodel/meta_types/qt6qmlfolderlistmodelplugin_debug_metatypes.json"
> The input line is too long."
> 
> Issue Number 2 is a "mismatch detected for '_ITERATOR_DEBUG_LEVEL'" with
> "[4/1547] Linking CXX executable qtbase\bin\lupdate.exe
> FAILED: qtbase/bin/lupdate.exe
> cmd.exe /C "cd . && C:\Dev\CMake\bin\cmake.exe -E vs_link_exe
> --intdir=qttools\src\linguist\lupdate\CMakeFiles\lupdate.dir
> --rc=C:\PROGRA~2\WI3CF2~1\10\bin\100190~1.0\x64\rc.exe
> --mt=C:\PROGRA~2\WI3CF2~1\10\bin\100190~1.0\x64\mt.exe --manifests  --
> C:\PROGRA~2\MICROS~2\2019\COMMUN~1\VC\Tools\MSVC\1426~1.288\bin\Hostx64\x86\link.exe
> /nologo @CMakeFiles\lupdate.rsp  /out:qtbase\bin\lupdate.exe
> /implib:qttools\src\linguist\lupdate\lupdate.lib
> /pdb:qtbase\bin\lupdate.pdb /version:0.0  /machine:X86 /DYNAMICBASE
> /SUBSYSTEM:CONSOLE,10.0 /DEBUG:FASTLINK /GUARD:CF /INCREMENTAL /NXCOMPAT
> /subsystem:console   -DYNAMICBASE -NXCOMPAT  && cd ."
> LINK Pass 1: command
> "C:\PROGRA~2\MICROS~2\2019\COMMUN~1\VC\Tools\MSVC\1426~1.288\bin\Hostx64\x86\link.exe
> /nologo @CMakeFiles\lupdate.rsp /out:qtbase\bin\lupdate.exe
> /implib:qttools\src\linguist\lupdate\lupdate.lib
> /pdb:qtbase\bin\lupdate.pdb /version:0.0 /machine:X86 /DYNAMICBASE
> /SUBSYSTEM:CONSOLE,10.0 /DEBUG:FASTLINK /GUARD:CF /INCREMENTAL /NXCOMPAT
> /subsystem:console -DYNAMICBASE -NXCOMPAT /MANIFEST
> /MANIFESTFILE:qttools\src\linguist\lupdate\CMakeFiles\lupdate.dir/intermediate.manifest
> qttools\src\linguist\lupdate\CMakeFiles\lupdate.dir/manifest.res" failed
> (exit code 1319) with the following output:
> clangTooling.lib(Tooling.cpp.obj) : error LNK2038: mismatch detected for
> '_ITERATOR_DEBUG_LEVEL': value '0' doesn't match value '2' in
> numerus.cpp.obj
> clangTooling.lib(Tooling.cpp.obj) : error LNK2038: mismatch detected for
> 'RuntimeLibrary': value 'MD_DynamicRelease' doesn't match value
> 'MDd_DynamicDebug' in numerus.cpp.obj
> clangTooling.lib(CommonOptionsParser.cpp.obj) : error LNK2038: mismatch
> detected for '_ITERATOR_DEBUG_LEVEL': value '0' doesn't match value '2'
> in numerus.cpp.obj
> clangTooling.lib(CommonOptionsParser.cpp.obj) : error LNK2038: mismatch
> detected for 'RuntimeLibrary': value 'MD_DynamicRelease' doesn't match
> value 'MDd_DynamicDebug' in numerus.cpp.obj
> clangTooling.lib(ArgumentsAdjusters.cpp.obj) : error LNK2038: mismatch
> detected for '_ITERATOR_DEBUG_LEVEL': value '0' doesn't match value '2'
> in numerus.cpp.obj
> clangTooling.lib(ArgumentsAdjusters.cpp.obj) : error LNK2038: mismatch
> detected for 'RuntimeLibrary': value 'MD_DynamicRelease' doesn't match
> value 'MDd_DynamicDebug' in numerus.cpp.obj
> [etc. etc. etc.]"
> 
> Yes, I have tested removing the additional Compiler Flags like /Qspectre
> etc. - those are not the Problem. And please ignore the Numbers which
> counting the build order: I had to restart Ninja to get the Error
> Messages - Windows CMD Shell Output is very limited. No matter how high
> you set the Buffer Number.
> 
> I am fully aware that the CMake Port is not finished and has a lot of
> Issues (having the Qt6 Bugreports Site pinned in the Browser). Still:
> Should I create a BR or wait for some Changes to Merge?
> 
> Thanks!
> Olli
> 
> 
> ___
> Interest mailing list
> Interest@qt-project.org
> https://lists.qt-project.org/listinfo/interest
> 



signature.asc
Description: OpenPGP digital signature

[Interest] Qt6 CMake Windows VS Debug Build Issues

2020-06-29 Thread Oliver Niebuhr 
Hello List.

I keep running into some Issues when trying to build a Debug Build with
* Clang 10.0.1, build from Git, with VS 2019, Release build
* CMake 3.17.3
* Ninja 1.10
* VS 2019 16.6.2
* Qt 6 Dev Branch: latest Git

Issue Number 1 is a too long Input Line. No problem with Release builds
though.
"[1/1547] Automatic QML type registration for target
qmlfolderlistmodelplugin
FAILED:
qtdeclarative/src/imports/folderlistmodel/qmlfolderlistmodelplugin_qmltyperegistrations.cpp

cmd.exe /C "cd /D
C:\Dev\QtSrcx86DevMSVC\qtdeclarative\src\imports\folderlistmodel && set
"PATH=C:\Dev\QtSrcx86DevMSVC\qtdeclarative\bin;C:\Dev\Qtx86DevDebugMSVC\bin;%PATH%"
&& C:\Dev\QtSrcx86DevMSVC\qtbase\bin\qmltyperegistrar.exe
--generate-qmltypes=C:/Dev/QtSrcx86DevMSVC/qtdeclarative/src/imports/folderlistmodel/plugins.qmltypes
--import-name=Qt.labs.folderlistmodel --major-version=6
--minor-version=0
@C:/Dev/QtSrcx86DevMSVC/qtdeclarative/src/imports/folderlistmodel/qmltypes/foreign_types.txt
-o
C:/Dev/QtSrcx86DevMSVC/qtdeclarative/src/imports/folderlistmodel/qmlfolderlistmodelplugin_qmltyperegistrations.cpp
C:/Dev/QtSrcx86DevMSVC/qtdeclarative/src/imports/folderlistmodel/meta_types/qt6qmlfolderlistmodelplugin_debug_metatypes.json"
The input line is too long."

Issue Number 2 is a "mismatch detected for '_ITERATOR_DEBUG_LEVEL'" with
"[4/1547] Linking CXX executable qtbase\bin\lupdate.exe
FAILED: qtbase/bin/lupdate.exe
cmd.exe /C "cd . && C:\Dev\CMake\bin\cmake.exe -E vs_link_exe
--intdir=qttools\src\linguist\lupdate\CMakeFiles\lupdate.dir
--rc=C:\PROGRA~2\WI3CF2~1\10\bin\100190~1.0\x64\rc.exe
--mt=C:\PROGRA~2\WI3CF2~1\10\bin\100190~1.0\x64\mt.exe --manifests  --
C:\PROGRA~2\MICROS~2\2019\COMMUN~1\VC\Tools\MSVC\1426~1.288\bin\Hostx64\x86\link.exe
/nologo @CMakeFiles\lupdate.rsp  /out:qtbase\bin\lupdate.exe
/implib:qttools\src\linguist\lupdate\lupdate.lib
/pdb:qtbase\bin\lupdate.pdb /version:0.0  /machine:X86 /DYNAMICBASE
/SUBSYSTEM:CONSOLE,10.0 /DEBUG:FASTLINK /GUARD:CF /INCREMENTAL /NXCOMPAT
/subsystem:console   -DYNAMICBASE -NXCOMPAT  && cd ."
LINK Pass 1: command
"C:\PROGRA~2\MICROS~2\2019\COMMUN~1\VC\Tools\MSVC\1426~1.288\bin\Hostx64\x86\link.exe
/nologo @CMakeFiles\lupdate.rsp /out:qtbase\bin\lupdate.exe
/implib:qttools\src\linguist\lupdate\lupdate.lib
/pdb:qtbase\bin\lupdate.pdb /version:0.0 /machine:X86 /DYNAMICBASE
/SUBSYSTEM:CONSOLE,10.0 /DEBUG:FASTLINK /GUARD:CF /INCREMENTAL /NXCOMPAT
/subsystem:console -DYNAMICBASE -NXCOMPAT /MANIFEST
/MANIFESTFILE:qttools\src\linguist\lupdate\CMakeFiles\lupdate.dir/intermediate.manifest
qttools\src\linguist\lupdate\CMakeFiles\lupdate.dir/manifest.res" failed
(exit code 1319) with the following output:
clangTooling.lib(Tooling.cpp.obj) : error LNK2038: mismatch detected for
'_ITERATOR_DEBUG_LEVEL': value '0' doesn't match value '2' in
numerus.cpp.obj
clangTooling.lib(Tooling.cpp.obj) : error LNK2038: mismatch detected for
'RuntimeLibrary': value 'MD_DynamicRelease' doesn't match value
'MDd_DynamicDebug' in numerus.cpp.obj
clangTooling.lib(CommonOptionsParser.cpp.obj) : error LNK2038: mismatch
detected for '_ITERATOR_DEBUG_LEVEL': value '0' doesn't match value '2'
in numerus.cpp.obj
clangTooling.lib(CommonOptionsParser.cpp.obj) : error LNK2038: mismatch
detected for 'RuntimeLibrary': value 'MD_DynamicRelease' doesn't match
value 'MDd_DynamicDebug' in numerus.cpp.obj
clangTooling.lib(ArgumentsAdjusters.cpp.obj) : error LNK2038: mismatch
detected for '_ITERATOR_DEBUG_LEVEL': value '0' doesn't match value '2'
in numerus.cpp.obj
clangTooling.lib(ArgumentsAdjusters.cpp.obj) : error LNK2038: mismatch
detected for 'RuntimeLibrary': value 'MD_DynamicRelease' doesn't match
value 'MDd_DynamicDebug' in numerus.cpp.obj
[etc. etc. etc.]"

Yes, I have tested removing the additional Compiler Flags like /Qspectre
etc. - those are not the Problem. And please ignore the Numbers which
counting the build order: I had to restart Ninja to get the Error
Messages - Windows CMD Shell Output is very limited. No matter how high
you set the Buffer Number.

I am fully aware that the CMake Port is not finished and has a lot of
Issues (having the Qt6 Bugreports Site pinned in the Browser). Still:
Should I create a BR or wait for some Changes to Merge?

Thanks!
Olli



signature.asc
Description: OpenPGP digital signature
___
Interest mailing list
Interest@qt-project.org
https://lists.qt-project.org/listinfo/interest

Re: [Interest] Qt 6.0 and the future of QWebSockets module

2020-06-29 Thread Jason H 
+1 I've moved to QtWebSockets for all IP communication, and it's made everything so much easier, even easier thant he QtHttpServer, which is what I was using and is still being developed.

 

 

 

 
 

Sent: Saturday, June 27, 2020 at 4:01 PM
From: "Narolewski Jakub" 
To: "Lars Knoll" 
Cc: "interest@qt-project.org Interest" 
Subject: Re: [Interest] Qt 6.0 and the future of QWebSockets module





That's great to hear. Thank you :]

 

Jakub Narolewski


 



On Fri, 26 Jun 2020, 15:11 Lars Knoll,  wrote:




Hi,


 



The plan is to bring those modules back after Qt 6.0. This is mainly a prioritisation question right now, where the choice was to focus most development efforts on the Qt Essentials to make them as good as possible for Qt 6.



 



So I expect that we’ll have a fully supported web sockets module available for Qt 6 by the time 6.1 or latest 6.2 is being released.



 



Cheers,



Lars



 



On 26 Jun 2020, at 14:23, Narolewski Jakub  wrote:


 



Hello :]

Lurking yesterday on a dev mailing list I accidentally stumbled upon topic that mentioned this wiki site: https://wiki.qt.io/Checklist_for_Qt_6.0_inclusion
As I understand it, it is a listing of Qt modules and their their 'cmake porting progress' and I quote:

"Given the deadline for the Qt 6.0 release at the end of 2020, it is likely that not all Qt modules will be ready for the deadline set by the 6.0 release schedule."

Enter the QWebSocket module. As it currently stands QSW is in some kind of a development limbo.
On wiki: https://wiki.qt.io/Maintainers Kurt Pattyn is still listed as module's maintainer but I believe he is currently inactive in development.
On JIRA there is a task that specifies improvements for the module: https://bugreports.qt.io/browse/QTBUG-42749
But under connected ticket: https://bugreports.qt.io/browse/QTBUG-75638
There is ominous: "unify QtWebSocket with other networking classes (out of scope)"

Does this mean that QWS will be removed as an available module in Qt 6.0?
Will it be unsupported after Qt5.x releases?
If I use it currently, would it be wise to start using something different if I would like to later jump to the Qt 6.X releases?

Yours Truly 2095,
Jakub Narolewski


___
Interest mailing list
Interest@qt-project.org
https://lists.qt-project.org/listinfo/interest








 

___ Interest mailing list Interest@qt-project.org https://lists.qt-project.org/listinfo/interest




___
Interest mailing list
Interest@qt-project.org
https://lists.qt-project.org/listinfo/interest

Re: [Interest] Qt 5.x configure line prefix

2020-06-29 Thread Robert Heller 
At Mon, 29 Jun 2020 09:46:16 +0530 Ramakanth Kesireddy  
wrote:

> 
> 
> 
> Hi,
> 
> Can anyone let me know if it is recommended to use -prefix /usr or the
> default in the configure line where it gets installed in /usr/local/Qt5.x?

Unless you are building an O/S packaging system package (eg .deb or .rpm), you 
should *not* install locally build software with the /usr prefix.

> 
> As the font algorithm using font config checks the available fonts in
> /usr/lib/fonts, does it makes sense to configure Qt 5.x with prefix /usr?

No.  To use your locally built Qt 5.x, you will need to make sure 
/usr/local/ is known to your build environment (path, compiler, 
linker, etc.).  (Generally, this should normally be set up by default, but it 
can't hurt to check.)


> 
> Thanks and Regards,
> Ramakanth
> 
> MIME-Version: 1.0
> 
> ___
> Interest mailing list
> Interest@qt-project.org
> https://lists.qt-project.org/listinfo/interest
> 
>  
> 

-- 
Robert Heller -- 978-544-6933 Cell: 413-658-7953 GV: 978-633-5364
Deepwoods Software-- Custom Software Services
http://www.deepsoft.com/  -- Linux Administration Services
hel...@deepsoft.com   -- Webhosting Services

   
___
Interest mailing list
Interest@qt-project.org
https://lists.qt-project.org/listinfo/interest