Re: [Interest] How do you want to select exactly C++11 with GCC 6+?

[Elvis Stansvik]

Den 10 mars 2017 12:19 fm skrev "Thiago Macieira" :
>
> On quinta-feira, 9 de março de 2017 18:12:57 CET Sérgio Martins wrote:
> > On Thu, Mar 9, 2017 at 1:13 PM, Thiago Macieira
> > > 1) is there a need for qmake to provide a way to select *exactly*
C++11,
> > > not a later, available version?
> >
> > I wouldn't worry much about it, aren't C++11 and C++14 ABI compatible ?
>
> Yes.
>
> > If there's some implementation where this is an issue then qmake
> > should provide an obscure way to workaround and not through CONFIG.
>
> Right. I'm trying to figure out if I need to worry about this at all.
>
> In other words, for people who already have in their .pro files:
> CONFIG += c++11
>
> is it acceptable to enable C++14 instead?

To me it's acceptable, but my gut reaction is that it's a little magical to
get something newer.

How about CXX_VERSION, MIN_CXX_VERSION and MAX_CXX_VERSION, each taking the
arguments 98, 11, 14, 17, ...? Too many variables?

Could be done by adding CONFIG options min-c++N and max-c++N instead, for N
= 98, 11, 14, 17, ...

If <  and = are allowed in CONFIG keys, maybe e.g. >=c++11 is nicer. Or lt,
gt, le ge prefixes..

Elvis

>
> --
> Thiago Macieira - thiago.macieira (AT) intel.com
>   Software Architect - Intel Open Source Technology Center
>
> ___
> Interest mailing list
> Interest@qt-project.org
> http://lists.qt-project.org/mailman/listinfo/interest
___
Interest mailing list
Interest@qt-project.org
http://lists.qt-project.org/mailman/listinfo/interest

Re: [Interest] Support for Visual Studio 2017

[Tom Isaacson]

Visual Studio About screen shows .NET Framework Version 4.6.01586

I turned off Windows Defender but I now get a message saying "This extension is 
already installed to all applicable products". It's never completed the install 
and doesn't appear in VS2017. Turning it on doesn't make any difference.

I tried following the uninstall instructions here:
https://github.com/github/VisualStudio/issues/864
but I can't find a directory for the addin and C:\Program Files (x86)\Microsoft 
Visual 
Studio\2017\Professional\Common7\IDE\Extensions\extensions.configurationchanged 
is empty.

Tom Isaacson

-Original Message-
From: Interest [mailto:interest-bounces+tom.isaacson=navico@qt-project.org] 
On Behalf Of Henry Skoglund
Sent: Friday, 10 March 2017 11:56
To: interest@qt-project.org
Subject: Re: [Interest] Support for Visual Studio 2017

Hi, just guessing, but googling the error suggests: check that your .NET 
Framework has been updated to 4.6 and also turn off any antivirus program.

Rgrds Henry

