Re: [Interest] Qt 5.8.0 RC build under windows

2017-01-19 Thread Gunnar Roth 
>> 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'
>>
>> What is that and why it can be? How to avoid that error?

>That looks like a genuine problem, but I have no clue what it is about. Please
>report it against Qt3D.

Well thats an error on the directx 3d 12.0 scenegraph implementationin 
qtdeclarative, not Qt3d.

I have no problem compiling 5.8.0rc with vs2015 upd3  ( well angle crashes, my 
latest assumption is use of ltcg ) it brings its own win10 sdk.
I am also able to compile with vs2017rc ( using a patch from 5.8).

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

Re: [Interest] Shadow Build Question

2017-01-19 Thread Carel Combrink 
Just my 2c: Never ignore the warning when building QtCreator from source.

I've had numerous issues because of this on windows:
https://bugreports.qt.io/browse/QTCREATORBUG-14917

Regards

On Fri, Jan 20, 2017 at 4:26 AM, Thiago Macieira 
wrote:

> On sexta-feira, 20 de janeiro de 2017 00:44:14 PST Konstantin Shegunov
> wrote:
> > If I recall correctly, it's supposedly a limitation of qmake. But, again
> if
> > memory serves me, you can safely ignore the warning in most cases (take
> > this with a grain of salt, however).
>
> Indeed. There's a bug somewhere in the code that deals with making paths
> relative and we never bothered to investigate & fix. So YMMV.
>
> --
> 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] QThreadPool - global instance or custom one

2017-01-19 Thread Frank Rueter | OHUfx 

Great, thanks for the quick reply and confirmation.
One more question: Would you create one QThreadPool instance for the 
entire application or create new instances as you go (from within 
different modules). Does it matter?


Cheers,
frank

On 20/01/17 3:29 PM, Thiago Macieira wrote:

On sexta-feira, 20 de janeiro de 2017 11:59:31 PST Frank Rueter | OHUfx wrote:

Hi all,

I have started using QThreadPool for the first time and am wondering if
it's save/recommended to create my own instance of it or to always use
the global instance?

The rule I use is that you should use your own pool if you plan on launching
tasks that may block, but it's ok to use the global one if you need to run
things that run as fast as they can without blocking.

QHostInfo uses its own thread pool because it calls a blocking function that
is known to sometimes take 30 seconds to return (getaddrinfo).


In my case my app will run inside a host application, so my gut feeling
says to create my own thread pool so I don't accidentally hijack the
host application's pool, but I may be wrong?!

You're probably right. QHostInfo's example also matches your thinking: Qt's
behind-the-scenes usage should not affect the main application's ability to
use the global thread pool.



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

Re: [Interest] Doubt extending my app functions ability

2017-01-19 Thread Ernesto 

Bob,

Thanks to you I achieved my goal, in my last mail about Qt plugins I 
only had a questions about the diferences of "reinterpret_cas" and 
"dynamic_cast" which you answered me whit a link of a web page that 
explain all cast operators of C++.


However I will look around your link above and I will comment you about it.


Thanks again.

Your friend,

Ernesto


El 20/01/2017 a las 1:08, Bob Hood escribió:

On 1/12/2017 6:23 AM, Ernesto wrote:


Hello to everyone,

My name is Ernesto. I am a beginner in Qt programming and I have an 
specifics problems whit my first big project (desktop app). Let me 
explain myself:


I have to include plugins or add-ons to my application for new file 
format types




Ernesto, I don't know if you finally solved your issues, but I've just 
posted the project I have been working on which uses Qt plug-ins in 
the ways I previously described:


http://github.com/b0bh00d/Newsroom

This should give you a good example of a working Qt application that 
uses plug-ins to extend its functionality.Sorry I wasn't able to 
reference it earlier.




__ Información de ESET NOD32 Antivirus, versión de la base de 
firmas de virus 13498 (20160516) __


ESET NOD32 Antivirus ha comprobado este mensaje.

