Re: [Interest] [Qt3D] SkyboxEntity textures are not rendered on Windows 7 (just black)

2017-04-14 Thread Oleg Evseev
Hi Sean,

As I wrote, I try to prepare test case example with same "basis" of 3d as
in my application, but it suddenly turned out to be valid.
Unfortunately I can't provide my entire application.

> Not sure what could be wrong off hand.

Ok, never mind then. It's not so important. I'll try to do test case latter
when got time for this.

Just had a little hope that you'll easy solve this, something like "Yes, in
commit #... we've changed ... so you need to ..." :)
Sorry for bothering.


2017-04-14 20:22 GMT+03:00 Sean Harmer :

> Hi,
>
> could you provide a test case for this please? Not sure what could be
> wrong off hand.
>
> Cheers,
>
> Sean
>
>
> On 14/04/2017 17:51, Oleg Evseev wrote:
>
>> Hi,
>>
>> Cause Sean is now get busy with SkyboxEntity, I take this opportunity to
>> ask what could be wrong:
>>
>> Related to qt3d I have Qml with loader that loads qml with Scene3D.
>> World3D - root entity is written in C++ and shared with qml with help of
>> qmlRegisterType.
>>
>> hierarchy is this:
>> World3D
>> -- renderSettings (as component)
>>  viewort (as activeFrameGraph)
>> -- renderSurfaceSelector
>>   cameraSelector
>> -- clearBuffers (light blue)
>>  QNoDraw
>> -- layerFilter
>>  layerBackground (added layer)
>> -- QSkyboxEntity (as a child)
>>  layerBackground (as component)
>> -- other objects
>>
>> (do not pay attention that there is no frustum culling disabling, it's
>> not relevant now)
>>
>> It works with qt 5.8 (on Windows 7 and Android), but when I moved to qt
>> 5.9 SkyboxEntity textures stop being rendered (they are just black) on
>> Windows (but they are render on Android).
>> I clean everything unrelated (other objects) to make simple example to
>> post the bug, but it  works! Skybox entity reneders fine.
>>
>> Even if I'm not setting parent for other objects in my application (that
>> is there is only skyboxentity in 3d scene) I can't do the same - skybox
>> is full black (it's not the clear buffer color by the way).
>>
>> I'm really confused what can be a problem?
>> Qml buttons on top of the Scene3D? - No, I check it, simple example
>> still works with them.
>>
>> Thanks in advance for help.
>>
>> ---
>> With regards, Oleg
>>
>>
>>
>>
>> ___
>> 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] [Qt3D] SkyboxEntity textures are not rendered on Windows 7 (just black)

2017-04-14 Thread Sean Harmer

Hi,

could you provide a test case for this please? Not sure what could be 
wrong off hand.


Cheers,

Sean

On 14/04/2017 17:51, Oleg Evseev wrote:

Hi,

Cause Sean is now get busy with SkyboxEntity, I take this opportunity to
ask what could be wrong:

Related to qt3d I have Qml with loader that loads qml with Scene3D.
World3D - root entity is written in C++ and shared with qml with help of
qmlRegisterType.

hierarchy is this:
World3D
-- renderSettings (as component)
 viewort (as activeFrameGraph)
-- renderSurfaceSelector
  cameraSelector
-- clearBuffers (light blue)
 QNoDraw
-- layerFilter
 layerBackground (added layer)
-- QSkyboxEntity (as a child)
 layerBackground (as component)
-- other objects

(do not pay attention that there is no frustum culling disabling, it's
not relevant now)

It works with qt 5.8 (on Windows 7 and Android), but when I moved to qt
5.9 SkyboxEntity textures stop being rendered (they are just black) on
Windows (but they are render on Android).
I clean everything unrelated (other objects) to make simple example to
post the bug, but it  works! Skybox entity reneders fine.

Even if I'm not setting parent for other objects in my application (that
is there is only skyboxentity in 3d scene) I can't do the same - skybox
is full black (it's not the clear buffer color by the way).

I'm really confused what can be a problem?
Qml buttons on top of the Scene3D? - No, I check it, simple example
still works with them.

Thanks in advance for help.

---
With regards, Oleg




___
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] [Qt3D] SkyboxEntity textures are not rendered on Windows 7 (just black)

2017-04-14 Thread Oleg Evseev
Hi,

Cause Sean is now get busy with SkyboxEntity, I take this opportunity to
ask what could be wrong:

Related to qt3d I have Qml with loader that loads qml with Scene3D. World3D
- root entity is written in C++ and shared with qml with help of
qmlRegisterType.

hierarchy is this:
World3D
-- renderSettings (as component)
 viewort (as activeFrameGraph)