On 2017-03-09 23:33, Tom Isaacson wrote:
> Unfortunately it fails for me:
>
> 10/03/2017 11:31:08 AM - Microsoft VSIX Installer
> 10/03/2017 11:31:08 AM - ---
> 10/03/2017 11:31:08 AM - vsixinstaller.exe version:
> 10/03/2017 11:31:08 AM - 15.0.26228.0 built by: D15REL
> 10/03/2017 11:31:08 AM - ---
> 10/03/2017 11:31:08 AM - Command line parameters:
> 10/03/2017 11:31:08 AM - C:\Program Files (x86)\Microsoft Visual 
> Studio\2017\Professional\Common7\IDE\VSIXInstaller.exe,C:\Users\Tom\Do
> wnloads\qt-vsaddin-msvc2017-2.1.1-beta (1).vsix
> 10/03/2017 11:31:08 AM - ---
> 10/03/2017 11:31:08 AM - Microsoft VSIX Installer
> 10/03/2017 11:31:08 AM - ---
> 10/03/2017 11:31:09 AM - Initializing Install...
> 10/03/2017 11:31:09 AM - Extension Details...
> 10/03/2017 11:31:09 AM -  Identifier : 
> QtVsTools.13121978-cd02-4fd0-89bd-e36f85abe16a
> 10/03/2017 11:31:09 AM -  Name   : Qt Visual Studio Tools
> 10/03/2017 11:31:09 AM -  Author : The Qt Company Ltd.
> 10/03/2017 11:31:09 AM -  Version: 2.1.1
> 10/03/2017 11:31:09 AM -  Description: The Qt Visual Studio Tools 
> allow developers to use the standard development environment without having 
> to worry about any Qt-related build steps or tools.
> 10/03/2017 11:31:09 AM -  Locale : en-US
> 10/03/2017 11:31:09 AM -  MoreInfoURL: http://www.qt.io/
> 10/03/2017 11:31:09 AM -  InstalledByMSI : False
> 10/03/2017 11:31:09 AM -  SupportedFrameworkVersionRange : [4.6,)
> 10/03/2017 11:31:09 AM -
> 10/03/2017 11:31:09 AM -  SignatureState : Unsigned
> 10/03/2017 11:31:09 AM -  Supported Products :
> 10/03/2017 11:31:09 AM -  Microsoft.VisualStudio.Pro
> 10/03/2017 11:31:09 AM -  Version : [15.0]
> 10/03/2017 11:31:09 AM -  Microsoft.VisualStudio.Premium
> 10/03/2017 11:31:09 AM -  Version : [15.0]
> 10/03/2017 11:31:09 AM -  Microsoft.VisualStudio.Ultimate
> 10/03/2017 11:31:09 AM -  Version : [15.0]
> 10/03/2017 11:31:09 AM -  Microsoft.VisualStudio.Community
> 10/03/2017 11:31:09 AM -  Version : [15.0]
> 10/03/2017 11:31:09 AM -
> 10/03/2017 11:31:09 AM -  References :
> 10/03/2017 11:31:09 AM -  Prerequisites  :
> 10/03/2017 11:31:09 AM -  
> ---
> 10/03/2017 11:31:09 AM -  Identifier   : 
> Microsoft.VisualStudio.Component.CoreEditor
> 10/03/2017 11:31:09 AM -  Name : Visual Studio core editor
> 10/03/2017 11:31:09 AM -  Version  : [15.0.26208.0,16.0)
> 10/03/2017 11:31:09 AM -
> 10/03/2017 11:31:09 AM -  
> ---
> 10/03/2017 11:31:09 AM -  Identifier   : 
> Microsoft.VisualStudio.Component.VC.CoreIde
> 10/03/2017 11:31:09 AM -  Name : Visual Studio C++ core 
> features
> 10/03/2017 11:31:09 AM -  Version  : [15.0.26208.0,16.0)
> 10/03/2017 11:31:09 AM -
> 10/03/2017 11:31:09 AM - Signature Details...
> 10/03/2017 11:31:09 AM -  Extension is not signed.
> 10/03/2017 11:31:09 AM -
> 10/03/2017 11:31:09 AM - Searching for applicable products...
> 10/03/2017 11:31:09 AM - Found installed product - Microsoft Visual 
> Studio Professional 2013
> 10/03/2017 11:31:09 AM - Found installed product - Microsoft Visual 
> Studio 2013 Shell (Integrated)
> 10/03/2017 11:31:09 AM - Found installed product - Microsoft Visual 
> Studio Professional 2015
> 10/03/2017 11:31:09 AM - Found installed product - Microsoft Visual 
> Studio Community 2015
> 10/03/2017 11:31:09 AM - Found installed product - Microsoft Visual 
> Studio 2015 Shell 

[Interest] signed DLLs/Frameworks for Qt

[Hamish Moffatt]

I notice that the official distributions for Qt commercial contain 
unsigned DLLs and frameworks. Does the Qt Company have any plans to sign 
these in a future release?


Mac App Store requires all frameworks to be signed, although I don't 
think macOS is enforcing it for frameworks in non-store applications 
yet. Windows is not enforcing anything as far as I can tell.



thanks,

Hamish

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

Re: [Interest] generated header file not being processed by moc

[Glen Mabey]

Is this something that could be handled better by qbs?

Glen

> On Feb 14, 2017, at 3:59 PM, Glen Mabey  wrote:
> 
> 
> Well, I have the strangest of solutions that isn’t clean, pretty, or even 
> explainable (by me).
> 
> Consider these extra rules (linux only) so the complete .pro file looks like 
> this:
> 
> 
> TEMPLATE = app
> 
> SOURCES += main.cpp
> 
> OBJ_SOURCE = dummy_input_file.txt
> 
> OBJ_GENERATOR.CONFIG   += no_link target_predeps
> OBJ_GENERATOR.output   = ${QMAKE_FILE_BASE}_QObject.h
> OBJ_GENERATOR.commands = ./generate_a_file.py ${QMAKE_FILE_OUT}
> OBJ_GENERATOR.input = OBJ_SOURCE
> OBJ_GENERATOR.variable_out = HEADERS
> QMAKE_EXTRA_COMPILERS += OBJ_GENERATOR
> 
> PRO_FILE_TOUCHER.CONFIG   += no_link target_predeps
> PRO_FILE_TOUCHER.output   = .lmp_${QMAKE_FILE_BASE}_generated
> PRO_FILE_TOUCHER.commands = touch $$_PRO_FILE_ ${QMAKE_FILE_OUT} && $(MAKE) 
> && exit 1
> PRO_FILE_TOUCHER.input= OBJ_SOURCE
> QMAKE_EXTRA_COMPILERS += PRO_FILE_TOUCHER
> 
> OBJECTS_DIR=.o
> MOC_DIR=.moc
> 
> 
> That is, the first time that make runs, it touches the .pro file as well as 
> .lmp_dummy_input_file_generated, then re-runs make.
> 
> Here’s what I don’t understand: when those commands are followed by “exit 1” 
> then for some reason the “new” version of the Makefile gets used in the rest 
> of the build commands, whereas if “exit 0” is used, then in the Makefile, 
> OBJECTS does not contain .o/moc_dummy_input_file_QObject.o and linking fails …
> 
> So, this all seems extremely hackish, and make still returns with a non-zero 
> value (like it does when linking fails) but now in this case it actually has 
> succeeded … blech.
> 
> Glen
> 
>> On Feb 13, 2017, at 12:04 PM, Glen Mabey  wrote:
>> 
>> Hello,
>> 
>> I think I’ve got the exact problem described here back in 2012: 
>> https://forum.qt.io/topic/21964/qmake-custom-compilers-how-to-process-generated-header-files-with-moc
>> 
>> That is, my generated header file includes a class that inherits from 
>> QObject and needs to be moc'ed.
>> 
>> However, these lines are not sufficient to make that happen the first time 
>> the project is built:
>> 
>> OBJ_SOURCE = dummy_input_file.txt
>> 
>> OBJ_GENERATOR.CONFIG   += no_link target_predeps
>> OBJ_GENERATOR.output   = ${QMAKE_FILE_BASE}_QObject.h
>> OBJ_GENERATOR.commands = ./generate_a_file.py ${QMAKE_FILE_OUT}
>> OBJ_GENERATOR.input = OBJ_SOURCE
>> OBJ_GENERATOR.variable_out = HEADERS
>> QMAKE_EXTRA_COMPILERS += OBJ_GENERATOR
>> 
>> 
>> That is, the project fails to link due to undefined references.
>> 
>> If I rerun qmake and build again, though, everything works out fine.
>> 
>> Any suggestions?
>> Glen
>> ___
>> Interest mailing list
>> Interest@qt-project.org
>> http://lists.qt-project.org/mailman/listinfo/interest
> 
> ___
> Interest mailing list
> Interest@qt-project.org
> http://lists.qt-project.org/mailman/listinfo/interest

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