http://www.eset.com


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

Re: [Interest] QThreadPool - global instance or custom one

2017-01-19 Thread Thiago Macieira 
On sexta-feira, 20 de janeiro de 2017 11:59:31 PST Frank Rueter | OHUfx wrote:
> Hi all,
> 
> I have started using QThreadPool for the first time and am wondering if
> it's save/recommended to create my own instance of it or to always use
> the global instance?

The rule I use is that you should use your own pool if you plan on launching 
tasks that may block, but it's ok to use the global one if you need to run 
things that run as fast as they can without blocking.

QHostInfo uses its own thread pool because it calls a blocking function that 
is known to sometimes take 30 seconds to return (getaddrinfo).

> In my case my app will run inside a host application, so my gut feeling
> says to create my own thread pool so I don't accidentally hijack the
> host application's pool, but I may be wrong?!

You're probably right. QHostInfo's example also matches your thinking: Qt's 
behind-the-scenes usage should not affect the main application's ability to 
use the global thread pool.

-- 
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] Shadow Build Question

2017-01-19 Thread Thiago Macieira 
On sexta-feira, 20 de janeiro de 2017 00:44:14 PST Konstantin Shegunov wrote:
> If I recall correctly, it's supposedly a limitation of qmake. But, again if
> memory serves me, you can safely ignore the warning in most cases (take
> this with a grain of salt, however).

Indeed. There's a bug somewhere in the code that deals with making paths 
relative and we never bothered to investigate & fix. So YMMV.

-- 
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] Qt 5.8.0 RC build under windows

2017-01-19 Thread Thiago Macieira 
On quinta-feira, 19 de janeiro de 2017 15:55:41 PST Jason H wrote:
> I really think Qt needs a compile tool (like the Linux kernel has/had (make
> menuconfig or xconfig) ) that will also provide telemetry* when a build
> fails. I *never* have had Qt "just compile" and these days I'm compiling it
> for at least 3 platforms.
> 
> Heck even a make clean doesn't complete without errors.
> 
> *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 information that they don't want shared. Not to mention that 
it's another possible point of failure, for example on build servers without 
Internet connectivity.

-- 
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] Qt 5.8.0 RC build under windows

2017-01-19 Thread Thiago Macieira 
On quinta-feira, 19 de janeiro de 2017 16:54:58 PST Prav wrote:
> 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 you added patch to remove -no-rtti flag for
> 5.8.1. I got it.

Yeah, because I had three choices:

 a) leave it, which meant that you could compile qtbase with -no-rtti, but 
you'd run into a compiler error later if you tried to compile qtdeclarative

 b) remove the option, so that no one can get a compiler error

 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, (a) didn't look nice.

> >>So finally : Qt version 5.8.0 can NOT be build under Win7 with Win7SDK!?
> >>(It seems Qt for desktop need some definitions from WinRT ... who know
> >>why)>
> >Qt 5.8 can be built under Win7, but you should use the Win10SDK. The reason
> >for that is that you want your programs to support Windows 10, regardless
> >of what you use to develop.
> 
> OK. Someone added unknown Win10 features to Qt lib unconditionally and now
> desktop Qt build depends on WinRT SDK and as result Qt can not be build
> with Win7SDK now.
> I got this also.

Nope. It doesn't depend on the WinRT SDK. It depends on the Windows (desktop) 
8 SDK. Requiring you to have the latest SDK is an acceptable compromise.

> I do NOT feel good about how easy and invisibly such fundamental
> compatibility features are lost in Qt because of very small and probably
> unimportant changes in Qt code. I can only live with Qt in the way it will
> be created by Thiago and others Qt's developers.

Explain to me why you want your applications, when run on Windows 10, *not* to 
have the best functionality. Note that it will still run on Windows 7 and 8.1, 
with the same binary.

If you give me a good enough reason, I will consider applying a fix myself.