-- renderSurfaceSelector
  cameraSelector
-- clearBuffers (light blue)
 QNoDraw
-- layerFilter
 layerBackground (added layer)
-- QSkyboxEntity (as a child)
 layerBackground (as component)
-- other objects

(do not pay attention that there is no frustum culling disabling, it's not
relevant now)

It works with qt 5.8 (on Windows 7 and Android), but when I moved to qt 5.9
SkyboxEntity textures stop being rendered (they are just black) on Windows
(but they are render on Android).
I clean everything unrelated (other objects) to make simple example to post
the bug, but it  works! Skybox entity reneders fine.

Even if I'm not setting parent for other objects in my application (that is
there is only skyboxentity in 3d scene) I can't do the same - skybox is
full black (it's not the clear buffer color by the way).

I'm really confused what can be a problem?
Qml buttons on top of the Scene3D? - No, I check it, simple example still
works with them.

Thanks in advance for help.

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


Re: [Interest] Qt 5.9 Beta

2017-04-14 Thread Thiago Macieira
Em sexta-feira, 14 de abril de 2017, às 03:37:10 PDT, Igor Mironchik escreveu:
> 14.04.2017 13:33, Igor Mironchik пишет:
> > Hi,
> > 
> > I tried to check with no qmake in the PATH.
> > 
> > And in this case I have two errors:
> > 
> > D:\Qt\5.9\msvc2015\mkspecs\features\toolchain.prf:129: error: Variable
> > QMAKE_CXX.COMPILER_MACROS is not defined.
> > 
> > :-1: error: msvc-version.conf loaded but QMAKE_MSC_VER isn't set
> > 
> > I'm using QtCreator and it should do the job even without qmake in the
> > path. And this issue is only in Qt 5.9 Beta version.
> 
> And one more... When I have no qmake in the PATH generates only
> .qmake.stash with:
> 
> QMAKE_CXX.INCDIRS = \
>  "c:\\Program Files (x86)\\Microsoft Visual Studio
> 14.0\\VC\\include\\" \
>  "c:\\Program Files (x86)\\Windows Kits\\8.1\\Include\\shared\\" \
>  "c:\\Program Files (x86)\\Windows Kits\\8.1\\Include\\um\\" \
>  "c:\\Program Files (x86)\\Windows Kits\\8.1\\Include\\winrt\\" \
>  d:\\3rdparty\\opencv\\build\\include\\
> QMAKE_CXX.LIBDIRS = \
>  "c:\\Program Files (x86)\\Microsoft Visual Studio 14.0\\VC\\lib\\" \
>  "c:\\Program Files (x86)\\Windows Kits\\8.1\\Lib\\winv6.3\\um\\x86\\" \
> d:\\3rdparty\\opencv\\build\\x86\\vc12\\lib\\
> 
> And if delete .qmake.stash and re-run qmake then following error:
> 
> D:\Qt\5.9\msvc2015\mkspecs\features\toolchain.prf:129: error: Variable
> QMAKE_CXX.COMPILER_MACROS is not defined.

I don't know what this is. The only possibility I can see is that it tried to 
run the compiler to get the predefined macros and failed.

Can you rerun with -d -d, capture stderr and send it to me directly?

-- 
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] Q_GADGET vs Q_OBJECT

2017-04-14 Thread Shawn Rutledge
You got an answer on StackOverflow already, but to repeat: he’s right, a 
QObject is always passed from C++ to QML by pointer, and a Q_GADGET is always 
passed by value.  That means Q_GADGET is only suitable for smallish 
self-contained classes, because it will always be copied.

> On 13 Apr 2017, at 20:31, Russell, Matthew  wrote:
> 
> Why can my Q_GADGET be read perfectly in QML (JS) but not my Q_OBJECT?
>  
> I created a class, registered it (Q_DECLARE_METATYPE), and then push 
> instances of it into a QVariantMap.  If the object is a Q_GADGET my JS can 
> read it perfectly, but when I switch it to a Q_OBJECT, the objects are blank.
>  
> I placed some code examples on SO here: 
> http://stackoverflow.com/questions/43398740/qml-can-see-my-q-gadget-but-not-q-object
>  
> Basically I’ve narrowed it down to Q_GADGET vs Q_OBJECT, nothing else seems 
> to make any difference.  I’d prefer to use Q_OBJECT so that I can use signals 
> and other objects in the QML/JS can bind to them.
>  
> Thanks.
> ___
> 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] Getting a QImage from an QML Image, protocol, , agnostic QImage?