Re: [Interest] How do you want to select exactly C++11 with GCC 6+?

[Thiago Macieira]

On quinta-feira, 9 de março de 2017 18:12:57 CET Sérgio Martins wrote:
> On Thu, Mar 9, 2017 at 1:13 PM, Thiago Macieira
> > 1) is there a need for qmake to provide a way to select *exactly* C++11,
> > not a later, available version?
> 
> I wouldn't worry much about it, aren't C++11 and C++14 ABI compatible ?

Yes.

> If there's some implementation where this is an issue then qmake
> should provide an obscure way to workaround and not through CONFIG.

Right. I'm trying to figure out if I need to worry about this at all.

In other words, for people who already have in their .pro files:
CONFIG += c++11

is it acceptable to enable C++14 instead?

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

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

Re: [Interest] Support for Visual Studio 2017

[Henry Skoglund]

Hi, just guessing, but googling the error suggests: check that your .NET 
Framework has been updated to 4.6 and also turn off any antivirus program.


Rgrds Henry

On 2017-03-09 23:33, Tom Isaacson wrote:

Unfortunately it fails for me:

10/03/2017 11:31:08 AM - Microsoft VSIX Installer
10/03/2017 11:31:08 AM - ---
10/03/2017 11:31:08 AM - vsixinstaller.exe version:
10/03/2017 11:31:08 AM - 15.0.26228.0 built by: D15REL
10/03/2017 11:31:08 AM - ---
10/03/2017 11:31:08 AM - Command line parameters:
10/03/2017 11:31:08 AM - C:\Program Files (x86)\Microsoft Visual 
Studio\2017\Professional\Common7\IDE\VSIXInstaller.exe,C:\Users\Tom\Downloads\qt-vsaddin-msvc2017-2.1.1-beta
 (1).vsix
