Re: [Interest] How to run a WinRT app on a Window 8 intel tablet?
I have installed the Window 8.1 SDK, restarted the computer and decided to build the release version only. Now it's failing like this. cd wbmp\ ( if not exist Makefile C:\Qt\5.4\Src\qtbase\bin\qmake C:\Qt\5.4\Src\qtimageformats\src\plugins\imageformats\wbmp\wbmp.pro -o Make file ) C:\Qt\5.4\jom.exe -f Makefile C:\Qt\5.4\jom.exe -f Makefile.Release cd imageformats\ ( if not exist Makefile C:\Qt\5.4\Src\qtbase\bin\qmake C:\Qt\5.4\Src\qtimageformats\src\imageformats\imageformats.pro -o M akefile ) C:\Qt\5.4\jom.exe -f Makefile C:\Qt\5.4\jom.exe -f Makefile.Release Error: dependent '..\..\include\QtXmlPatterns\5.4.1\QtXmlPatterns\private\qacceltree_p.h' does not exist. jom: C:\Qt\5.4\Src\qtxmlpatterns\src\xmlpatterns\Makefile [release] Error 2 jom: C:\Qt\5.4\Src\qtxmlpatterns\src\Makefile [sub-xmlpatterns-make_first] Error 2 jom: C:\Qt\5.4\Src\qtxmlpatterns\Makefile [sub-src-make_first] Error 2 jom: C:\Qt\5.4\Src\Makefile [module-qtxmlpatterns-make_first] Error 2 C:\Qt\5.4\Src It's not easy to build WinRT from source. Regards, Nuno On 08/06/2015 16:57, Andrew Knight wrote: On 08/06/15 17:50, Nuno Santos wrote: Still can't build WinRT x86 from source. Now it's failing here but can't understand why... link /NOLOGO /DYNAMICBASE /NXCOMPAT /NODEFAULTLIB:ole32.lib /APPCONTAINER /SAFESEH /MACHINE:X86 /DEBUG /MANIFEST:NO /DLL /SUBSYSTEM:WINDOWS /V ERSION:5.42 /OUT:..\..\..\..\plugins\imageformats\qwbmpd.dll @C:\Users\nsantos\AppData\Local\Temp\qwbmpd.dll.2080.922.jom Creating library ..\..\..\..\plugins\imageformats\qwbmpd.lib and object ..\..\..\..\plugins\imageformats\qwbmpd.exp cd imageformats\ ( if not exist Makefile C:\Qt\5.4\Src\qtbase\bin\qmake C:\Qt\5.4\Src\qtimageformats\src\imageformats\imageformats.pro -o M akefile ) C:\Qt\5.4\jom.exe -f Makefile C:\Qt\5.4\jom.exe -f Makefile.Debug jom: C:\Qt\5.4\Src\Makefile [module-qtxmlpatterns-make_first] Error 2 There are interleaved make commands here, so please use nmake to straighten out the output and find which project is failing. It looks like qtxmlpatterns is the one breaking the build, so go in there and run nmake to see if there's e.g. another symbol definition related issue. -Andrew ___ Interest mailing list Interest@qt-project.org http://lists.qt-project.org/mailman/listinfo/interest
[Interest] Qt nntp server?
Hi, I'm turning my mailing list overhead over to gmane and noticed that this ML isn't available there while the development ML is. In case that's no simple omission: what happened to nntp.trolltech.com and nntp.qt.nokia.com ? Is there still a Qt-specific nntp server that provides access to the various Qt mailing lists? Or can the interest ML be subscribed to gmane? Thanks, René ___ Interest mailing list Interest@qt-project.org http://lists.qt-project.org/mailman/listinfo/interest
Re: [Interest] Qt nntp server?
On Mon, Jun 8, 2015 at 11:04 PM, René J.V. rjvber...@gmail.com wrote: Hi, I'm turning my mailing list overhead over to gmane and noticed that this ML isn't available there while the development ML is. In case that's no simple omission: what happened to nntp.trolltech.com and nntp.qt.nokia.com ? Is there still a Qt-specific nntp server that provides access to the various Qt mailing lists? Both of those domains are dead :( Or can the interest ML be subscribed to gmane? It's there: nntp://news.gmane.org/gmane.comp.lib.qt.general HTH, -- Giuseppe D'Angelo ___ Interest mailing list Interest@qt-project.org http://lists.qt-project.org/mailman/listinfo/interest
Re: [Interest] Qt nntp server?
On Monday June 08 2015 23:14:33 Giuseppe D'Angelo wrote: Both of those domains are dead :( That much I noticed (nntp.trolltech.com still resolves though) ... Or can the interest ML be subscribed to gmane? It's there: nntp://news.gmane.org/gmane.comp.lib.qt.general I'd hoped to post something like yes, indeed through it, but I'm only getting messages from 2011 there?! But thanks. Maybe it just requires someone checking in to do an update. R. ___ Interest mailing list Interest@qt-project.org http://lists.qt-project.org/mailman/listinfo/interest
Re: [Interest] Qt 5.4.1 crashes on iOS 5.1
The Qt port in 5.1 is very initial - Instead, take the latest 5.4.2 I meant iOS 5.1, not Qt. the real support is starting from iOS-8 Then as I said, the QtCreator should create projects with compatibility set to iOS 8, because the default XCode settings for compatibility is iOS 5.1. And then, the apps get rejected in appStore because it crashes on the platform it says it's compatible with. (but I still think fixing the shoudAutorotate crash should be very easy, and even if not all Qt features work on 5.1, at least it wouldn't crash straight away, and allow developers to work with it) Stephane. On Tue, Jun 9, 2015 at 7:20 AM, Robert Iakobashvili corobe...@gmail.com wrote: On Tue, Jun 9, 2015 at 6:49 AM, Stephane Clavel steph...@virtualdj.com wrote: By default, Qt on iOS creates projects with 5.1.1 compatibility (which is the minimum version required to be compatible with iPad 1). However, the current Qt 5.4.1 crashes on iOS 5.1, with a [QIOSViewController shouldAutorotate]: unrecognized selector sent to instance error. (reproduced with unmodified examples from the QtCreator example list) As such, applications can get rejected from AppStore. So you should either: 1 - change QtCreator to generate XCode projects with compatibility set to iOS6 or 2 - fix the crash so that Qt applications can run on iOS 5.1 (obviously, solution 2 would be better, since it would allow people to create applications that run on iPad 1) Thank you, __ Stephane The Qt port in 5.1 is very initial - don't even try to work with it. Instead, take the latest 5.4.2 Whatever the declared support in the docs is, the real support is starting from iOS-8 since Qt-team as per my knowledge seen in bug reports has only iOS-8 in their labs and not even iOS-7. Many iPads, though, have iOS-7. Qt still works with iOS-7 at least with widgets, but test thoroughly. You will miss iPad-1 with Qt-5.4.2, but this is a really small market. Note, that iPad-2, two difference HW-editions, has only 512 MB of RAM, and it is a good case to test the memory efficiency of your app. Regards, Robert ___ Interest mailing list Interest@qt-project.org http://lists.qt-project.org/mailman/listinfo/interest
Re: [Interest] Qt 5.4.1 crashes on iOS 5.1
On Tue, Jun 9, 2015 at 7:26 AM, Stephane Clavel steph...@virtualdj.com wrote: The Qt port in 5.1 is very initial - Instead, take the latest 5.4.2 I meant iOS 5.1, not Qt. the real support is starting from iOS-8 Then as I said, the QtCreator should create projects with compatibility set to iOS 8, because the default XCode settings for compatibility is iOS 5.1. And then, the apps get rejected in appStore because it crashes on the platform it says it's compatible with. (but I still think fixing the shoudAutorotate crash should be very easy, and even if not all Qt features work on 5.1, at least it wouldn't crash straight away, and allow developers to work with it) Stephane. Try to open bug reports, but I'd doubt Qt-team will be fixing it. Regards, Robert ___ Interest mailing list Interest@qt-project.org http://lists.qt-project.org/mailman/listinfo/interest
[Interest] Qt 5.4.1 crashes on iOS 5.1
By default, Qt on iOS creates projects with 5.1.1 compatibility (which is the minimum version required to be compatible with iPad 1). However, the current Qt 5.4.1 crashes on iOS 5.1, with a [QIOSViewController shouldAutorotate]: unrecognized selector sent to instance error. (reproduced with unmodified examples from the QtCreator example list) As such, applications can get rejected from AppStore. So you should either: 1 - change QtCreator to generate XCode projects with compatibility set to iOS6 or 2 - fix the crash so that Qt applications can run on iOS 5.1 (obviously, solution 2 would be better, since it would allow people to create applications that run on iPad 1) Thank you, __ Stephane ___ Interest mailing list Interest@qt-project.org http://lists.qt-project.org/mailman/listinfo/interest
Re: [Interest] Qt 5.4.1 crashes on iOS 5.1
On Tue, Jun 9, 2015 at 6:49 AM, Stephane Clavel steph...@virtualdj.com wrote: By default, Qt on iOS creates projects with 5.1.1 compatibility (which is the minimum version required to be compatible with iPad 1). However, the current Qt 5.4.1 crashes on iOS 5.1, with a [QIOSViewController shouldAutorotate]: unrecognized selector sent to instance error. (reproduced with unmodified examples from the QtCreator example list) As such, applications can get rejected from AppStore. So you should either: 1 - change QtCreator to generate XCode projects with compatibility set to iOS6 or 2 - fix the crash so that Qt applications can run on iOS 5.1 (obviously, solution 2 would be better, since it would allow people to create applications that run on iPad 1) Thank you, __ Stephane The Qt port in 5.1 is very initial - don't even try to work with it. Instead, take the latest 5.4.2 Whatever the declared support in the docs is, the real support is starting from iOS-8 since Qt-team as per my knowledge seen in bug reports has only iOS-8 in their labs and not even iOS-7. Many iPads, though, have iOS-7. Qt still works with iOS-7 at least with widgets, but test thoroughly. You will miss iPad-1 with Qt-5.4.2, but this is a really small market. Note, that iPad-2, two difference HW-editions, has only 512 MB of RAM, and it is a good case to test the memory efficiency of your app. Regards, Robert ___ Interest mailing list Interest@qt-project.org http://lists.qt-project.org/mailman/listinfo/interest
[Interest] NSView inside Carbon Window
Hi, Does anyone know if it is possible to create an NSView inside a Carbon Window on Mac OSX? I'm trying to instantiate a QWindow inside a Carbon WindowRef, but QWindow fromWid method needs a NSView to be passed by parameter and not a WindowRef. I have seen been saying that it is not possible to have a NSView inside a CarbonWindow. Maybe someone more experienced in Mac OSX architecture could confirm me this. Thanks in advance, Regards, Nuno ___ Interest mailing list Interest@qt-project.org http://lists.qt-project.org/mailman/listinfo/interest
Re: [Interest] QML and OpenGL conflicts
In case we want to share our context with QtQuick, which one should we pick? Is there a main context Qt uses for its views (not only QtQuick because classic widgets use OpenGL too I guess)? Or do we have to share QtQuickView contextes as they are created? 2015-06-05 20:31 GMT+02:00 Marc Gilleron marc.gille...@gmail.com: Here is where we currently are: - Threading our OpenGL code would currently mean having a thread between our project and Qt-related code. - Wrapping OpenGL code in makeCurrent() is not done and is not planned by the team due to optimizations and refactoring that never has been necessary. I agree it might sound not very clever, but that's the way it is now. - Share the context with Qt Quick might be an option, to be tested because there is a chance it doesn't works as you said. However we still think about threading so that both renderers don't slow each other. We recently had a test case where the two renderers worked, however performance dropped dramatically, not sure why. - Note: it's not all about render(), but also ressources loading that may happen at almost anytime within the main thread. Another tricky point for the approach is the complexity of our project and the way we had to integrate Qt in it. At the moment, the GUI/QML interacts directly with the main thread, where our renderer is also doing its operations at different places (far away). So, maybe we'll have to separate those threads... but if we do, I wonder at which level, and how windowing will work since our renderer has its own window. 2015-06-05 19:09 GMT+02:00 Sean Harmer sean.har...@kdab.com: On 04/06/2015 14:25, Marc Gilleron wrote: I tried to set QSG_RENDER_LOOP to threaded but didn't noticed any difference, our application still crashes. Then you need to isolate why it crashes and choose a method to fix it. Some options: * Put your custom rendering into another thread and integrate it into Qt Quick's scene using QQuickFramebufferObject as Kai suggested. * Have your application drive when Qt Quick performs it's rendering by using QQuickRenderControl. * Debug your code to ensure that your rendering code calls makeCurrent() on it's own context whenever it needs to do some GL calls. Apitrace, vogl or similar can help here. * Share the context with Qt Quick so that there is only one context that is always current. This may or may not be possible depending upon the GL requirements of your renderer. Qt Quick is not doing anything naughty here. It's just typical integration of 2 renderers situation where your renderer is making the assumption that no other context will ever be made current. That assumption is being broken by introducing Qt Quick into the picture. Cheers, Sean -- Dr Sean Harmer | sean.har...@kdab.com | Managing Director UK Klarälvdalens Datakonsult AB, a KDAB Group company Tel. Sweden (HQ) +46-563-540090, USA +1-866-777-KDAB(5322) KDAB - Qt Experts - Platform-independent software solutions ___ 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] Any good (e)books yet on QML?
Hello, http://qmlbook.github.io/ Thank you! -- Alfredo Palhares GPG/PGP Key Fingerprint 68FC B06A 6C22 8B9B F110 38D6 E8F7 4D1F 0763 CAAD ___ Interest mailing list Interest@qt-project.org http://lists.qt-project.org/mailman/listinfo/interest
Re: [Interest] How to run a WinRT app on a Window 8 intel tablet?
Andrew, Yeah! How could I not remeber that! :) Thanks, Nuno On 08/06/2015 11:25, Andrew Knight wrote: Hi Nuno, On 08/06/15 13:05, Nuno Santos wrote: Oliver, Is Qt for WinRT only available for x64 arch? In terms of pre-built releases, yes. The test tablet I got is x64 but it has a 32bit windows installed on it. Is there any way of work around this? Build Qt yourself with the winrt-x86-msvc2013 mkspec. Regards, Nuno On 04/06/2015 12:37, Oliver Wolff wrote: Hi, I am afraid that deployment to a device from Creator only works for Windows Phone but not for Windows Tablets. For Tablets you have to package/deploy everything manually using windeployqt for example. The other option (that I would tend to avoid) would be building on your tablet (if it has an x86 CPU). Another option would be to use Visual Studio. There it should be possible to select your tablet and deploy the application you created (for example by calling qmake -tp vc CONFIG+=windeployqt). Some more information can be found on http://doc.qt.io/qt-5/winrt-support.html#package-content but the content here is partially outdated and being updated at the moment. The D3D shader service for example is no longer needed. BR, Olli On 6/4/2015 12:57, Nuno Santos wrote: Hi, I'm doing my first experiments with WinRT. I have a Dell Window 8 tablet and i'm trying to run a QtQuick Hello World program on it. I was able to start the app on the computer but not on the tablet. I thought there was a mechanism like iOS and Android, in which I could select the device. Is there any guide line on how to proceed? Regards, Nuno ___ 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 mailing list Interest@qt-project.org http://lists.qt-project.org/mailman/listinfo/interest
Re: [Interest] How to run a WinRT app on a Window 8 intel tablet?
Andrew, Yeah! I could I not remember that! :) Thanks! Regards, Nuno On 08/06/2015 11:25, Andrew Knight wrote: Hi Nuno, On 08/06/15 13:05, Nuno Santos wrote: Oliver, Is Qt for WinRT only available for x64 arch? In terms of pre-built releases, yes. The test tablet I got is x64 but it has a 32bit windows installed on it. Is there any way of work around this? Build Qt yourself with the winrt-x86-msvc2013 mkspec. Regards, Nuno On 04/06/2015 12:37, Oliver Wolff wrote: Hi, I am afraid that deployment to a device from Creator only works for Windows Phone but not for Windows Tablets. For Tablets you have to package/deploy everything manually using windeployqt for example. The other option (that I would tend to avoid) would be building on your tablet (if it has an x86 CPU). Another option would be to use Visual Studio. There it should be possible to select your tablet and deploy the application you created (for example by calling qmake -tp vc CONFIG+=windeployqt). Some more information can be found on http://doc.qt.io/qt-5/winrt-support.html#package-content but the content here is partially outdated and being updated at the moment. The D3D shader service for example is no longer needed. BR, Olli On 6/4/2015 12:57, Nuno Santos wrote: Hi, I'm doing my first experiments with WinRT. I have a Dell Window 8 tablet and i'm trying to run a QtQuick Hello World program on it. I was able to start the app on the computer but not on the tablet. I thought there was a mechanism like iOS and Android, in which I could select the device. Is there any guide line on how to proceed? Regards, Nuno ___ 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 mailing list Interest@qt-project.org http://lists.qt-project.org/mailman/listinfo/interest
Re: [Interest] NSView inside Carbon Window
On Monday June 08 2015 11:51:25 Nuno Santos wrote: NSWindow *nsw = [[NSWindow alloc] initWithWindowRef:(WindowRef*)ptr]; 2015-06-08 11:45:36.795 Live[65095:685104] A Carbon window's attributes couldn't be gotten. 2015-06-08 11:45:36.795 Live[65095:685104] A Carbon window's features couldn't be gotten. 2015-06-08 11:45:36.795 Live[65095:685104] Couldn't get window modality: error=-5600 % /usr/bin/macerror -5600 Mac OS error -5600 (errInvalidWindowRef): tried to pass a bad WindowRef argument Are you by chance passing a pointer to a WindowRef? Also, heed the advice at the bottom of this page: http://www.cocoabuilder.com/archive/cocoa/298219-initializing-nswindow-with-carbon-window.html . There is a CoreAudio mailing list on which you're likely to get better answers, if this has to do with AU. 2015-06-08 11:45:36.795 Live[65095:685104] frame - 0.00 0.00 0.00 0.00 I’m also not doing anything else with the Window. If I use it as a parent of QQuickView (approach that works on Windows), the host app crashes with the following: That's a crash in the video driver (with a weird backtrace suggesting it's in strlen() called from QCoreApplication::arguments(), or maybe it really is in that function). It's bad that it's so easy to provoke that, but it probably comes directly from the error above. The window you get isn't valid. R. Crashed Thread:0 Dispatch queue: com.apple.main-thread Exception Type:EXC_BAD_ACCESS (SIGSEGV) Exception Codes: KERN_INVALID_ADDRESS at 0x002b VM Regions Near 0x2b: MALLOC_LARGE (reserved 00012d20-0004231e6000 [ 11.8G] rw-/rwx SM=NUL reserved VM address space (unallocated) -- __TEXT 1234-123400509000 [ 5156K] r-x/rwx SM=COW /System/Library/Extensions/AppleIntelHD5000GraphicsGLDriver.bundle/Contents/MacOS/AppleIntelHD5000GraphicsGLDriver Thread 0 Crashed:: Dispatch queue: com.apple.main-thread 0 libsystem_c.dylib 0x7fff8a9ab152 strlen + 18 1 org.qt-project.QtCore 0x00011f4f6f27 QCoreApplication::arguments() + 199 2 org.qt-project.QtQuick0x00011e94bd76 0x11e8bc000 + 589174 3 org.qt-project.QtQuick0x00011e94c299 QSGContext::createWindowManager() + 9 4 org.qt-project.QtQuick0x00011e9614c7 QSGRenderLoop::instance() + 71 5 org.qt-project.QtQuick0x00011e992cc3 QQuickWindowPrivate::init(QQuickWindow*, QQuickRenderControl*) + 307 6 org.qt-project.QtQuick0x00011ea3e39d QQuickView::QQuickView(QWindow*) + 189 7 com.imaginando.Audiolab 0x00011dff1e1b IVstEditor::open(void*) + 107 (IVstEditor.cpp:34) Nuno Santos Founder / CEO / CTO www.imaginando.pt +351 91 621 69 62 On 08 Jun 2015, at 11:36, René J.V. Bertin rjvber...@gmail.com wrote: On Monday June 08 2015 09:24:56 Nuno Santos wrote: Hi Nuno: I'm trying to instantiate a QWindow inside a Carbon WindowRef, but QWindow fromWid method needs a NSView to be passed by parameter and not a WindowRef. I have seen been saying that it is not possible to have a NSView inside a CarbonWindow. Maybe someone more experienced in Mac OSX architecture could confirm me this. Try this: https://developer.apple.com/library/mac/documentation/Cocoa/Reference/ApplicationKit/Classes/NSWindow_Class/index.html#//apple_ref/occ/instm/NSWindow/initWithWindowRef: Then you send a contentView message to the NSWindow instance you got. Note that that gives you the window’s content view, the highest accessible NSView object in the window’s view hierarchy. If that's not the one you need, you'll have to figure out how to get the subviews (answer via google!) and pick the right one. R. ___ 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 to run a WinRT app on a Window 8 intel tablet?
Hi Nuno, On 08/06/15 13:05, Nuno Santos wrote: Oliver, Is Qt for WinRT only available for x64 arch? In terms of pre-built releases, yes. The test tablet I got is x64 but it has a 32bit windows installed on it. Is there any way of work around this? Build Qt yourself with the winrt-x86-msvc2013 mkspec. Regards, Nuno On 04/06/2015 12:37, Oliver Wolff wrote: Hi, I am afraid that deployment to a device from Creator only works for Windows Phone but not for Windows Tablets. For Tablets you have to package/deploy everything manually using windeployqt for example. The other option (that I would tend to avoid) would be building on your tablet (if it has an x86 CPU). Another option would be to use Visual Studio. There it should be possible to select your tablet and deploy the application you created (for example by calling qmake -tp vc CONFIG+=windeployqt). Some more information can be found on http://doc.qt.io/qt-5/winrt-support.html#package-content but the content here is partially outdated and being updated at the moment. The D3D shader service for example is no longer needed. BR, Olli On 6/4/2015 12:57, Nuno Santos wrote: Hi, I'm doing my first experiments with WinRT. I have a Dell Window 8 tablet and i'm trying to run a QtQuick Hello World program on it. I was able to start the app on the computer but not on the tablet. I thought there was a mechanism like iOS and Android, in which I could select the device. Is there any guide line on how to proceed? Regards, Nuno ___ 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 mailing list Interest@qt-project.org http://lists.qt-project.org/mailman/listinfo/interest
Re: [Interest] NSView inside Carbon Window
On Monday June 08 2015 09:24:56 Nuno Santos wrote: Hi Nuno: I'm trying to instantiate a QWindow inside a Carbon WindowRef, but QWindow fromWid method needs a NSView to be passed by parameter and not a WindowRef. I have seen been saying that it is not possible to have a NSView inside a CarbonWindow. Maybe someone more experienced in Mac OSX architecture could confirm me this. Try this: https://developer.apple.com/library/mac/documentation/Cocoa/Reference/ApplicationKit/Classes/NSWindow_Class/index.html#//apple_ref/occ/instm/NSWindow/initWithWindowRef: Then you send a contentView message to the NSWindow instance you got. Note that that gives you the window’s content view, the highest accessible NSView object in the window’s view hierarchy. If that's not the one you need, you'll have to figure out how to get the subviews (answer via google!) and pick the right one. R. ___ Interest mailing list Interest@qt-project.org http://lists.qt-project.org/mailman/listinfo/interest
Re: [Interest] How to run a WinRT app on a Window 8 intel tablet?
On Monday 08 June 2015 14:43:26 Nuno Santos wrote: kernel\qhostaddress.cpp(786) : error C2065: 'INADDR_BROADCAST' : undeclared identifier kernel\qhostaddress.cpp(789) : error C2065: 'INADDR_LOOPBACK' : undeclared identifier Check if they are defined in winsock2.h, as they should be. -- 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 to run a WinRT app on a Window 8 intel tablet?
Are you sure you are using a native command prompt meaning the one for compiling desktop applications? BR, Maurice -Original Message- From: interest-bounces+maurice.kalinowski=theqtcompany.com@qt- project.org [mailto:interest- bounces+maurice.kalinowski=theqtcompany@qt-project.org] On Behalf Of Nuno Santos Sent: Montag, 8. Juni 2015 15:33 To: Andrew Knight; interest@qt-project.org Subject: Re: [Interest] How to run a WinRT app on a Window 8 intel tablet? Andrew, I'm configure QT with this line: configure -prefix c:\qt\5.4\winrt_x86 -xplatform winrt-x64-msvc2013 -debug- and-release -nomake examples -nomake tests -skip webkit -skip multimedia How do you configure yours? I didn't had problems configuring it, but i'm having problems building it. kernel\qhostaddress.cpp(786) : error C2065: 'INADDR_BROADCAST' : undeclared identifier kernel\qhostaddress.cpp(789) : error C2065: 'INADDR_LOOPBACK' : undeclared identifier kernel\qhostaddress.cpp(795) : error C2065: 'INADDR_ANY' : undeclared identifier Regards, Nuno On 08/06/2015 11:25, Andrew Knight wrote: Hi Nuno, On 08/06/15 13:05, Nuno Santos wrote: Oliver, Is Qt for WinRT only available for x64 arch? In terms of pre-built releases, yes. The test tablet I got is x64 but it has a 32bit windows installed on it. Is there any way of work around this? Build Qt yourself with the winrt-x86-msvc2013 mkspec. Regards, Nuno On 04/06/2015 12:37, Oliver Wolff wrote: Hi, I am afraid that deployment to a device from Creator only works for Windows Phone but not for Windows Tablets. For Tablets you have to package/deploy everything manually using windeployqt for example. The other option (that I would tend to avoid) would be building on your tablet (if it has an x86 CPU). Another option would be to use Visual Studio. There it should be possible to select your tablet and deploy the application you created (for example by calling qmake -tp vc CONFIG+=windeployqt). Some more information can be found on http://doc.qt.io/qt-5/winrt-support.html#package-content but the content here is partially outdated and being updated at the moment. The D3D shader service for example is no longer needed. BR, Olli On 6/4/2015 12:57, Nuno Santos wrote: Hi, I'm doing my first experiments with WinRT. I have a Dell Window 8 tablet and i'm trying to run a QtQuick Hello World program on it. I was able to start the app on the computer but not on the tablet. I thought there was a mechanism like iOS and Android, in which I could select the device. Is there any guide line on how to proceed? Regards, Nuno ___ 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 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 to run a WinRT app on a Window 8 intel tablet?
When building Qt from source for desktop, I was using a Qt vars recommended on Qt documentation. With the following setup: REM Set up \Microsoft Visual Studio 2013, where arch is \c amd64, \c x86, etc. CALL C:\Program Files (x86)\Microsoft Visual Studio 12.0\VC\vcvarsall.bat x86 SET _ROOT=C:\Qt\5.4\Src SET PATH=%_ROOT%\qtbase\bin;%_ROOT%\gnuwin32\bin;C:\Python27;%PATH% REM Uncomment the below line when using a git checkout of the source repository REM SET PATH=%_ROOT%\qtrepotools\bin;%PATH% SET QMAKESPEC=win32-msvc2013 SET _ROOT= But if I use this to try building for WinRT, it says to me that there is not suitable compiler. So what I did was to execute cmd.exe and then call vcvarsall.bat inside Visual Studio 12.0\VC directory with x86 argument. Then I went to Qt source directory and called: configure -prefix c:\qt\5.4\winrt_x86 -xplatform winrt-x86-msvc2013 -debug-and-release -nomake examples -nomake tests -skip webkit -skip multimedia I have tried again and it's giving me errors on the same place: kernel\qhostaddress.cpp(786) : error C2065: 'INADDR_BROADCAST' : undeclared identifier kernel\qhostaddress.cpp(789) : error C2065: 'INADDR_LOOPBACK' : undeclared identifier Regards, Nuno On 08/06/2015 14:39, Kalinowski Maurice wrote: Are you sure you are using a native command prompt meaning the one for compiling desktop applications? BR, Maurice -Original Message- From: interest-bounces+maurice.kalinowski=theqtcompany.com@qt- project.org [mailto:interest- bounces+maurice.kalinowski=theqtcompany@qt-project.org] On Behalf Of Nuno Santos Sent: Montag, 8. Juni 2015 15:33 To: Andrew Knight; interest@qt-project.org Subject: Re: [Interest] How to run a WinRT app on a Window 8 intel tablet? Andrew, I'm configure QT with this line: configure -prefix c:\qt\5.4\winrt_x86 -xplatform winrt-x64-msvc2013 -debug- and-release -nomake examples -nomake tests -skip webkit -skip multimedia How do you configure yours? I didn't had problems configuring it, but i'm having problems building it. kernel\qhostaddress.cpp(786) : error C2065: 'INADDR_BROADCAST' : undeclared identifier kernel\qhostaddress.cpp(789) : error C2065: 'INADDR_LOOPBACK' : undeclared identifier kernel\qhostaddress.cpp(795) : error C2065: 'INADDR_ANY' : undeclared identifier Regards, Nuno On 08/06/2015 11:25, Andrew Knight wrote: Hi Nuno, On 08/06/15 13:05, Nuno Santos wrote: Oliver, Is Qt for WinRT only available for x64 arch? In terms of pre-built releases, yes. The test tablet I got is x64 but it has a 32bit windows installed on it. Is there any way of work around this? Build Qt yourself with the winrt-x86-msvc2013 mkspec. Regards, Nuno On 04/06/2015 12:37, Oliver Wolff wrote: Hi, I am afraid that deployment to a device from Creator only works for Windows Phone but not for Windows Tablets. For Tablets you have to package/deploy everything manually using windeployqt for example. The other option (that I would tend to avoid) would be building on your tablet (if it has an x86 CPU). Another option would be to use Visual Studio. There it should be possible to select your tablet and deploy the application you created (for example by calling qmake -tp vc CONFIG+=windeployqt). Some more information can be found on http://doc.qt.io/qt-5/winrt-support.html#package-content but the content here is partially outdated and being updated at the moment. The D3D shader service for example is no longer needed. BR, Olli On 6/4/2015 12:57, Nuno Santos wrote: Hi, I'm doing my first experiments with WinRT. I have a Dell Window 8 tablet and i'm trying to run a QtQuick Hello World program on it. I was able to start the app on the computer but not on the tablet. I thought there was a mechanism like iOS and Android, in which I could select the device. Is there any guide line on how to proceed? Regards, Nuno ___ 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 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] [QtBluetooth] Basic tests
-Original Message- project.org] On Behalf Of Blasche Alexander Sent: Monday, 8 June 2015 16:03 The above getDevice() function is related to Pairing and Bluez 4.x and involved in device discovery at all. Small correction (missing negation): The above getDevice() function is related to Pairing and Bluez 4.x and *NOT* involved in device discovery at all. -- Alex ___ Interest mailing list Interest@qt-project.org http://lists.qt-project.org/mailman/listinfo/interest
Re: [Interest] How to run a WinRT app on a Window 8 intel tablet?
Thiago, Nope, it was not defined... Had to define it. Did it like this on qhostaddress.h #define INADDR_ANY ((unsigned long int) 0x) #define INADDR_BROADCAST((unsigned long int) 0x) #define INADDR_LOOPBACK 0x7f01 /* 127.0.0.1 */ The winsock2.h that I edited was on: C:\Program Files (x86)\Windows Kits\8.1\include\um From config: Environment: INCLUDE= C:\Program Files (x86)\Microsoft Visual Studio 12.0\VC\INCLUDE C:\Program Files (x86)\Microsoft Visual Studio 12.0\VC\ATLMFC\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 LIB= C:\Program Files (x86)\Microsoft Visual Studio 12.0\VC\LIB C:\Program Files (x86)\Microsoft Visual Studio 12.0\VC\ATLMFC\LIB C:\Program Files (x86)\Windows Kits\8.1\lib\winv6.3\um\x86 PATH= C:\Program Files (x86)\Microsoft Visual Studio 12.0\Common7\IDE\CommonExtensions\Microsoft\TestWindow C:\Program Files (x86)\Microsoft SDKs\F#\3.1\Framework\v4.0\ C:\Program Files (x86)\MSBuild\12.0\bin C:\Program Files (x86)\Microsoft Visual Studio 12.0\Common7\IDE\ C:\Program Files (x86)\Microsoft Visual Studio 12.0\VC\BIN C:\Program Files (x86)\Microsoft Visual Studio 12.0\Common7\Tools C:\WINDOWS\Microsoft.NET\Framework\v4.0.30319 C:\Program Files (x86)\Microsoft Visual Studio 12.0\VC\VCPackages C:\Program Files (x86)\HTML Help Workshop C:\Program Files (x86)\Microsoft Visual Studio 12.0\Team Tools\Performance Tools C:\Program Files (x86)\Windows Kits\8.1\bin\x86 C:\Program Files (x86)\Microsoft SDKs\Windows\v8.1A\bin\NETFX 4.5.1 Tools\ C:\Perl64\site\bin C:\Perl64\bin C:\WINDOWS\system32 C:\WINDOWS C:\WINDOWS\System32\Wbem C:\WINDOWS\System32\WindowsPowerShell\v1.0\ C:\Program Files (x86)\Windows Kits\8.1\Windows Performance Toolkit\ C:\Program Files (x86)\Microsoft SDKs\TypeScript\1.0\ C:\Qt\Qt5.3.1-32\5.3\msvc2013_opengl\bin C:\Program Files (x86)\Skype\Phone\ C:\Program Files\Microsoft SQL Server\110\Tools\Binn\ C:\Program Files (x86)\QuickTime\QTSystem\ On 08/06/2015 14:50, Thiago Macieira wrote: On Monday 08 June 2015 14:43:26 Nuno Santos wrote: kernel\qhostaddress.cpp(786) : error C2065: 'INADDR_BROADCAST' : undeclared identifier kernel\qhostaddress.cpp(789) : error C2065: 'INADDR_LOOPBACK' : undeclared identifier Check if they are defined in winsock2.h, as they should be. ___ Interest mailing list Interest@qt-project.org http://lists.qt-project.org/mailman/listinfo/interest
Re: [Interest] How to run a WinRT app on a Window 8 intel tablet?
Andrew, I'm configure QT with this line: configure -prefix c:\qt\5.4\winrt_x86 -xplatform winrt-x64-msvc2013 -debug-and-release -nomake examples -nomake tests -skip webkit -skip multimedia How do you configure yours? I didn't had problems configuring it, but i'm having problems building it. kernel\qhostaddress.cpp(786) : error C2065: 'INADDR_BROADCAST' : undeclared identifier kernel\qhostaddress.cpp(789) : error C2065: 'INADDR_LOOPBACK' : undeclared identifier kernel\qhostaddress.cpp(795) : error C2065: 'INADDR_ANY' : undeclared identifier Regards, Nuno On 08/06/2015 11:25, Andrew Knight wrote: Hi Nuno, On 08/06/15 13:05, Nuno Santos wrote: Oliver, Is Qt for WinRT only available for x64 arch? In terms of pre-built releases, yes. The test tablet I got is x64 but it has a 32bit windows installed on it. Is there any way of work around this? Build Qt yourself with the winrt-x86-msvc2013 mkspec. Regards, Nuno On 04/06/2015 12:37, Oliver Wolff wrote: Hi, I am afraid that deployment to a device from Creator only works for Windows Phone but not for Windows Tablets. For Tablets you have to package/deploy everything manually using windeployqt for example. The other option (that I would tend to avoid) would be building on your tablet (if it has an x86 CPU). Another option would be to use Visual Studio. There it should be possible to select your tablet and deploy the application you created (for example by calling qmake -tp vc CONFIG+=windeployqt). Some more information can be found on http://doc.qt.io/qt-5/winrt-support.html#package-content but the content here is partially outdated and being updated at the moment. The D3D shader service for example is no longer needed. BR, Olli On 6/4/2015 12:57, Nuno Santos wrote: Hi, I'm doing my first experiments with WinRT. I have a Dell Window 8 tablet and i'm trying to run a QtQuick Hello World program on it. I was able to start the app on the computer but not on the tablet. I thought there was a mechanism like iOS and Android, in which I could select the device. Is there any guide line on how to proceed? Regards, Nuno ___ 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 mailing list Interest@qt-project.org http://lists.qt-project.org/mailman/listinfo/interest
Re: [Interest] NSView inside Carbon Window
Rene, New findings… After printing the pointer with NSLog(“%@“, ptr); I have found that the pointer is actually for a NSView Unfortunately, when I create a QWindow::fromWinId((Wid)ptr), the program crashes… I have been inspecting QWindow and in case of qcocoa, it is actually expecting a NSView to be passed. Crashed Thread:0 Dispatch queue: com.apple.main-thread Exception Type:EXC_BAD_ACCESS (SIGSEGV) Exception Codes: KERN_INVALID_ADDRESS at 0x002b VM Regions Near 0x2b: MALLOC_LARGE (reserved 00012ddd-000423db6000 [ 11.8G] rw-/rwx SM=NUL reserved VM address space (unallocated) -- __TEXT 1234-123400509000 [ 5156K] r-x/rwx SM=COW /System/Library/Extensions/AppleIntelHD5000GraphicsGLDriver.bundle/Contents/MacOS/AppleIntelHD5000GraphicsGLDriver Thread 0 Crashed:: Dispatch queue: com.apple.main-thread 0 libsystem_c.dylib 0x7fff8a9ab152 strlen + 18 1 org.qt-project.QtCore 0x0001204def27 QCoreApplication::arguments() + 199 2 org.qt-project.QtQuick 0x00011f933d76 0x11f8a4000 + 589174 3 org.qt-project.QtQuick 0x00011f934299 QSGContext::createWindowManager() + 9 4 org.qt-project.QtQuick 0x00011f9494c7 QSGRenderLoop::instance() + 71 5 org.qt-project.QtQuick 0x00011f97acc3 QQuickWindowPrivate::init(QQuickWindow*, QQuickRenderControl*) + 307 6 org.qt-project.QtQuick 0x00011fa2639d QQuickView::QQuickView(QWindow*) + 189 7 com.imaginando.Audiolab 0x00011efd9e3b IVstEditor::open(void*) + 107 (IVstEditor.cpp:34) Nuno Santos Founder / CEO / CTO www.imaginando.pt +351 91 621 69 62 On 08 Jun 2015, at 16:12, Nuno Santos nunosan...@imaginando.pt wrote: Rene, Answers below... On 08 Jun 2015, at 12:05, René J.V. Bertin rjvber...@gmail.com mailto:rjvber...@gmail.com wrote: On Monday June 08 2015 11:51:25 Nuno Santos wrote: NSWindow *nsw = [[NSWindow alloc] initWithWindowRef:(WindowRef*)ptr]; 2015-06-08 11:45:36.795 Live[65095:685104] A Carbon window's attributes couldn't be gotten. 2015-06-08 11:45:36.795 Live[65095:685104] A Carbon window's features couldn't be gotten. 2015-06-08 11:45:36.795 Live[65095:685104] Couldn't get window modality: error=-5600 % /usr/bin/macerror -5600 Mac OS error -5600 (errInvalidWindowRef): tried to pass a bad WindowRef argument This is a nice tip. Didn’t knew about macerror tool Are you by chance passing a pointer to a WindowRef? Well, VST SDK says that in case of windows a HWND will be passed and in case of Mac OS X a WindowRef will be passed. The open function argument is a void* Also, heed the advice at the bottom of this page: http://www.cocoabuilder.com/archive/cocoa/298219-initializing-nswindow-with-carbon-window.html http://www.cocoabuilder.com/archive/cocoa/298219-initializing-nswindow-with-carbon-window.html . There is a CoreAudio mailing list on which you're likely to get better answers, if this has to do with AU. 2015-06-08 11:45:36.795 Live[65095:685104] frame - 0.00 0.00 0.00 0.00 I’m also not doing anything else with the Window. If I use it as a parent of QQuickView (approach that works on Windows), the host app crashes with the following: That's a crash in the video driver (with a weird backtrace suggesting it's in strlen() called from QCoreApplication::arguments(), or maybe it really is in that function). It's bad that it's so easy to provoke that, but it probably comes directly from the error above. The window you get isn't valid. R. Crashed Thread:0 Dispatch queue: com.apple.main-thread Exception Type:EXC_BAD_ACCESS (SIGSEGV) Exception Codes: KERN_INVALID_ADDRESS at 0x002b VM Regions Near 0x2b: MALLOC_LARGE (reserved 00012d20-0004231e6000 [ 11.8G] rw-/rwx SM=NUL reserved VM address space (unallocated) -- __TEXT 1234-123400509000 [ 5156K] r-x/rwx SM=COW /System/Library/Extensions/AppleIntelHD5000GraphicsGLDriver.bundle/Contents/MacOS/AppleIntelHD5000GraphicsGLDriver Thread 0 Crashed:: Dispatch queue: com.apple.main-thread 0 libsystem_c.dylib 0x7fff8a9ab152 strlen + 18 1 org.qt-project.QtCore 0x00011f4f6f27 QCoreApplication::arguments() + 199 2 org.qt-project.QtQuick 0x00011e94bd76 0x11e8bc000 + 589174 3 org.qt-project.QtQuick 0x00011e94c299 QSGContext::createWindowManager() + 9 4 org.qt-project.QtQuick 0x00011e9614c7 QSGRenderLoop::instance() + 71 5 org.qt-project.QtQuick 0x00011e992cc3 QQuickWindowPrivate::init(QQuickWindow*, QQuickRenderControl*) + 307 6 org.qt-project.QtQuick 0x00011ea3e39d QQuickView::QQuickView(QWindow*) + 189 7 com.imaginando.Audiolab
Re: [Interest] How to run a WinRT app on a Window 8 intel tablet?
Still can't build WinRT x86 from source. Now it's failing here but can't understand why... link /NOLOGO /DYNAMICBASE /NXCOMPAT /NODEFAULTLIB:ole32.lib /APPCONTAINER /SAFESEH /MACHINE:X86 /DEBUG /MANIFEST:NO /DLL /SUBSYSTEM:WINDOWS /V ERSION:5.42 /OUT:..\..\..\..\plugins\imageformats\qwbmpd.dll @C:\Users\nsantos\AppData\Local\Temp\qwbmpd.dll.2080.922.jom Creating library ..\..\..\..\plugins\imageformats\qwbmpd.lib and object ..\..\..\..\plugins\imageformats\qwbmpd.exp cd imageformats\ ( if not exist Makefile C:\Qt\5.4\Src\qtbase\bin\qmake C:\Qt\5.4\Src\qtimageformats\src\imageformats\imageformats.pro -o M akefile ) C:\Qt\5.4\jom.exe -f Makefile C:\Qt\5.4\jom.exe -f Makefile.Debug jom: C:\Qt\5.4\Src\Makefile [module-qtxmlpatterns-make_first] Error 2 C:\Qt\5.4\Src On 08/06/2015 14:50, Thiago Macieira wrote: On Monday 08 June 2015 14:43:26 Nuno Santos wrote: kernel\qhostaddress.cpp(786) : error C2065: 'INADDR_BROADCAST' : undeclared identifier kernel\qhostaddress.cpp(789) : error C2065: 'INADDR_LOOPBACK' : undeclared identifier Check if they are defined in winsock2.h, as they should be. ___ Interest mailing list Interest@qt-project.org http://lists.qt-project.org/mailman/listinfo/interest
Re: [Interest] NSView inside Carbon Window
Rene, Answers below... On 08 Jun 2015, at 12:05, René J.V. Bertin rjvber...@gmail.com wrote: On Monday June 08 2015 11:51:25 Nuno Santos wrote: NSWindow *nsw = [[NSWindow alloc] initWithWindowRef:(WindowRef*)ptr]; 2015-06-08 11:45:36.795 Live[65095:685104] A Carbon window's attributes couldn't be gotten. 2015-06-08 11:45:36.795 Live[65095:685104] A Carbon window's features couldn't be gotten. 2015-06-08 11:45:36.795 Live[65095:685104] Couldn't get window modality: error=-5600 % /usr/bin/macerror -5600 Mac OS error -5600 (errInvalidWindowRef): tried to pass a bad WindowRef argument This is a nice tip. Didn’t knew about macerror tool Are you by chance passing a pointer to a WindowRef? Well, VST SDK says that in case of windows a HWND will be passed and in case of Mac OS X a WindowRef will be passed. The open function argument is a void* Also, heed the advice at the bottom of this page: http://www.cocoabuilder.com/archive/cocoa/298219-initializing-nswindow-with-carbon-window.html . There is a CoreAudio mailing list on which you're likely to get better answers, if this has to do with AU. 2015-06-08 11:45:36.795 Live[65095:685104] frame - 0.00 0.00 0.00 0.00 I’m also not doing anything else with the Window. If I use it as a parent of QQuickView (approach that works on Windows), the host app crashes with the following: That's a crash in the video driver (with a weird backtrace suggesting it's in strlen() called from QCoreApplication::arguments(), or maybe it really is in that function). It's bad that it's so easy to provoke that, but it probably comes directly from the error above. The window you get isn't valid. R. Crashed Thread:0 Dispatch queue: com.apple.main-thread Exception Type:EXC_BAD_ACCESS (SIGSEGV) Exception Codes: KERN_INVALID_ADDRESS at 0x002b VM Regions Near 0x2b: MALLOC_LARGE (reserved 00012d20-0004231e6000 [ 11.8G] rw-/rwx SM=NUL reserved VM address space (unallocated) -- __TEXT 1234-123400509000 [ 5156K] r-x/rwx SM=COW /System/Library/Extensions/AppleIntelHD5000GraphicsGLDriver.bundle/Contents/MacOS/AppleIntelHD5000GraphicsGLDriver Thread 0 Crashed:: Dispatch queue: com.apple.main-thread 0 libsystem_c.dylib0x7fff8a9ab152 strlen + 18 1 org.qt-project.QtCore0x00011f4f6f27 QCoreApplication::arguments() + 199 2 org.qt-project.QtQuick 0x00011e94bd76 0x11e8bc000 + 589174 3 org.qt-project.QtQuick 0x00011e94c299 QSGContext::createWindowManager() + 9 4 org.qt-project.QtQuick 0x00011e9614c7 QSGRenderLoop::instance() + 71 5 org.qt-project.QtQuick 0x00011e992cc3 QQuickWindowPrivate::init(QQuickWindow*, QQuickRenderControl*) + 307 6 org.qt-project.QtQuick 0x00011ea3e39d QQuickView::QQuickView(QWindow*) + 189 7 com.imaginando.Audiolab 0x00011dff1e1b IVstEditor::open(void*) + 107 (IVstEditor.cpp:34) Nuno Santos Founder / CEO / CTO www.imaginando.pt +351 91 621 69 62 On 08 Jun 2015, at 11:36, René J.V. Bertin rjvber...@gmail.com wrote: On Monday June 08 2015 09:24:56 Nuno Santos wrote: Hi Nuno: I'm trying to instantiate a QWindow inside a Carbon WindowRef, but QWindow fromWid method needs a NSView to be passed by parameter and not a WindowRef. I have seen been saying that it is not possible to have a NSView inside a CarbonWindow. Maybe someone more experienced in Mac OSX architecture could confirm me this. Try this: https://developer.apple.com/library/mac/documentation/Cocoa/Reference/ApplicationKit/Classes/NSWindow_Class/index.html#//apple_ref/occ/instm/NSWindow/initWithWindowRef: Then you send a contentView message to the NSWindow instance you got. Note that that gives you the window’s content view, the highest accessible NSView object in the window’s view hierarchy. If that's not the one you need, you'll have to figure out how to get the subviews (answer via google!) and pick the right one. R. ___ 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] NSView inside Carbon Window
On Monday June 08 2015 16:12:07 Nuno Santos wrote: Are you by chance passing a pointer to a WindowRef? Well, VST SDK says that in case of windows a HWND will be passed and in case of Mac OS X a WindowRef will be passed. The open function argument is a void* I'm guessing you'll have to pass the WindowRef as is, as if it were a pointer. It probably *is* a pointer, just like a HWND is. R. ___ Interest mailing list Interest@qt-project.org http://lists.qt-project.org/mailman/listinfo/interest
Re: [Interest] How to run a WinRT app on a Window 8 intel tablet?
On 08/06/15 17:25, Nuno Santos wrote: Thiago, Nope, it was not defined... Had to define it. Did it like this on qhostaddress.h #define INADDR_ANY ((unsigned long int) 0x) #define INADDR_BROADCAST((unsigned long int) 0x) #define INADDR_LOOPBACK 0x7f01 /* 127.0.0.1 */ The winsock2.h that I edited was on: C:\Program Files (x86)\Windows Kits\8.1\include\um Have you only installed VS2013 (Express/Ultimate/Pro?). One possible solution is to install the standalone Windows 8.1 SDK (https://msdn.microsoft.com/en-us/windows/desktop/bg162891.aspx) on top, as it seems some versions that ship with VS have different defines around these symbols. We should probably implement some ifdef magic to fix to define these inside Qt as needed. Another option is to use VS2013 Community Edition, as I'm pretty sure things work there out of the box. VS2015 also works, but you need https://codereview.qt-project.org/112015 -Andrew ___ Interest mailing list Interest@qt-project.org http://lists.qt-project.org/mailman/listinfo/interest
Re: [Interest] How to run a WinRT app on a Window 8 intel tablet?
On 08/06/15 17:50, Nuno Santos wrote: Still can't build WinRT x86 from source. Now it's failing here but can't understand why... link /NOLOGO /DYNAMICBASE /NXCOMPAT /NODEFAULTLIB:ole32.lib /APPCONTAINER /SAFESEH /MACHINE:X86 /DEBUG /MANIFEST:NO /DLL /SUBSYSTEM:WINDOWS /V ERSION:5.42 /OUT:..\..\..\..\plugins\imageformats\qwbmpd.dll @C:\Users\nsantos\AppData\Local\Temp\qwbmpd.dll.2080.922.jom Creating library ..\..\..\..\plugins\imageformats\qwbmpd.lib and object ..\..\..\..\plugins\imageformats\qwbmpd.exp cd imageformats\ ( if not exist Makefile C:\Qt\5.4\Src\qtbase\bin\qmake C:\Qt\5.4\Src\qtimageformats\src\imageformats\imageformats.pro -o M akefile ) C:\Qt\5.4\jom.exe -f Makefile C:\Qt\5.4\jom.exe -f Makefile.Debug jom: C:\Qt\5.4\Src\Makefile [module-qtxmlpatterns-make_first] Error 2 There are interleaved make commands here, so please use nmake to straighten out the output and find which project is failing. It looks like qtxmlpatterns is the one breaking the build, so go in there and run nmake to see if there's e.g. another symbol definition related issue. -Andrew ___ Interest mailing list Interest@qt-project.org http://lists.qt-project.org/mailman/listinfo/interest