2017-04-14 Thread Roland Hughes
And some 12 year old kid will do a Web search, find the interest archive 
messages then do exactly that. Once they release their app into the wild 
they will be in all kinds of legal trouble. That is why I chimed in. 
These posts live forever at various places on the Internet. From a 
technical perspective it is very easy to fetch an image, write it to a 
local file, then load it for display. Legally, not-so-much.



On 04/13/2017 03:16 AM, interest-requ...@qt-project.org wrote:

fetch or what the purpose of doing so is. They may be images he or
colleagues/partners etc have made available specifically for this
purpose. I responded to a technical query.

Sean


--
Roland Hughes, President
Logikal Solutions
(630)-205-1593

http://www.theminimumyouneedtoknow.com
http://www.infiniteexposure.net
http://www.johnsmith-book.com
http://www.logikalblog.com
http://www.interestingauthors.com/blog
http://lesedi.us/

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


Re: [Interest] Qt 5.9 Beta

2017-04-14 Thread Igor Mironchik



14.04.2017 13:33, Igor Mironchik пишет:


Hi,

I tried to check with no qmake in the PATH.

And in this case I have two errors:

D:\Qt\5.9\msvc2015\mkspecs\features\toolchain.prf:129: error: Variable 
QMAKE_CXX.COMPILER_MACROS is not defined.


:-1: error: msvc-version.conf loaded but QMAKE_MSC_VER isn't set

I'm using QtCreator and it should do the job even without qmake in the 
path. And this issue is only in Qt 5.9 Beta version.




And one more... When I have no qmake in the PATH generates only 
.qmake.stash with:


QMAKE_CXX.INCDIRS = \
"c:\\Program Files (x86)\\Microsoft Visual Studio 
14.0\\VC\\include\\" \

"c:\\Program Files (x86)\\Windows Kits\\8.1\\Include\\shared\\" \
"c:\\Program Files (x86)\\Windows Kits\\8.1\\Include\\um\\" \
"c:\\Program Files (x86)\\Windows Kits\\8.1\\Include\\winrt\\" \
d:\\3rdparty\\opencv\\build\\include\\
QMAKE_CXX.LIBDIRS = \
"c:\\Program Files (x86)\\Microsoft Visual Studio 14.0\\VC\\lib\\" \
"c:\\Program Files (x86)\\Windows Kits\\8.1\\Lib\\winv6.3\\um\\x86\\" \
d:\\3rdparty\\opencv\\build\\x86\\vc12\\lib\\

And if delete .qmake.stash and re-run qmake then following error:

D:\Qt\5.9\msvc2015\mkspecs\features\toolchain.prf:129: error: Variable 
QMAKE_CXX.COMPILER_MACROS is not defined.




14.04.2017 13:13, Igor Mironchik пишет:




14.04.2017 13:12, Igor Mironchik пишет:




14.04.2017 13:03, Igor Mironchik пишет:


Hi,

I have to add that after qmake processed my project in the build 
dir I can see the .qmake.stash file with following content:


QMAKE_CXX.INCDIRS = \
"C:\\Program Files (x86)\\Microsoft Visual Studio 
14.0\\VC\\INCLUDE" \
"C:\\Program Files (x86)\\Microsoft Visual Studio 
14.0\\VC\\ATLMFC\\INCLUDE" \
"C:\\Program Files (x86)\\Windows 
Kits\\10\\include\\10.0.14393.0\\ucrt" \
"C:\\Program Files (x86)\\Windows 
Kits\\NETFXSDK\\4.6.1\\include\\um" \
"C:\\Program Files (x86)\\Windows 
Kits\\10\\include\\10.0.14393.0\\shared" \
"C:\\Program Files (x86)\\Windows 
Kits\\10\\include\\10.0.14393.0\\um" \
"C:\\Program Files (x86)\\Windows 
Kits\\10\\include\\10.0.14393.0\\winrt" \
"c:\\Program Files (x86)\\Microsoft Visual Studio 
14.0\\VC\\include\\" \

"c:\\Program Files (x86)\\Windows Kits\\8.1\\Include\\shared\\" \
"c:\\Program Files (x86)\\Windows Kits\\8.1\\Include\\um\\" \
"c:\\Program Files (x86)\\Windows Kits\\8.1\\Include\\winrt\\" \
d:\\3rdparty\\opencv\\build\\include\\
QMAKE_CXX.LIBDIRS = \
"C:\\Program Files (x86)\\Microsoft Visual Studio 14.0\\VC\\LIB" \
"C:\\Program Files (x86)\\Microsoft Visual Studio 
14.0\\VC\\ATLMFC\\LIB" \
"C:\\Program Files (x86)\\Windows 
Kits\\10\\lib\\10.0.14393.0\\ucrt\\x86" \
"C:\\Program Files (x86)\\Windows 
Kits\\NETFXSDK\\4.6.1\\lib\\um\\x86" \
"C:\\Program Files (x86)\\Windows 
Kits\\10\\lib\\10.0.14393.0\\um\\x86" \
"c:\\Program Files (x86)\\Microsoft Visual Studio 
14.0\\VC\\lib\\" \
"c:\\Program Files (x86)\\Windows 
Kits\\8.1\\Lib\\winv6.3\\um\\x86\\" \