10/03/2017 11:31:08 AM - ---
10/03/2017 11:31:08 AM - Microsoft VSIX Installer
10/03/2017 11:31:08 AM - ---
10/03/2017 11:31:09 AM - Initializing Install...
10/03/2017 11:31:09 AM - Extension Details...
10/03/2017 11:31:09 AM -Identifier : 
QtVsTools.13121978-cd02-4fd0-89bd-e36f85abe16a
10/03/2017 11:31:09 AM -Name   : Qt Visual Studio Tools
10/03/2017 11:31:09 AM -Author : The Qt Company Ltd.
10/03/2017 11:31:09 AM -Version: 2.1.1
10/03/2017 11:31:09 AM -Description: The Qt Visual Studio Tools 
allow developers to use the standard development environment without having to 
worry about any Qt-related build steps or tools.
10/03/2017 11:31:09 AM -Locale : en-US
10/03/2017 11:31:09 AM -MoreInfoURL: http://www.qt.io/
10/03/2017 11:31:09 AM -InstalledByMSI : False
10/03/2017 11:31:09 AM -SupportedFrameworkVersionRange : [4.6,)
10/03/2017 11:31:09 AM -
10/03/2017 11:31:09 AM -SignatureState : Unsigned
10/03/2017 11:31:09 AM -Supported Products :
10/03/2017 11:31:09 AM -Microsoft.VisualStudio.Pro
10/03/2017 11:31:09 AM -Version : [15.0]
10/03/2017 11:31:09 AM -Microsoft.VisualStudio.Premium
10/03/2017 11:31:09 AM -Version : [15.0]
10/03/2017 11:31:09 AM -Microsoft.VisualStudio.Ultimate
10/03/2017 11:31:09 AM -Version : [15.0]
10/03/2017 11:31:09 AM -Microsoft.VisualStudio.Community
10/03/2017 11:31:09 AM -Version : [15.0]
10/03/2017 11:31:09 AM -
10/03/2017 11:31:09 AM -References :
10/03/2017 11:31:09 AM -Prerequisites  :
10/03/2017 11:31:09 AM -
---
10/03/2017 11:31:09 AM -Identifier   : 
Microsoft.VisualStudio.Component.CoreEditor
10/03/2017 11:31:09 AM -Name : Visual Studio core editor
10/03/2017 11:31:09 AM -Version  : [15.0.26208.0,16.0)
10/03/2017 11:31:09 AM -
10/03/2017 11:31:09 AM -
---
10/03/2017 11:31:09 AM -Identifier   : 
Microsoft.VisualStudio.Component.VC.CoreIde
10/03/2017 11:31:09 AM -Name : Visual Studio C++ core 
features
10/03/2017 11:31:09 AM -Version  : [15.0.26208.0,16.0)
10/03/2017 11:31:09 AM -
10/03/2017 11:31:09 AM - Signature Details...
10/03/2017 11:31:09 AM -Extension is not signed.
10/03/2017 11:31:09 AM -
10/03/2017 11:31:09 AM - Searching for applicable products...
10/03/2017 11:31:09 AM - Found installed product - Microsoft Visual Studio 
Professional 2013
10/03/2017 11:31:09 AM - Found installed product - Microsoft Visual Studio 2013 
Shell (Integrated)
10/03/2017 11:31:09 AM - Found installed product - Microsoft Visual Studio 
Professional 2015
10/03/2017 11:31:09 AM - Found installed product - Microsoft Visual Studio 
Community 2015
10/03/2017 11:31:09 AM - Found installed product - Microsoft Visual Studio 2015 
Shell (Integrated)
10/03/2017 11:31:09 AM - Found installed product - Global Location
10/03/2017 11:31:09 AM - Found installed product - Visual Studio Professional 
2017
10/03/2017 11:31:09 AM - PKGDEF Information: Looking for master PkgDef file, 
Path: C:\Program Files (x86)\Microsoft Visual 
Studio\2017\Professional\Common7\IDE\master.pkgdef

10/03/2017 11:31:09 AM - PKGDEF Information: Creating PkgDefCacheNonVolatile
10/03/2017 11:31:09 AM - PKGDEF Information: Double-checking master pkgdef file
10/03/2017 11:31:09 AM - PKGDEF Information: PkgDefManagement initialized
10/03/2017 11:31:09 AM - PKGDEF Information: RootFolder, Path: C:\Program Files 
(x86)\Microsoft Visual Studio\2017\Professional\

10/03/2017 11:31:09 AM - PKGDEF Information: ShellFolder, Path: C:\Program 
Files (x86)\Microsoft Visual Studio\2017\Professional\

10/03/2017 11:31:09 AM - PKGDEF Information: PkgDefSearchPath, Path: C:\Program 
Files 

Re: [Interest] Support for Visual Studio 2017

[Tom Isaacson]

Unfortunately it fails for me:

10/03/2017 11:31:08 AM - Microsoft VSIX Installer
10/03/2017 11:31:08 AM - ---
10/03/2017 11:31:08 AM - vsixinstaller.exe version:
10/03/2017 11:31:08 AM - 15.0.26228.0 built by: D15REL
10/03/2017 11:31:08 AM - ---
10/03/2017 11:31:08 AM - Command line parameters:
10/03/2017 11:31:08 AM - C:\Program Files (x86)\Microsoft Visual 
Studio\2017\Professional\Common7\IDE\VSIXInstaller.exe,C:\Users\Tom\Downloads\qt-vsaddin-msvc2017-2.1.1-beta
 (1).vsix