> But I still want to be able to build it under windows? I still do not
> understand why I still have error (even when I use Win10SDK and if I will
> NOT use -no-rtti): error is in :
> 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'
> 
> What is that and why it can be? How to avoid that error?

That looks like a genuine problem, but I have no clue what it is about. Please 
report it against Qt3D.

-- 
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] I can´t compile Qt statically (statically link)

2017-01-19 Thread Thiago Macieira 
On quinta-feira, 19 de janeiro de 2017 10:17:37 PST Etienne Sandré-Chardonnal 
wrote:
> Hi,
> 
> 5.6.2 is not necessarily the best 5.6 option regarding compiling Qt. There
> is at least a regression between 5.6.1 and 5.6.2 which prevents me building
> a static Qt with system libpng.
> 
> https://bugreports.qt.io/browse/QTBUG-57148

The problem is not a static Qt, but the static libpng. We never test that, so 
if you want to see that fixed, you'll need to supply the fix yourself.

I can also confidently say you're the first person I've ever seen trying to use 
a static system libpng. Not to mention doing that on Windows.

> I'm currently stuck with 5.6.1 as this is the latest version which compiles
> under windows with system libpng. Latest release do not mean less
> compilation issues.

Indeed, but Ernesto may not have your problem.
-- 
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] QThreadPool functionality for QThreads

2017-01-19 Thread Thiago Macieira 
On quinta-feira, 19 de janeiro de 2017 07:55:12 PST Elvis Stansvik wrote:
> Frank, another threading approach in Qt which we haven't mentioned yet
> is QtConcurrent. I use that myself in an application where I had to
> load a series of large tomographic volumes using VTK (so blocking
> I/O). It might not be a good fit for your use case, but thought I
> should mention it for brevity.

Or you can use Thread Building Blocks too.

-- 
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] QTest + QSignalSpy doesn't seem to work with deferred signals

2017-01-19 Thread Bob Hood 

On 1/19/2017 2:29 AM, Viktor Engelmann wrote:


QSignalSpy::wait has a race condition though. When the signal is emitted 
from a different thread, it might come before you called .wait and then the 
wait will time out and return false (so it looks like the signal wasn't 
emitted). You can store the value of spy.size() and after the wait compare 
it to the current spy.size(). That is more robust, but when the signal is 
emitted before you start the .wait, the .wait will still wait for the full 
timeout time.


QTRY_COMPARE terminates as soon as the condition is met, so 
QTRY_COMPARE(spy.size(), 1) is better, but it uses a timeout of only 5 
seconds, which should be enough in most cases, but I have seen cases where a 
signal came 11 seconds after I caused it to be emitted (due to network 
and/or system load). I used QTRY_COMPARE_WITH_TIMEOUT instead to set a 
higher timeout.




Thanks for the info, Viktor.  :)

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

Re: [Interest] Doubt extending my app functions ability

2017-01-19 Thread Bob Hood 

On 1/12/2017 6:23 AM, Ernesto wrote:


Hello to everyone,

My name is Ernesto. I am a beginner in Qt programming and I have an 
specifics problems whit my first big project (desktop app). Let me explain 
myself:


I have to include plugins or add-ons to my application for new file format 
types




Ernesto, I don't know if you finally solved your issues, but I've just posted 
the project I have been working on which uses Qt plug-ins in the ways I 
previously described:


http://github.com/b0bh00d/Newsroom

This should give you a good example of a working Qt application that uses 
plug-ins to extend its functionality.Sorry I wasn't able to reference it earlier.


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

[Interest] QThreadPool - global instance or custom one

2017-01-19 Thread Frank Rueter | OHUfx 

Hi all,

I have started using QThreadPool for the first time and am wondering if 
it's save/recommended to create my own instance of it or to always use 
the global instance?
I.e. the docs all tend to refer to the global instance but they don't 
say anything about creating your own.


Are there any pros and cons?

In my case my app will run inside a host application, so my gut feeling 
says to create my own thread pool so I don't accidentally hijack the 
host application's pool, but I may be wrong?!