d:\\3rdparty\\opencv\\build\\x86\\vc12\\lib\\
QMAKE_CXX.QMAKE_MSC_VER = 1900
QMAKE_CXX.QMAKE_MSC_FULL_VER = 190024215
QMAKE_CXX.COMPILER_MACROS = \
QMAKE_MSC_VER \
QMAKE_MSC_FULL_VER

But with Qt 5.9 Beta this file will not be generated until I won't 
do the workaround.




Sorry, file generates. But build failed with

:-1: error: msvc-version.conf loaded but QMAKE_MSC_VER isn't set


And deleteing of build dir doesn't help...




Is it a bug? Or something missed in Qt installation?


14.04.2017 10:30, Igor Mironchik пишет:


Hi,


14.04.2017 10:22, Thiago Macieira пишет:

Em quinta-feira, 13 de abril de 2017, às 21:32:26 PDT, Igor Mironchik
escreveu:

Hello,

Qt 5.9 official binaries requires QMAKE_MSC_VER on project load.

Is it normal? Should I specify QMAKE_MSC_VER by hands?

Delete all your Makefiles and .qmake.* files in your build dir. In fact, delete
your build dir and run qmake again.


I'm sorry, probably I was not clear. I installed Qt 5.9 Beta with 
Online Installer. Launch QtCreator with one project and configure 
build to work with Qt 5.9. On qmake stage QtCreator said:


Running Windows Runtime device detection.

No winrtrunner.exe found.

Project ERROR: msvc-version.conf loaded but QMAKE_MSC_VER isn't set


I don't build Qt 5.9 my own, I use ready binaries.


To workaround it I modified 
Qt\5.9\msvc2015\mkspecs\common\msvc-version.conf and added on the top:



QMAKE_MSC_VER = 1900


I guess that this is problem of the installation of Qt 5.9.


Is it so?











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


Re: [Interest] Qt 5.9 Beta

2017-04-14 Thread Igor Mironchik

Hi,

I tried to check with no qmake in the PATH.

And in this case I have two errors:

D:\Qt\5.9\msvc2015\mkspecs\features\toolchain.prf:129: error: Variable 
QMAKE_CXX.COMPILER_MACROS is not defined.


:-1: error: msvc-version.conf loaded but QMAKE_MSC_VER isn't set

I'm using QtCreator and it should do the job even without qmake in the 
path. And this issue is only in Qt 5.9 Beta version.



14.04.2017 13:13, Igor Mironchik пишет:




14.04.2017 13:12, Igor Mironchik пишет:




14.04.2017 13:03, Igor Mironchik пишет:


Hi,

I have to add that after qmake processed my project in the build dir 
I can see the .qmake.stash file with following content:


QMAKE_CXX.INCDIRS = \
"C:\\Program Files (x86)\\Microsoft Visual Studio 
14.0\\VC\\INCLUDE" \
"C:\\Program Files (x86)\\Microsoft Visual Studio 
14.0\\VC\\ATLMFC\\INCLUDE" \
"C:\\Program Files (x86)\\Windows 
Kits\\10\\include\\10.0.14393.0\\ucrt" \
"C:\\Program Files (x86)\\Windows 
Kits\\NETFXSDK\\4.6.1\\include\\um" \
"C:\\Program Files (x86)\\Windows 
Kits\\10\\include\\10.0.14393.0\\shared" \
"C:\\Program Files (x86)\\Windows 
Kits\\10\\include\\10.0.14393.0\\um" \
"C:\\Program Files (x86)\\Windows 
Kits\\10\\include\\10.0.14393.0\\winrt" \
"c:\\Program Files (x86)\\Microsoft Visual Studio 
14.0\\VC\\include\\" \

"c:\\Program Files (x86)\\Windows Kits\\8.1\\Include\\shared\\" \
"c:\\Program Files (x86)\\Windows Kits\\8.1\\Include\\um\\" \
"c:\\Program Files (x86)\\Windows Kits\\8.1\\Include\\winrt\\" \
d:\\3rdparty\\opencv\\build\\include\\
QMAKE_CXX.LIBDIRS = \
"C:\\Program Files (x86)\\Microsoft Visual Studio 14.0\\VC\\LIB" \
"C:\\Program Files (x86)\\Microsoft Visual Studio 
14.0\\VC\\ATLMFC\\LIB" \
"C:\\Program Files (x86)\\Windows 
Kits\\10\\lib\\10.0.14393.0\\ucrt\\x86" \
"C:\\Program Files (x86)\\Windows 
Kits\\NETFXSDK\\4.6.1\\lib\\um\\x86" \
"C:\\Program Files (x86)\\Windows 
Kits\\10\\lib\\10.0.14393.0\\um\\x86" \