10/03/2017 11:31:08 AM - ---
10/03/2017 11:31:08 AM - Microsoft VSIX Installer
10/03/2017 11:31:08 AM - ---
10/03/2017 11:31:09 AM - Initializing Install...
10/03/2017 11:31:09 AM - Extension Details...
10/03/2017 11:31:09 AM -Identifier : 
QtVsTools.13121978-cd02-4fd0-89bd-e36f85abe16a
10/03/2017 11:31:09 AM -Name   : Qt Visual Studio Tools
10/03/2017 11:31:09 AM -Author : The Qt Company Ltd.
10/03/2017 11:31:09 AM -Version: 2.1.1
10/03/2017 11:31:09 AM -Description: The Qt Visual Studio Tools 
allow developers to use the standard development environment without having to 
worry about any Qt-related build steps or tools.
10/03/2017 11:31:09 AM -Locale : en-US
10/03/2017 11:31:09 AM -MoreInfoURL: http://www.qt.io/
10/03/2017 11:31:09 AM -InstalledByMSI : False
10/03/2017 11:31:09 AM -SupportedFrameworkVersionRange : [4.6,)
10/03/2017 11:31:09 AM - 
10/03/2017 11:31:09 AM -SignatureState : Unsigned
10/03/2017 11:31:09 AM -Supported Products : 
10/03/2017 11:31:09 AM -Microsoft.VisualStudio.Pro
10/03/2017 11:31:09 AM -Version : [15.0]
10/03/2017 11:31:09 AM -Microsoft.VisualStudio.Premium
10/03/2017 11:31:09 AM -Version : [15.0]
10/03/2017 11:31:09 AM -Microsoft.VisualStudio.Ultimate
10/03/2017 11:31:09 AM -Version : [15.0]
10/03/2017 11:31:09 AM -Microsoft.VisualStudio.Community
10/03/2017 11:31:09 AM -Version : [15.0]
10/03/2017 11:31:09 AM - 
10/03/2017 11:31:09 AM -References : 
10/03/2017 11:31:09 AM -Prerequisites  : 
10/03/2017 11:31:09 AM -
---
10/03/2017 11:31:09 AM -Identifier   : 
Microsoft.VisualStudio.Component.CoreEditor
10/03/2017 11:31:09 AM -Name : Visual Studio core editor
10/03/2017 11:31:09 AM -Version  : [15.0.26208.0,16.0)
10/03/2017 11:31:09 AM - 
10/03/2017 11:31:09 AM -
---
10/03/2017 11:31:09 AM -Identifier   : 
Microsoft.VisualStudio.Component.VC.CoreIde
10/03/2017 11:31:09 AM -Name : Visual Studio C++ core 
features
10/03/2017 11:31:09 AM -Version  : [15.0.26208.0,16.0)
10/03/2017 11:31:09 AM - 
10/03/2017 11:31:09 AM - Signature Details...
10/03/2017 11:31:09 AM -Extension is not signed.
10/03/2017 11:31:09 AM - 
10/03/2017 11:31:09 AM - Searching for applicable products...
10/03/2017 11:31:09 AM - Found installed product - Microsoft Visual Studio 
Professional 2013
10/03/2017 11:31:09 AM - Found installed product - Microsoft Visual Studio 2013 
Shell (Integrated)
10/03/2017 11:31:09 AM - Found installed product - Microsoft Visual Studio 
Professional 2015
10/03/2017 11:31:09 AM - Found installed product - Microsoft Visual Studio 
Community 2015
10/03/2017 11:31:09 AM - Found installed product - Microsoft Visual Studio 2015 
Shell (Integrated)
10/03/2017 11:31:09 AM - Found installed product - Global Location
10/03/2017 11:31:09 AM - Found installed product - Visual Studio Professional 
2017
10/03/2017 11:31:09 AM - PKGDEF Information: Looking for master PkgDef file, 
Path: C:\Program Files (x86)\Microsoft Visual 
Studio\2017\Professional\Common7\IDE\master.pkgdef

10/03/2017 11:31:09 AM - PKGDEF Information: Creating PkgDefCacheNonVolatile
10/03/2017 11:31:09 AM - PKGDEF Information: Double-checking master pkgdef file
10/03/2017 11:31:09 AM - PKGDEF Information: PkgDefManagement initialized
10/03/2017 11:31:09 AM - PKGDEF Information: RootFolder, Path: C:\Program Files 
(x86)\Microsoft Visual Studio\2017\Professional\

10/03/2017 11:31:09 AM - PKGDEF Information: ShellFolder, Path: C:\Program 
Files (x86)\Microsoft Visual Studio\2017\Professional\

10/03/2017 11:31:09 AM - PKGDEF Information: PkgDefSearchPath, Path: C:\Program 
Files (x86)\Microsoft Visual 
Studio\2017\Professional\Common7\IDE\Extensions;C:\Program Files 
(x86)\Microsoft Visual 
Studio\2017\Professional\Common7\IDE\CommonExtensions;C:\Program Files 
(x86)\Microsoft Visual 

Re: [Interest] How do you want to select exactly C++11 with GCC 6+?

[Sérgio Martins]

On Thu, Mar 9, 2017 at 1:13 PM, Thiago Macieira
 wrote:
> This is a straw poll to see if we should change qmake's behaviour for Qt 5.9.
>
> GCC 6 and ICC 17, in the absence of -std= comipler options, default ot C++14.
> So I have two questions:
>
> 1) is there a need for qmake to provide a way to select *exactly* C++11, not a
> later, available version?

I wouldn't worry much about it, aren't C++11 and C++14 ABI compatible ?
If there's some implementation where this is an issue then qmake
should provide an obscure way to workaround and not through CONFIG.

Regards,
Sérgio Martins
___
Interest mailing list
Interest@qt-project.org
http://lists.qt-project.org/mailman/listinfo/interest

Re: [Interest] How do you want to select exactly C++11 with GCC 6+?

[Konrad Rosenbaum]