Any insight on this?

Cheers,
frank

--
ohufxLogo 50x50  	*vfx compositing 
 | *workflow customisation and 
consulting * *


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

Re: [Interest] Shadow Build Question

2017-01-19 Thread Konstantin Shegunov 
If I recall correctly, it's supposedly a limitation of qmake. But, again if
memory serves me, you can safely ignore the warning in most cases (take
this with a grain of salt, however).

On Thu, Jan 19, 2017 at 7:07 PM, Adrian Jäkel  wrote:

> When configuring my project for shadow build and setting my build
> directory to somewhere, i get a warning symbol and message that my build
> directory has to be on the same level as the source directory. Whats the
> reasoning behind that? I cannot remember that it ever was a problem to have
> it somewhere else.
>
> Regards,
> Adrian
> ___
> 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] Qt 5.8.0 RC build under windows

2017-01-19 Thread Jason H 
How many platforms are you supporting?

None of the platform documentation for mobile is up-to-date.  I don't need 
documentation if I have a tool. Just update the tool because the docs never get 
updated.


> Sent: Thursday, January 19, 2017 at 12:28 PM
> From: "william.croc...@analog.com" 
> To: interest@qt-project.org
> Subject: Re: [Interest] Qt 5.8.0 RC build under windows
>
> On 01/19/2017 09:55 AM, Jason H wrote:
> > I really think Qt needs a compile tool
> 
> I would vote against that as it would be just another
> layer to be learned and for which something would eventually go wrong.
> (Kind of like what the aliens did to our space probe
>   in the first Star Trek movie.)
> 
> I prefer a well documented procedure using
> familiar old friends.
> 
___
Interest mailing list
Interest@qt-project.org
http://lists.qt-project.org/mailman/listinfo/interest

[Interest] Android networking: Won't connect

2017-01-19 Thread Jason H 
I have apps that work, and I remember having solved this problem before, but it 
escapes me... 

I am trying to use QML and XMLHttpRequest and the request foes from 1 to 4, 
which is CONNECTING to DONE. Nothing hits the server.

QT += core qml quick network websockets
android {
DISTFILES += \
android/AndroidManifest.xml \
android/gradle/wrapper/gradle-wrapper.jar \
android/gradlew \
android/res/values/libs.xml \
android/build.gradle \
android/gradle/wrapper/gradle-wrapper.properties \
android/gradlew.bat
OTHER_FILES += android/AndroidManifest.xml

ANDROID_EXTRA_LIBS += 
$$PWD/android/openssl/android-14-1.0.1s-arm/libcrypto.so 
$$PWD/android/openssl/android-14-1.0.1s-arm/libssl.so

ANDROID_PACKAGE_SOURCE_DIR = $$PWD/android
}

Anyone know what I'm missing?
___
Interest mailing list
Interest@qt-project.org
http://lists.qt-project.org/mailman/listinfo/interest

Re: [Interest] Qt 5.8.0 RC build under windows

2017-01-19 Thread william.croc...@analog.com 

On 01/19/2017 09:55 AM, Jason H wrote:

I really think Qt needs a compile tool


I would vote against that as it would be just another
layer to be learned and for which something would eventually go wrong.
(Kind of like what the aliens did to our space probe
 in the first Star Trek movie.)

I prefer a well documented procedure using
familiar old friends.


(like the Linux kernel has/had (make menuconfig or xconfig) ) that will also provide 
telemetry* when a build fails. I *never* have had Qt "just compile" and these 
days I'm compiling it for at least 3 platforms.

Heck even a make clean doesn't complete without errors.

*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.





Sent: Monday, January 16, 2017 at 11:04 AM
From: Prav 
To: "interest@qt-project.org" 
Subject: [Interest] Qt 5.8.0 RC build under windows

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 :
qtbase\src\plugins\platforms\windows\Makefile.Debug 
[.obj\debug\qwindowsservices.obj] Error 2
and it is :
qtbase\src\plugins\platforms\windows\qwin10helpers.cpp(53) : fatal error C1083: 
Cannot open include file: 'inspectable.h': No such file or directory