"c:\\Program Files (x86)\\Microsoft Visual Studio 14.0\\VC\\lib\\" \
"c:\\Program Files (x86)\\Windows 
Kits\\8.1\\Lib\\winv6.3\\um\\x86\\" \

d:\\3rdparty\\opencv\\build\\x86\\vc12\\lib\\
QMAKE_CXX.QMAKE_MSC_VER = 1900
QMAKE_CXX.QMAKE_MSC_FULL_VER = 190024215
QMAKE_CXX.COMPILER_MACROS = \
QMAKE_MSC_VER \
QMAKE_MSC_FULL_VER

But with Qt 5.9 Beta this file will not be generated until I won't 
do the workaround.




Sorry, file generates. But build failed with

:-1: error: msvc-version.conf loaded but QMAKE_MSC_VER isn't set


And deleteing of build dir doesn't help...




Is it a bug? Or something missed in Qt installation?


14.04.2017 10:30, Igor Mironchik пишет:


Hi,


14.04.2017 10:22, Thiago Macieira пишет:

Em quinta-feira, 13 de abril de 2017, às 21:32:26 PDT, Igor Mironchik
escreveu:

Hello,

Qt 5.9 official binaries requires QMAKE_MSC_VER on project load.

Is it normal? Should I specify QMAKE_MSC_VER by hands?

Delete all your Makefiles and .qmake.* files in your build dir. In fact, delete
your build dir and run qmake again.


I'm sorry, probably I was not clear. I installed Qt 5.9 Beta with 
Online Installer. Launch QtCreator with one project and configure 
build to work with Qt 5.9. On qmake stage QtCreator said:


Running Windows Runtime device detection.

No winrtrunner.exe found.

Project ERROR: msvc-version.conf loaded but QMAKE_MSC_VER isn't set


I don't build Qt 5.9 my own, I use ready binaries.


To workaround it I modified 
Qt\5.9\msvc2015\mkspecs\common\msvc-version.conf and added on the top:



QMAKE_MSC_VER = 1900


I guess that this is problem of the installation of Qt 5.9.


Is it so?









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


Re: [Interest] Qt 5.9 Beta

2017-04-14 Thread Igor Mironchik



14.04.2017 13:12, Igor Mironchik пишет:




14.04.2017 13:03, Igor Mironchik пишет:


Hi,

I have to add that after qmake processed my project in the build dir 
I can see the .qmake.stash file with following content:


QMAKE_CXX.INCDIRS = \
"C:\\Program Files (x86)\\Microsoft Visual Studio 
14.0\\VC\\INCLUDE" \
"C:\\Program Files (x86)\\Microsoft Visual Studio 
14.0\\VC\\ATLMFC\\INCLUDE" \
"C:\\Program Files (x86)\\Windows 
Kits\\10\\include\\10.0.14393.0\\ucrt" \
"C:\\Program Files (x86)\\Windows 
Kits\\NETFXSDK\\4.6.1\\include\\um" \
"C:\\Program Files (x86)\\Windows 
Kits\\10\\include\\10.0.14393.0\\shared" \
"C:\\Program Files (x86)\\Windows 
Kits\\10\\include\\10.0.14393.0\\um" \
"C:\\Program Files (x86)\\Windows 
Kits\\10\\include\\10.0.14393.0\\winrt" \
"c:\\Program Files (x86)\\Microsoft Visual Studio 
14.0\\VC\\include\\" \

"c:\\Program Files (x86)\\Windows Kits\\8.1\\Include\\shared\\" \
"c:\\Program Files (x86)\\Windows Kits\\8.1\\Include\\um\\" \
"c:\\Program Files (x86)\\Windows Kits\\8.1\\Include\\winrt\\" \
d:\\3rdparty\\opencv\\build\\include\\
QMAKE_CXX.LIBDIRS = \
"C:\\Program Files (x86)\\Microsoft Visual Studio 14.0\\VC\\LIB" \
"C:\\Program Files (x86)\\Microsoft Visual Studio 
14.0\\VC\\ATLMFC\\LIB" \
"C:\\Program Files (x86)\\Windows 
Kits\\10\\lib\\10.0.14393.0\\ucrt\\x86" \
"C:\\Program Files (x86)\\Windows 
Kits\\NETFXSDK\\4.6.1\\lib\\um\\x86" \
"C:\\Program Files (x86)\\Windows 
Kits\\10\\lib\\10.0.14393.0\\um\\x86" \