On Thu, March 9, 2017 15:54, Thiago Macieira wrote:
> Em quinta-feira, 9 de março de 2017, às 15:04:55 CET, Konrad Rosenbaum
> escreveu:
>> CONFIG -= c++14 feels like "give me whatever predates C++ 14, even if it
>> is C++ 98" or simply "I'm a hillbilly, disable those newfangled C++ 14
>> features!"
>
> I guess you'd do [changed to future version as C++11 is now required]:
>
> CONFIG += c++14
> CONFIG -= c++1z

Yes, that would look reasonable to select exactly C++ 14 to my eye.



Konrad

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

Re: [Interest] How do you want to select exactly C++11 with GCC 6+?

[Michael Sué]

> 1) is there a need for qmake to provide a way to select *exactly* C++11, not 
> a later, available version?
I would say no.

> 2) 
but IF well then I would prefer option I
CONFIG += c++11  means plus c++11 language extensions
CONFIG += c++14  means plus c++11 and plus c++14 language extensions

- Michael.


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

Re: [Interest] How do you want to select exactly C++11 with GCC 6+?

[Massimiliano Maini]

On 9 March 2017 at 15:53, Thiago Macieira  wrote:
>
> Em quinta-feira, 9 de março de 2017, às 14:47:58 CET, Konstantin Tokarev
> escreveu:
> > I would prefer something like CXX_STANDARD = c++11
>
> And how do you select "C++11 or later" ?

 CXX_STANDARD = min_c++11

Or something similar ?
___
Interest mailing list
Interest@qt-project.org
http://lists.qt-project.org/mailman/listinfo/interest

Re: [Interest] How do you want to select exactly C++11 with GCC 6+?

[Thiago Macieira]

Em quinta-feira, 9 de março de 2017, às 15:04:55 CET, Konrad Rosenbaum 
escreveu:
> CONFIG -= c++14 feels like "give me whatever predates C++ 14, even if it
> is C++ 98" or simply "I'm a hillbilly, disable those newfangled C++ 14
> features!"

I guess you'd do [changed to future version as C++11 is now required]:

CONFIG += c++14
CONFIG -= c++1z

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

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

Re: [Interest] How do you want to select exactly C++11 with GCC 6+?

[Thiago Macieira]

Em quinta-feira, 9 de março de 2017, às 14:47:58 CET, Konstantin Tokarev 
escreveu:
> I would prefer something like CXX_STANDARD = c++11

And how do you select "C++11 or later" ?

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

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

Re: [Interest] How do you want to select exactly C++11 with GCC 6+?

[Konrad Rosenbaum]

On Thu, March 9, 2017 14:13, Thiago Macieira wrote:
> 1) is there a need for qmake to provide a way to select *exactly* C++11,
> not a
> later, available version?

I don't see it. If I wanted to do compiler behavior tests I'd either not
use qmake or use a more specific command like:

QMAKE_CXXFLAGS += -std=c++11

(in full knowledge of the risks of course...)

> 2) if the answer is "yes", how would you prefer to do so?
>   option I:   CONFIG += c++11
>   option II:  CONFIG -= c++14 (obviously disables later 
> editions too)

Both feel kind of wrong to me:

CONFIG += c++11 feels more like "give me at least C++ 11 or newer"

CONFIG -= c++14 feels like "give me whatever predates C++ 14, even if it
is C++ 98" or simply "I'm a hillbilly, disable those newfangled C++ 14
features!"



Konrad

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

Re: [Interest] How do you want to select exactly C++11 with GCC 6+?

[Konstantin Tokarev]

09.03.2017, 16:14, "Thiago Macieira" :
> This is a straw poll to see if we should change qmake's behaviour for Qt 5.9.
>
> GCC 6 and ICC 17, in the absence of -std= comipler options, default ot C++14.
> So I have two questions:
>
> 1) is there a need for qmake to provide a way to select *exactly* C++11, not a
> later, available version?
>
> 2) if the answer is "yes", how would you prefer to do so?
> option I: CONFIG += c++11
> option II: CONFIG -= c++14 (obviously disables later editions too)
>
> I want to first get just gut feeling, so I won't post pros and cons of the
> approaches.

I would prefer something like CXX_STANDARD = c++11

> --
> Thiago Macieira - thiago.macieira (AT) intel.com
>   Software Architect - Intel Open Source Technology Center
>
> ___
> Interest mailing list
> Interest@qt-project.org
> http://lists.qt-project.org/mailman/listinfo/interest

-- 
Regards,
Konstantin
___
Interest mailing list
Interest@qt-project.org
http://lists.qt-project.org/mailman/listinfo/interest

Re: [Interest] How do you want to select exactly C++11 with GCC 6+?

[Thiago Macieira]

Em quinta-feira, 9 de março de 2017, às 14:24:13 CET, Viktor Engelmann 
escreveu:
> I'd prefer option I, because saying "I want X" feels more precise and to
> the point than "I don't want Y". In a restaurant, you don't order "not
> fish", do you?

Uh... sometimes you do. I order hamburgers and say, "no pickles".

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

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

Re: [Interest] How do you want to select exactly C++11 with GCC 6+?

[Viktor Engelmann]