So it is something about Win10 (from name qwin10helpers.cpp). Who asked for 
Win10 features? I did not

So what? We really need Win10 SDK to compile Qt for Win7 or this is mistake in 
build system?


But OK. Let try Win10 SDK instead of Win7 SDK. Compiler will be same msvc2013 
(update 5). In that case I get another error. First error is in :
qtdeclarative\src\quick\Makefile.Release 
[.obj\release\qsgsoftwarepublicnodes.obj] Error 2
and it is
qtbase\include\qtcore\../../src/corelib/global/qglobal.h(1009) : error C2825: 
'T': must be a class or namespace when followed by '::'
 
A:\qtt\__\580\qtdeclarative\src\quick\scenegraph\adaptations\software\qsgsoftwarepublicnodes.cpp(101)
 : see reference to function template instantiation 'T 
qt_dynamic_cast_check(X,T *)' being 
compiled
 with
 [
 T=QSGSoftwarePixmapTexture *
,X=QSGTexture *
 ]

And some errors in the same file just after that :
qtbase\include\qtcore\../../src/corelib/global/qglobal.h(1009) : error C2039: 
'dynamic_cast_will_always_fail_because_rtti_is_disabled' : is not a member of 
'`global namespace''
qtbase\include\qtcore\../../src/corelib/global/qglobal.h(1009) : error C2146: 
syntax error : missing ';' before identifier 
'dynamic_cast_will_always_fail_because_rtti_is_disabled'
qtbase\include\qtcore\../../src/corelib/global/qglobal.h(1009) : error C2275: 
'T' : illegal use of this type as an expression
qtdeclarative\src\quick\scenegraph\adaptations\software\qsgsoftwarepublicnodes.cpp(101)
 : see declaration of 'T'
qtbase\include\qtcore\../../src/corelib/global/qglobal.h(1009) : error C2065: 
'dynamic_cast_will_always_fail_because_rtti_is_disabled' : undeclared identifier
qtdeclarative\src\quick\scenegraph\adaptations\software\qsgsoftwarepublicnodes.cpp(104)
 : see declaration of 'T'

Does anyone ever had such error in qtdeclarative? Why it happens?


I can download
qt-opensource-windows-x86-msvc2013-5.8.0-rc_699.exe
which mean that msvc2013 should be fine to compile Qt.


Finally:
1. I did something wrong?
2. Why there is need in Win10 SDK (this is feature or bug)?
3. May be some requirements changed for tools like perl or something else in 
5.8.0 version and this is why I can not build the Qt 5.8.0 RC?

Thanks in advance!



PS
I am building only some modules of Qt (if it matters ... but I belive it does 
not) :
qtbase
qtdeclarative
qtxmlpatterns

___
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

[Interest] Shadow Build Question

2017-01-19 Thread Adrian Jäkel 
When configuring my project for shadow build and setting my build 
directory to somewhere, i get a warning symbol and message that my build 
directory has to be on the same level as the source directory. Whats the 
reasoning behind that? I cannot remember that it ever was a problem to 
have it somewhere else.


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

Re: [Interest] Qt 5.8.0 RC build under windows

2017-01-19 Thread Jason H 
I really think Qt needs a compile tool (like the Linux kernel has/had (make 
menuconfig or xconfig) ) that will also provide telemetry* when a build fails. 
I *never* have had Qt "just compile" and these days I'm compiling it for at 
least 3 platforms. 

Heck even a make clean doesn't complete without errors.

*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.