"c:\\Program Files (x86)\\Microsoft Visual Studio 14.0\\VC\\lib\\" \
"c:\\Program Files (x86)\\Windows 
Kits\\8.1\\Lib\\winv6.3\\um\\x86\\" \

d:\\3rdparty\\opencv\\build\\x86\\vc12\\lib\\
QMAKE_CXX.QMAKE_MSC_VER = 1900
QMAKE_CXX.QMAKE_MSC_FULL_VER = 190024215
QMAKE_CXX.COMPILER_MACROS = \
QMAKE_MSC_VER \
QMAKE_MSC_FULL_VER

But with Qt 5.9 Beta this file will not be generated until I won't do 
the workaround.




Sorry, file generates. But build failed with

:-1: error: msvc-version.conf loaded but QMAKE_MSC_VER isn't set


And deleteing of build dir doesn't help...




Is it a bug? Or something missed in Qt installation?


14.04.2017 10:30, Igor Mironchik пишет:


Hi,


14.04.2017 10:22, Thiago Macieira пишет:

Em quinta-feira, 13 de abril de 2017, às 21:32:26 PDT, Igor Mironchik
escreveu:

Hello,

Qt 5.9 official binaries requires QMAKE_MSC_VER on project load.

Is it normal? Should I specify QMAKE_MSC_VER by hands?

Delete all your Makefiles and .qmake.* files in your build dir. In fact, delete
your build dir and run qmake again.


I'm sorry, probably I was not clear. I installed Qt 5.9 Beta with 
Online Installer. Launch QtCreator with one project and configure 
build to work with Qt 5.9. On qmake stage QtCreator said:


Running Windows Runtime device detection.

No winrtrunner.exe found.

Project ERROR: msvc-version.conf loaded but QMAKE_MSC_VER isn't set


I don't build Qt 5.9 my own, I use ready binaries.


To workaround it I modified 
Qt\5.9\msvc2015\mkspecs\common\msvc-version.conf and added on the top:



QMAKE_MSC_VER = 1900


I guess that this is problem of the installation of Qt 5.9.


Is it so?







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


Re: [Interest] Qt 5.9 Beta

2017-04-14 Thread Igor Mironchik



14.04.2017 13:03, Igor Mironchik пишет:


Hi,

I have to add that after qmake processed my project in the build dir I 
can see the .qmake.stash file with following content:


QMAKE_CXX.INCDIRS = \
"C:\\Program Files (x86)\\Microsoft Visual Studio 14.0\\VC\\INCLUDE" \
"C:\\Program Files (x86)\\Microsoft Visual Studio 
14.0\\VC\\ATLMFC\\INCLUDE" \
"C:\\Program Files (x86)\\Windows 
Kits\\10\\include\\10.0.14393.0\\ucrt" \
"C:\\Program Files (x86)\\Windows 
Kits\\NETFXSDK\\4.6.1\\include\\um" \
"C:\\Program Files (x86)\\Windows 
Kits\\10\\include\\10.0.14393.0\\shared" \
"C:\\Program Files (x86)\\Windows 
Kits\\10\\include\\10.0.14393.0\\um" \
"C:\\Program Files (x86)\\Windows 
Kits\\10\\include\\10.0.14393.0\\winrt" \
"c:\\Program Files (x86)\\Microsoft Visual Studio 
14.0\\VC\\include\\" \

"c:\\Program Files (x86)\\Windows Kits\\8.1\\Include\\shared\\" \
"c:\\Program Files (x86)\\Windows Kits\\8.1\\Include\\um\\" \
"c:\\Program Files (x86)\\Windows Kits\\8.1\\Include\\winrt\\" \
d:\\3rdparty\\opencv\\build\\include\\
QMAKE_CXX.LIBDIRS = \
"C:\\Program Files (x86)\\Microsoft Visual Studio 14.0\\VC\\LIB" \
"C:\\Program Files (x86)\\Microsoft Visual Studio 
14.0\\VC\\ATLMFC\\LIB" \
"C:\\Program Files (x86)\\Windows 
Kits\\10\\lib\\10.0.14393.0\\ucrt\\x86" \
"C:\\Program Files (x86)\\Windows 
Kits\\NETFXSDK\\4.6.1\\lib\\um\\x86" \
"C:\\Program Files (x86)\\Windows 
Kits\\10\\lib\\10.0.14393.0\\um\\x86" \