I'd prefer option I, because saying "I want X" feels more precise and to
the point than "I don't want Y". In a restaurant, you don't order "not
fish", do you?


On 09.03.2017 14:13, Thiago Macieira wrote:
> This is a straw poll to see if we should change qmake's behaviour for Qt 5.9.
>
> GCC 6 and ICC 17, in the absence of -std= comipler options, default ot C++14. 
> So I have two questions:
>
> 1) is there a need for qmake to provide a way to select *exactly* C++11, not 
> a 
> later, available version?
>
> 2) if the answer is "yes", how would you prefer to do so?
>   option I:   CONFIG += c++11
>   option II:  CONFIG -= c++14 (obviously disables later 
> editions too)
>
> I want to first get just gut feeling, so I won't post pros and cons of the 
> approaches.

-- 

Viktor Engelmann
Software Engineer

The Qt Company GmbH
Rudower Chaussee 13
D-12489 Berlin

viktor.engelm...@qt.io
+49 151 26784521

http://qt.io
Geschäftsführer: Mika Pälsi, Juha Varelius, Mika Harjuaho
Sitz der Gesellschaft: Berlin
Registergericht: Amtsgericht Charlottenburg, HRB 144331 B

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

Re: [Interest] What is the status of Qt and MinGW 64 for Windows?

[Thiago Macieira]

Em quinta-feira, 9 de março de 2017, às 11:17:18 CET, Carel Combrink escreveu:
> Hi,
> 
> I would like to get a status update on what is the current
> thinking/planning regarding 64-bit applications on Windows using MinGW?
> 
> I am fully aware of the MinGW-64-Bit  page
> on the wiki, and have been following it for a while now.
> 
> Although the page has a lot of information regarding the different options,
> what is the conclusion?
> 
> Does the Qt Company plan to ship 64-bit MinGW Qt binaries with the
> installer (Opensource or Commercial) or is this completely off the roadmap?

I don't know about the Qt Company. The Qt Project has had this discussion and 
the conclusion is we want to, but we need to bring down the number of binaries 
generated. So it's unlikely to happen until we can drop one MSVC 2013 build.

> Should one rather switch to the MSVC compiler that does support compiling
> to 64 bit for which the installer contains the needed 64-bit binaries?

Not necessarily. If you want to use GCC, you should keep GCC. Just compile Qt 
from sources.

Unless you want qtwebengine. Because of an upstream decision we have no 
control or influece over, the only platform that supports qtwebengine is MSVC 
2015.

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

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

[Interest] How do you want to select exactly C++11 with GCC 6+?

[Thiago Macieira]

This is a straw poll to see if we should change qmake's behaviour for Qt 5.9.

GCC 6 and ICC 17, in the absence of -std= comipler options, default ot C++14. 
So I have two questions:

1) is there a need for qmake to provide a way to select *exactly* C++11, not a 
later, available version?

2) if the answer is "yes", how would you prefer to do so?
option I:   CONFIG += c++11
option II:  CONFIG -= c++14 (obviously disables later 
editions too)

I want to first get just gut feeling, so I won't post pros and cons of the 
approaches.
-- 
Thiago Macieira - thiago.macieira (AT) intel.com
  Software Architect - Intel Open Source Technology Center

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

[Interest] Diff between Qt-5.7.1 and Qt-5.8.0 on Android - Pointer Below the Cursor at Text Fields

[Robert Iakobashvili]

Hi,
Nexus-7 with Android-6

The same Qt app built with 5.7.1 works properly
and with 5.8.0 appears a blue pointer down the cursor at text fields.

The pointer is buggy and doesn't follow the cursor properly when positioning
and re-positioning child-windows/popups.

How to get rid from it?

Were it some theme changes or something else from 5.7 to 5.8?
Thanks

Kind regards,
Robert
___
Interest mailing list
Interest@qt-project.org
http://lists.qt-project.org/mailman/listinfo/interest

Re: [Interest] Support for Visual Studio 2017

[Karsten Heimrich]

Hi,

we've uploaded a beta version of the Qt Visual Studio Tools extension to 
http://download.qt.io/development_releases/vsaddin .

-- Karsten

-Original Message-
From: Interest [mailto:interest-bounces+karsten.heimrich=qt...@qt-project.org] 
On Behalf Of Tom Isaacson
Sent: Mittwoch, 8. März 2017 18:16
To: Qt Interest 
Subject: Re: [Interest] Support for Visual Studio 2017

Thanks. Keep up at https://bugreports.qt.io/browse/QTVSADDINBUG-459

Tom Isaacson

-Original Message-
From: Interest [mailto:interest-bounces+tom.isaacson=navico@qt-project.org] 
On Behalf Of Karsten Heimrich
Sent: Thursday, 9 March 2017 05:33
To: Qt Interest 
Subject: Re: [Interest] Support for Visual Studio 2017

We'll release a test version for VS 2017 within the next few days.

-- Karsten

-Original Message-
From: Interest [mailto:interest-bounces+karsten.heimrich=qt...@qt-project.org] 
On Behalf Of Tom Isaacson
Sent: Dienstag, 7. März 2017 17:47
To: Qt Interest 
Subject: Re: [Interest] Support for Visual Studio 2017