> Sent: Monday, January 16, 2017 at 11:04 AM
> From: Prav 
> To: "interest@qt-project.org" 
> Subject: [Interest] Qt 5.8.0 RC build under windows
>
> 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 :
> qtbase\src\plugins\platforms\windows\Makefile.Debug 
> [.obj\debug\qwindowsservices.obj] Error 2
> and it is :
> qtbase\src\plugins\platforms\windows\qwin10helpers.cpp(53) : fatal error 
> C1083: Cannot open include file: 'inspectable.h': No such file or directory
> 
> So it is something about Win10 (from name qwin10helpers.cpp). Who asked for 
> Win10 features? I did not
> 
> So what? We really need Win10 SDK to compile Qt for Win7 or this is mistake 
> in build system?
> 
> 
> But OK. Let try Win10 SDK instead of Win7 SDK. Compiler will be same msvc2013 
> (update 5). In that case I get another error. First error is in :
> qtdeclarative\src\quick\Makefile.Release 
> [.obj\release\qsgsoftwarepublicnodes.obj] Error 2
> and it is
> qtbase\include\qtcore\../../src/corelib/global/qglobal.h(1009) : error C2825: 
> 'T': must be a class or namespace when followed by '::'
> 
> A:\qtt\__\580\qtdeclarative\src\quick\scenegraph\adaptations\software\qsgsoftwarepublicnodes.cpp(101)
>  : see reference to function template instantiation 'T 
> qt_dynamic_cast_check(X,T *)' being 
> compiled
> with
> [
> T=QSGSoftwarePixmapTexture *
> ,X=QSGTexture *
> ]
> 
> And some errors in the same file just after that :
> qtbase\include\qtcore\../../src/corelib/global/qglobal.h(1009) : error C2039: 
> 'dynamic_cast_will_always_fail_because_rtti_is_disabled' : is not a member of 
> '`global namespace''
> qtbase\include\qtcore\../../src/corelib/global/qglobal.h(1009) : error C2146: 
> syntax error : missing ';' before identifier 
> 'dynamic_cast_will_always_fail_because_rtti_is_disabled'
> qtbase\include\qtcore\../../src/corelib/global/qglobal.h(1009) : error C2275: 
> 'T' : illegal use of this type as an expression
> qtdeclarative\src\quick\scenegraph\adaptations\software\qsgsoftwarepublicnodes.cpp(101)
>  : see declaration of 'T'
> qtbase\include\qtcore\../../src/corelib/global/qglobal.h(1009) : error C2065: 
> 'dynamic_cast_will_always_fail_because_rtti_is_disabled' : undeclared 
> identifier
> qtdeclarative\src\quick\scenegraph\adaptations\software\qsgsoftwarepublicnodes.cpp(104)
>  : see declaration of 'T'
> 
> Does anyone ever had such error in qtdeclarative? Why it happens?
> 
> 
> I can download
> qt-opensource-windows-x86-msvc2013-5.8.0-rc_699.exe
> which mean that msvc2013 should be fine to compile Qt.
> 
> 
> Finally:
> 1. I did something wrong?
> 2. Why there is need in Win10 SDK (this is feature or bug)?
> 3. May be some requirements changed for tools like perl or something else in 
> 5.8.0 version and this is why I can not build the Qt 5.8.0 RC?
> 
> Thanks in advance!
> 
> 
> 
> PS
> I am building only some modules of Qt (if it matters ... but I belive it does 
> not) :
> qtbase
> qtdeclarative
> qtxmlpatterns
> 
> ___
> 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] Qt 5.8.0 RC build under windows

2017-01-19 Thread Prav 
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 you added patch to remove -no-rtti flag for 5.8.1.
I got it.

>>So finally : Qt version 5.8.0 can NOT be build under Win7 with Win7SDK!? (It
>>seems Qt for desktop need some definitions from WinRT ... who know why)
>Qt 5.8 can be built under Win7, but you should use the Win10SDK. The reason
>for that is that you want your programs to support Windows 10, regardless of
>what you use to develop.
OK. Someone added unknown Win10 features to Qt lib unconditionally and now 
desktop Qt build depends on WinRT SDK and as result
Qt can not be build with Win7SDK now.
I got this also.