"c:\\Program Files (x86)\\Microsoft Visual Studio 14.0\\VC\\lib\\" \
"c:\\Program Files (x86)\\Windows 
Kits\\8.1\\Lib\\winv6.3\\um\\x86\\" \

d:\\3rdparty\\opencv\\build\\x86\\vc12\\lib\\
QMAKE_CXX.QMAKE_MSC_VER = 1900
QMAKE_CXX.QMAKE_MSC_FULL_VER = 190024215
QMAKE_CXX.COMPILER_MACROS = \
QMAKE_MSC_VER \
QMAKE_MSC_FULL_VER

But with Qt 5.9 Beta this file will not be generated until I won't do 
the workaround.




Sorry, file generates. But build failed with

:-1: error: msvc-version.conf loaded but QMAKE_MSC_VER isn't set


Is it a bug? Or something missed in Qt installation?


14.04.2017 10:30, Igor Mironchik пишет:


Hi,


14.04.2017 10:22, Thiago Macieira пишет:

Em quinta-feira, 13 de abril de 2017, às 21:32:26 PDT, Igor Mironchik
escreveu:

Hello,

Qt 5.9 official binaries requires QMAKE_MSC_VER on project load.

Is it normal? Should I specify QMAKE_MSC_VER by hands?

Delete all your Makefiles and .qmake.* files in your build dir. In fact, delete
your build dir and run qmake again.


I'm sorry, probably I was not clear. I installed Qt 5.9 Beta with 
Online Installer. Launch QtCreator with one project and configure 
build to work with Qt 5.9. On qmake stage QtCreator said:


Running Windows Runtime device detection.

No winrtrunner.exe found.

Project ERROR: msvc-version.conf loaded but QMAKE_MSC_VER isn't set


I don't build Qt 5.9 my own, I use ready binaries.


To workaround it I modified 
Qt\5.9\msvc2015\mkspecs\common\msvc-version.conf and added on the top:



QMAKE_MSC_VER = 1900


I guess that this is problem of the installation of Qt 5.9.


Is it so?





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


Re: [Interest] Qt 5.9 Beta

2017-04-14 Thread Igor Mironchik

Hi,

I have to add that after qmake processed my project in the build dir I 
can see the .qmake.stash file with following content:


QMAKE_CXX.INCDIRS = \
"C:\\Program Files (x86)\\Microsoft Visual Studio 14.0\\VC\\INCLUDE" \
"C:\\Program Files (x86)\\Microsoft Visual Studio 
14.0\\VC\\ATLMFC\\INCLUDE" \
"C:\\Program Files (x86)\\Windows 
Kits\\10\\include\\10.0.14393.0\\ucrt" \

"C:\\Program Files (x86)\\Windows Kits\\NETFXSDK\\4.6.1\\include\\um" \
"C:\\Program Files (x86)\\Windows 
Kits\\10\\include\\10.0.14393.0\\shared" \
"C:\\Program Files (x86)\\Windows 
Kits\\10\\include\\10.0.14393.0\\um" \
"C:\\Program Files (x86)\\Windows 
Kits\\10\\include\\10.0.14393.0\\winrt" \
"c:\\Program Files (x86)\\Microsoft Visual Studio 
14.0\\VC\\include\\" \

"c:\\Program Files (x86)\\Windows Kits\\8.1\\Include\\shared\\" \
"c:\\Program Files (x86)\\Windows Kits\\8.1\\Include\\um\\" \
"c:\\Program Files (x86)\\Windows Kits\\8.1\\Include\\winrt\\" \
d:\\3rdparty\\opencv\\build\\include\\
QMAKE_CXX.LIBDIRS = \
"C:\\Program Files (x86)\\Microsoft Visual Studio 14.0\\VC\\LIB" \
"C:\\Program Files (x86)\\Microsoft Visual Studio 
14.0\\VC\\ATLMFC\\LIB" \
"C:\\Program Files (x86)\\Windows 
Kits\\10\\lib\\10.0.14393.0\\ucrt\\x86" \
"C:\\Program Files (x86)\\Windows 
Kits\\NETFXSDK\\4.6.1\\lib\\um\\x86" \
"C:\\Program Files (x86)\\Windows 
Kits\\10\\lib\\10.0.14393.0\\um\\x86" \

"c:\\Program Files (x86)\\Microsoft Visual Studio 14.0\\VC\\lib\\" \
"c:\\Program Files (x86)\\Windows Kits\\8.1\\Lib\\winv6.3\\um\\x86\\" \
d:\\3rdparty\\opencv\\build\\x86\\vc12\\lib\\
QMAKE_CXX.QMAKE_MSC_VER = 1900
QMAKE_CXX.QMAKE_MSC_FULL_VER = 190024215
QMAKE_CXX.COMPILER_MACROS = \
QMAKE_MSC_VER \
QMAKE_MSC_FULL_VER