*crickets*

Visual Studio 2017 is being released today. Does anyone know if there's a plan 
to add support to the Qt Visual Studio Plug-In?

Tom Isaacson

-Original Message-
From: Interest [mailto:interest-bounces+tom.isaacson=navico@qt-project.org] 
On Behalf Of Tom Isaacson
Sent: Monday, 27 February 2017 07:46
To: Constantin Makshin ; Qt Interest 

Subject: Re: [Interest] Support for Visual Studio 2017

Final release is on March 7th.

We still need the Qt Visual Studio Plug-In. There's a comment from Karsten 
Heimrich on the last release page:
http://blog.qt.io/blog/2016/11/11/qt-visual-studio-tools-2-0-released/
"I did an initial commit that supports VS 2017 RC, you can find it here: 
https://codereview.qt-project.org/#/c/177499 Once we did some more testing, I 
will upload an RC at download.qt.io."
Does anyone know if this happened?

Tom Isaacson

-Original Message-
From: Interest [mailto:interest-bounces+tom.isaacson=navico@qt-project.org] 
On Behalf Of Constantin Makshin
Sent: Sunday, 26 February 2017 12:51
To: Qt Interest 
Subject: Re: [Interest] Support for Visual Studio 2017

Well, if that's true (we still have to wait for the final release of
VS2017) then, as Harri said, upgrade from VS2015 will be much easier for 
everyone. :)

On 02/24/2017 08:51 PM, Tom Isaacson wrote:
> VS2017 is ABI-compatible with VS2015:
> http://stackoverflow.com/questions/40854917/is-visual-c-2017-binary-co
> mpatible-with-vc-2015
> 
> There's a comment here that suggests VS2017 uses the same C++ standard 
> library implementation (search for "msvcp140.dll"):
> https://news.ycombinator.com/item?id=12967901
> "MSVC STL dev here. We're doing something different this time around. VS 2015 
> RTM and Update 1/2/3 were binary-compatible (as usual) while adding lots of 
> features to the compiler and STL (unusual). VS 2017 RTM and its Updates will 
> continue to be binary-compatible while adding features, meaning that our DLLs 
> are still vcruntime140.dll, msvcp140.dll, etc. The versions are admittedly a 
> mess, so here's the magic decoder ring:
> VS 2015: IDE version 14, DLL version 140, toolset version 140, compiler 
> version 19.0 (the C++ compiler is older than the Visual part of Visual C++).
> VS 2017: IDE version 15, DLL version 140 (same!), toolset version 141, 
> compiler version 19.1 We still recommend that you build everything with VS 
> 2017 consistently, as this will give you the most performance and 
> correctness. However, you can mix in object files, static libraries, and DLLs 
> compiled with previous versions all the way back to 2015 RTM, and things will 
> continue to work (although you won't necessarily activate fixes in the newer 
> version).
> For more info, read the comments on 
> https://blogs.msdn.microsoft.com/vcblog/2016/08/24/c1417-fea... where I 
> mentioned WCFB02."
> 
> Tom Isaacson
> 
> 
> -Original Message-
> From: Interest
> [mailto:interest-bounces+tom.isaacson=navico@qt-project.org] On 
> Behalf Of Constantin Makshin
> Sent: Saturday, 25 February 2017 00:22
> To: Qt Interest 
> Subject: Re: [Interest] Support for Visual Studio 2017
> 
> Still looks somewhat risky to me. Unless VS2017 uses C++ standard library 
> implementation from VS2015's "msvcp140.dll", of course.
> 
> On 02/24/2017 12:44 PM, Tom Isaacson wrote:
>> I had the prebuilt VS2015 libraries downloaded and installed and I was able 
>> to rebuild and run our app in VS2017. I didn't have to rebuild Qt myself.
>>
>>
>> Tom Isaacson
>>
>> -Original Message-
>> From: Interest
>> [mailto:interest-bounces+tom.isaacson=navico@qt-project.org] On 
>> Behalf Of Harri Porten
>> Sent: Friday, 24 February 2017 20:30
>> To: interest@qt-project.org
>> Subject: Re: [Interest] Support for Visual Studio 2017
>>
>> On 

[Interest] What is the status of Qt and MinGW 64 for Windows?

[Carel Combrink]

Hi,

I would like to get a status update on what is the current
thinking/planning regarding 64-bit applications on Windows using MinGW?

I am fully aware of the MinGW-64-Bit  page
on the wiki, and have been following it for a while now.

Although the page has a lot of information regarding the different options,
what is the conclusion?

Does the Qt Company plan to ship 64-bit MinGW Qt binaries with the
installer (Opensource or Commercial) or is this completely off the roadmap?

Should one rather switch to the MSVC compiler that does support compiling
to 64 bit for which the installer contains the needed 64-bit binaries?

Any input will be appreciated to help in determining the correct route, to
start the transition to 64-bit applications.

Regards,
___
Interest mailing list
Interest@qt-project.org
http://lists.qt-project.org/mailman/listinfo/interest