Hello, Maurice.
> However, when compiling Qt there are config tests verifying your
> environment is compatible against it. If not (for instance you do
> not have the correct SDK), those features will be turned off.
That seems very interesting features I never heard of. Can you explain little
bit
Title: Re: [Interest] Qt 5.8.0 RC build under windows
Hello, Mike and Everyone.
I compiled Qt 5.8.0 RC on Windows 7 with MSVC2013 and the Windows 8 SDK.
Can you (or anyone) share confgure string which successfully build Qt 5.8.0 RC (at least QtDeclarative)? Please tell which version of V
Hello, Thiago.
> Please explain why an application should not detect recent versions of Windows
> and use extra functionality that is there, making it better and/or more
> integrated with the OS.
I told you my opinion : what you called "extra functionality" does not exist
for desktop Qt and does
Hello, Thiago.
>> For example I do not understand : if c-compiler is simply a console app with
>> 10's years history of development ... what so important it could need from
>> WinVista so that it CAN NOT be run on older Windows?
> It's a tiny functionality called "getting the time". It's require
Hello, Thiago.
> You do realise that those flags aren't supported and they may not compile,
> right? I see commits going past every now and then fixing build failures with
> those.
Fixing commits goes to any part of Qt. I do not know what to tell. If some part
of Qt have many bugs then it probab
>> *Telemetry: the config, the resolved locations of libs and headers, compiler
>> and compiler version, modules selected for compile and anything else that
>> could help improve the Qt build experience.
> That's unacceptable for a lot of privacy-minded people and companies, as it
> might divulge
Hello, Gunnar.
>>> qtdeclarative\src\plugins\scenegraph\d3d12\Makefile.Debug
>>> [.obj\debug\qsgd3d12shadereffectnode.obj] Error 2 and it is :
>>> qtdeclarative\src\plugins\scenegraph\d3d12\qsgd3d12shadereffectnode.cpp(544)
>>> : error C2061: syntax error : identifier 'textureProviders'
>>>
>>> W
Hello, Thiago.
> c) remove the dynamic_cast by adding our own hand-rolled RTTI to detect
> whether the object in question was of the class that the code wanted
> (c) was too much work
Well ... Qt developers should decide about their style of development.
If Qt-developers gathered and decided that
Hello, Thiago.
>> And why Qt now needs RTTI? Qt 5.7.0 was building fine without RTTI. What
>> features added to 5.8.0 made RTTI mandatory I wonder?
> Someone added a dynamic_cast. That's all.
OK. Someone added dynamic_cast somewhere in Qt and whole Qt lost ability to be
build without RTTI. And y
Hello, Thiago.
> -no-rtti is not tested and clearly someone broke it. I've submitted a change
> to remove that option from configure starting with Qt 5.8.1.
I was thinking that without RTTI compiled programs became lighter and faster
(but never saw values of how much)
As I can see Qt tries to
Title: Re: [Interest] Qt 5.8.0 RC build under windows
Hello, Mike.
>Mike Chinander:
>I compiled Qt 5.8.0 RC on Windows 7 with MSVC2013 and the Windows 8 SDK.
OK. I got it. You are right ... there is no error with building of qwin10helpers.cpp with Win8SDK.
So finally : Qt version 5.8.0 can NOT
Hello, Thiago.
> Did you pass any options related to RTTI to configure?
Already wrote about that in previous message
Build errors with -no-rtti flag and without -no-rtti flag I gave in previous
message too
Previously I build Qt without RTTI with no problems. That is why I had RTTI
turned off.
I
Hello, Thiago.
>I want to see the command-line to the compiler
Here is compile command and its output (till next compile file)
cl -c -FIQtQuickDepends -YuQtQuickDepends
-Fp.pch\release\Qt5Quick_pch.pch -nologo -Zc:wchar_t -FS -O2 -MD
-Zc:strictStrings -D_HAS_EXCEPTIONS=0 -W3 -w34100 -w3
I tried to compile 5.8.0 RC just to see how healthy it is under windows with
msvc2013 (update 5) compiler.
As I understand using header and libs of Windows 7 SDK should be OK for
building Qt (at least it always was for previous versions).
But then I build I got errors. First error is in :
qtbas
Hi, Nikolai.
> I'm fine with making enum values "locatable", though personally I
> haven't missed them.
OK ... as result filled
https://bugreports.qt.io/browse/QTCREATORBUG-16060
Is there somewhere list of bugs planed for fixing for nearest versions of QtC?
May be in JIRA itself?
__
Hi, Christoph.
=>> But yeah, they are from hell and thou shall now use Qt on them.
:) :) :) :)
Yeah ... let's consider all platforms with non-multibyte locale codec from hell
This probably mean that it is worth to WARN in docs that for
QTextCodec::setCodecForLocale()
do not use UTF-16 or someth
Hi, Thiago.
> It boils down to "in theory, theory and practice are the same; in practice,
> they're not".
I am not a phylosopher ... only interested in practice.
> In theory, the locale codec can be anything, including 16- and 32-bit codecs.
> In practice, they can't because a lot of software i
17 matches
Mail list logo