But with Qt 5.9 Beta this file will not be generated until I won't do 
the workaround.


Is it a bug? Or something missed in Qt installation?


14.04.2017 10:30, Igor Mironchik пишет:


Hi,


14.04.2017 10:22, Thiago Macieira пишет:

Em quinta-feira, 13 de abril de 2017, às 21:32:26 PDT, Igor Mironchik
escreveu:

Hello,

Qt 5.9 official binaries requires QMAKE_MSC_VER on project load.

Is it normal? Should I specify QMAKE_MSC_VER by hands?

Delete all your Makefiles and .qmake.* files in your build dir. In fact, delete
your build dir and run qmake again.


I'm sorry, probably I was not clear. I installed Qt 5.9 Beta with 
Online Installer. Launch QtCreator with one project and configure 
build to work with Qt 5.9. On qmake stage QtCreator said:


Running Windows Runtime device detection.

No winrtrunner.exe found.

Project ERROR: msvc-version.conf loaded but QMAKE_MSC_VER isn't set


I don't build Qt 5.9 my own, I use ready binaries.


To workaround it I modified 
Qt\5.9\msvc2015\mkspecs\common\msvc-version.conf and added on the top:



QMAKE_MSC_VER = 1900


I guess that this is problem of the installation of Qt 5.9.


Is it so?



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


Re: [Interest] Qt 5.9 Beta

2017-04-14 Thread Igor Mironchik

Hi,


14.04.2017 10:22, Thiago Macieira пишет:

Em quinta-feira, 13 de abril de 2017, às 21:32:26 PDT, Igor Mironchik
escreveu:

Hello,

Qt 5.9 official binaries requires QMAKE_MSC_VER on project load.

Is it normal? Should I specify QMAKE_MSC_VER by hands?

Delete all your Makefiles and .qmake.* files in your build dir. In fact, delete
your build dir and run qmake again.


I'm sorry, probably I was not clear. I installed Qt 5.9 Beta with Online 
Installer. Launch QtCreator with one project and configure build to work 
with Qt 5.9. On qmake stage QtCreator said:


Running Windows Runtime device detection.

No winrtrunner.exe found.

Project ERROR: msvc-version.conf loaded but QMAKE_MSC_VER isn't set


I don't build Qt 5.9 my own, I use ready binaries.


To workaround it I modified 
Qt\5.9\msvc2015\mkspecs\common\msvc-version.conf and added on the top:



QMAKE_MSC_VER = 1900


I guess that this is problem of the installation of Qt 5.9.


Is it so?

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


Re: [Interest] Qt 5.9 Beta

2017-04-14 Thread Thiago Macieira
Em quinta-feira, 13 de abril de 2017, às 21:32:26 PDT, Igor Mironchik 
escreveu:
> Hello,
> 
> Qt 5.9 official binaries requires QMAKE_MSC_VER on project load.
> 
> Is it normal? Should I specify QMAKE_MSC_VER by hands?

Delete all your Makefiles and .qmake.* files in your build dir. In fact, delete 
your build dir and run qmake again.

-- 
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] Qt3D memory leaks

2017-04-14 Thread Igor Mironchik

Hi,

More data (in MB):

1. 136.1

2. 143.5 (+7.4)

3. 145.9 (+2.4)

4. 147.2 (+1.3)

5. 150.1 (+2.9)

6. 152.3 (+2.2)

7. 152.0 (-0.3)

8. 154.7 (+2.7)

I guess that small memory leaks still exist.

P.S. 5 years tree has 341 branches and 512 leafs. All of them I delete 
on restart of tree (I checked it).


14.04.2017 8:13, Igor Mironchik пишет:

Hi,


13.04.2017 22:20, Igor Mironchik пишет:

Hi,

The entity takes ownership of any components that are parentless 
when added. This is done using the usual QObject ownership mechanism 
so the components will be deleted by the entity when it is being 
destroyed just like any other QObject parent. There may be a leaks 
elsewhere but I don't think this is it. There were some leaks 
related to VAOs fixed around the time of the 5.8.0 release. I can't 
recall if they made it into 5.8.0 or not off the top of my head. 
Please try with a build from the 5.9 branch in git.


I will try to build Qt 5.9 and check 3Dtree with it.

And sorry guys for the noise... :)


I checked with Qt 5.9 Beta. The situation is much more better.

First tree - 132,9 MB.

Second tree - 141,5 MB.

Third tree - 144,1 MB.

Now probably there are no memory leaks, maybe it's a fragmentation, 
but maybe there are still small leaks. I don't know.


Measurements done on Windows.



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