I do NOT feel good about how easy and invisibly such fundamental compatibility 
features are lost in Qt because of very small and probably unimportant changes 
in Qt code.
I can only live with Qt in the way it will be created by Thiago and others Qt's 
developers.


But I still want to be able to build it under windows? I still do not 
understand why I still have error (even when I use Win10SDK and if I will NOT 
use -no-rtti):
error is in :
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'

What is that and why it can be? How to avoid that error?

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

Re: [Interest] QTest + QSignalSpy doesn't seem to work with deferred signals

2017-01-19 Thread Viktor Engelmann 
QSignalSpy::wait has a race condition though. When the signal is emitted
from a different thread, it might come before you called .wait and then
the wait will time out and return false (so it looks like the signal
wasn't emitted). You can store the value of spy.size() and after the
wait compare it to the current spy.size(). That is more robust, but when
the signal is emitted before you start the .wait, the .wait will still
wait for the full timeout time.

QTRY_COMPARE terminates as soon as the condition is met, so
QTRY_COMPARE(spy.size(), 1) is better, but it uses a timeout of only 5
seconds, which should be enough in most cases, but I have seen cases
where a signal came 11 seconds after I caused it to be emitted (due to
network and/or system load). I used QTRY_COMPARE_WITH_TIMEOUT instead to
set a higher timeout.

regards

Viktor


Am 18.01.2017 um 18:28 schrieb Konrad Rosenbaum:
> Hi,
>
> On Wednesday, January 18, 2017 10:16:30 Bob Hood wrote:
>> I'm trying to develop a unit test for an deferred signal; i.e. one that
>> won't be emitted until the event loop has been allowed to run.  The case
>> looks like:
>>
>>void MyTest::user_info_deferred()
>>{
>>QVERIFY(qnam_class_ptr != nullptr);
>>
>>QSignalSpy spy(qnam_class_ptr, ::signal_userInfoReceived);
>>
>>// Retrieve account user information (deferred)
>>QCOMPARE(qname_class_ptr->userInfo(), true);
> I think you need to insert a spy.wait(...) here. Give the event loop a chance 
> to run...
>
>>QCOMPARE(spy.count(), 1);   // make sure the signal was emitted
>> exactly one time
>> QNAMClassUser info = qvariant_cast(spy.at(0).at(0));
>>}
> [cut]
>
>
>   Konrad
>
>
> ___
> Interest mailing list
> Interest@qt-project.org
> http://lists.qt-project.org/mailman/listinfo/interest

-- 

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



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

Re: [Interest] I can´t compile Qt statically (statically link)

2017-01-19 Thread Etienne Sandré-Chardonnal 
Hi,

5.6.2 is not necessarily the best 5.6 option regarding compiling Qt. There
is at least a regression between 5.6.1 and 5.6.2 which prevents me building
a static Qt with system libpng.

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

It also affects latest 5.7 and 5.8

I'm currently stuck with 5.6.1 as this is the latest version which compiles
under windows with system libpng. Latest release do not mean less
compilation issues.

Cheers



2017-01-16 18:25 GMT+01:00 Thiago Macieira :

> On segunda-feira, 16 de janeiro de 2017 04:05:28 PST Ernesto wrote:
> > Hello everyone,
> >
> > Now I´m blocked trying to (statically link) compile Qt statically (I´m
> > using Qt 5.5.0) to runs my applications without Qt and others libraries.
> > I did the following:
>
> First of all, please upgrade. You're not using the latest. At the very
> least
> to 5.6.2, but 5.7.1 or 5.8.0 are fine too.
>
> > First I went to /C:\Qt\Qt5.5.0\5.5\mingw492_32\mkspecs\win32-g++\/ and
> > edited /qmake.conf/
> [cut]
> > /configure -platform win32-g++ -static –release/
>
> You don't need to edit the mkspec. The -static option you passed to
> configure
> is enough.
>
> --
> 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