Re: [Interest] Qt 5.5 for ios: frameworks support seems to be broken

That's awesome! :) I think this should be considered a big and must be reported. It made me waste a good hand of hours. It seems I was not the only one! ;) -- Nuno Santos No dia 26/09/2015, às 04:14, Ben Lau escreveu: > HI Nuno, > > Thanks for you reply~ > > I just found out what is wron

Re: [Interest] Qt 5.5 for ios: frameworks support seems to be broken

HI Nuno, Thanks for you reply~ I just found out what is wrong with it. In my source tree, it has a directory with 3rd party QML library. The library contains test code using QtTest which is not included in my application, but qmlimportscanner still treat it as a part of my program. So it add Qt5Q

Re: [Interest] rvalue references on Mac OS X 10.10 and XCode 7

On Saturday 26 September 2015 00:19:22 Philippe wrote: > > If you have some old library that needs libstdc++, then you're stuck with > > it for now. That means you must tell your linker not to use libc++, so > > you need to ensure that the -stdlib=libstdc++ is passed to all steps of > > the build (

Re: [Interest] rvalue references on Mac OS X 10.10 and XCode 7

> If you have some old library that needs libstdc++, then you're stuck with it > for now. That means you must tell your linker not to use libc++, so you need > to ensure that the -stdlib=libstdc++ is passed to all steps of the build > (compiler and linker). Otherwise you'll get the linker errors

Re: [Interest] rvalue references on Mac OS X 10.10 and XCode 7

On Friday 25 September 2015 22:41:38 Philippe wrote: > In my case, I have to add libstdc++.dylib as a linker argument, else the > presence of an old static third-party library that I must use, causes some > linker error. If you have some old library that needs libstdc++, then you're stuck with it

Re: [Interest] rvalue references on Mac OS X 10.10 and XCode 7

On 25/09/2015 21:41, Philippe wrote: > In my case, I have to add libstdc++.dylib as a linker argument, else the > presence of an old static third-party library that I must use, causes some > linker error. Are you aware of quite how broken libstdc++ is on MacOS X with clang++? It's a nightmare.

Re: [Interest] rvalue references on Mac OS X 10.10 and XCode 7

In my case, I have to add libstdc++.dylib as a linker argument, else the presence of an old static third-party library that I must use, causes some linker error. But __GNUC_LIBSTD__ is not defined, hence Q_COMPILER_RVALUE_REFS is #defined. IOW, it's possible to link with libstdc++ without the pen

Re: [Interest] Qt 5.5 for ios: frameworks support seems to be broken

In my case the problem was that I was linking to a framework called parse and inside the project dir there was a parse dir. For some reason that directory with the name of the framework I was linking was making the linker line to become "-framework “ invalidating all the frameworks in the line f

Re: [Interest] rvalue references on Mac OS X 10.10 and XCode 7

On Friday 25 September 2015 12:51:29 Thiago Macieira wrote: > # if (defined(Q_CC_CLANG) || defined(Q_CC_INTEL)) && defined(Q_OS_MAC) && > defined(__GNUC_LIBSTD__) \ > && ((__GNUC_LIBSTD__-0) * 100 + __GNUC_LIBSTD_MINOR__-0 <= 402) > // Apple has not updated libstdc++ since 2007, which means it

Re: [Interest] dyld: lazy symbol binding failed: Symbol not found: _SSLCreateContext

On Friday 25 September 2015 19:34:40 Nuno Santos wrote: > + -openssl Enable run-time OpenSSL support. > -openssl-linked . Enabled linked OpenSSL support. > > > What is the difference bet run time and linked? Whether QtNetwork links to OpenSSL or just tries to dlopen() it a

Re: [Interest] rvalue references on Mac OS X 10.10 and XCode 7

On Friday 25 September 2015 20:55:03 Philippe wrote: > Why do you say so? > > Qt defines Q_COMPILER_RVALUE_REFS > and I don't see this define dependent on the presence of libstdc++ Sven is right. From qcompilerdetection.h: # if (defined(Q_CC_CLANG) || defined(Q_CC_INTEL)) && defined(Q_OS_MAC) &&

Re: [Interest] Qt 5.5 for ios: frameworks support seems to be broken

I got similar problem after upgraded to Qt 5.5, but all frameworks are linked successfully. It only complains about the linkage with XCTestCase. Ofcoz I didn't include any test lib in my application. And tried to clear .qmake.config and .qmake.cache , but it do not help. I have also tried to run

Re: [Interest] rvalue references on Mac OS X 10.10 and XCode 7

Why do you say so? Qt defines Q_COMPILER_RVALUE_REFS and I don't see this define dependent on the presence of libstdc++ Philippe On Fri, 25 Sep 2015 19:29:44 +0200 Sven Bergner wrote: Hi, > I've just came across the fact, that on Mac OS X the rvalue references are > disabled because of an old

Re: [Interest] dyld: lazy symbol binding failed: Symbol not found: _SSLCreateContext

Thiago, I have found the following. Configure script now selects SecureTransport SSL backend as default one on OS X unless -no-securetransport specified or any of: -openssl -openssl-linked and not -no-securetransport I’m only unsure about the difference between -openssl and -openssl-linked.

Re: [Interest] dyld: lazy symbol binding failed: Symbol not found: _SSLCreateContext

Thiago, No, should I? Can you tell me what it does? Thanks, -- Nuno Santos No dia 25/09/2015, às 17:23, Thiago Macieira escreveu: >> On Friday 25 September 2015 10:39:38 Nuno Santos wrote: >> Time, >> >> Thanks for your prompt reply. >> >> So that means that Qt apps that depend on system

[Interest] rvalue references on Mac OS X 10.10 and XCode 7

Hi, I've just came across the fact, that on Mac OS X the rvalue references are disabled because of an old libstdc++. Is this still the case with XCode 7 and clang 7.0.0? I'm just a little bit surprised, because we are using std::move in our application and that seems to work. Any help appreciated.

Re: [Interest] dyld: lazy symbol binding failed: Symbol not found: _SSLCreateContext

On Friday 25 September 2015 10:39:38 Nuno Santos wrote: > Time, > > Thanks for your prompt reply. > > So that means that Qt apps that depend on system SSL will only work on 10.8? Did you compile with -openssl-linked? -- Thiago Macieira - thiago.macieira (AT) intel.com Software Architect - Int

[Interest] Qt Purchasing and Android API>20

Hi, Qt Purchasing is not working if I target my app to > API 20. Has anyone experienced the same kind of problem? Regards, Nuno___ Interest mailing list Interest@qt-project.org http://lists.qt-project.org/mailman/listinfo/interest

[Interest] How are High DPI Icons supposed to work?

Dear List, is there any clear and concise How To for High DPI icons/pixmaps? I gathered some information from several Wiki pages, Blog posts and documentation pages [1-7], but no luck. My MNWE (minimal not working example): // from main.cpp int main(int argc, char *argv[]) { QApplication a(a

Re: [Interest] QcameraViewfinder on iOS

Problem solved. Just needed to set size policy of QCameraViewfinder to (Fixed,Fixed) 9/25/2015 2:03 PM, Alexey Godko пишет: AFAIK, camera does not work in QtWidgets at all. Try QML cam :) 2015-09-25 13:56 GMT+03:00 Igor Mironchik >: Hi guys, I've

Re: [Interest] QcameraViewfinder on iOS

It works. But QCameraViewfinder doesn't. It shows video but not scaled. And one more... From time to time. QCameraViewfinder correctly resize video and places... 9/25/2015 2:03 PM, Alexey Godko пишет: AFAIK, camera does not work in QtWidgets at all. Try QML cam :) 2015-09-25 13:56 GMT+03:00

Re: [Interest] QcameraViewfinder on iOS

AFAIK, camera does not work in QtWidgets at all. Try QML cam :) 2015-09-25 13:56 GMT+03:00 Igor Mironchik : > Hi guys, > > I've ran into problem. I place QCameraViewfinder on top level widget. I > use layouts to place elements on the form. > > QCameraViewfinder places correctly, resized, all is f

[Interest] QcameraViewfinder on iOS

Hi guys, I've ran into problem. I place QCameraViewfinder on top level widget. I use layouts to place elements on the form. QCameraViewfinder places correctly, resized, all is fine. But it draws not scaled video. I.e. I see only part of the frame (top left part) and it overlapped all content o

Re: [Interest] dyld: lazy symbol binding failed: Symbol not found: _SSLCreateContext

Time, Thanks for your prompt reply. So that means that Qt apps that depend on system SSL will only work on 10.8? Regards, -- Nuno Santos No dia 25/09/2015, às 10:33, Pocheptsov Timur escreveu: > Ooops, that's a trouble. SSLCreateContext is a part of Security Framework > starting from 10.8

[Interest] dyld: lazy symbol binding failed: Symbol not found: _SSLCreateContext

Hi, I have compiled an app on Mac OS X 10.10.5 using QT 5.6 Alpha and tried to run it on a Mac OS X 10.7.5, it failed to start saying: dyld: lazy symbol binding failed: Symbol not found: _SSLCreateContext Referenced from: /path/to/file Expected in: /System/Library/Frameworks/Security.framewo

Re: [Interest] Qt/D3D integration through ANGLE PBuffer

Finally success! As always it was a simple and stupid mistake It appears that I have linked with the release version of libEGL in the debug version of my test program. Linking with the debug version solved it. Now I get a pbuffer and share handle using the QOpenGLContext. Mixing debug and rele

[Interest] rvalue references on Mac OS X 10.10 and XCode 7

Hi, I've just came across the fact, that on Mac OS X the rvalue references are disabled because of an old libstdc++. Is this still the case with XCode 7 and clang 7.0.0? I'm just a little bit surprised, because we are using std::move in our application and that seems to work. Any hints are apprecia

Re: [Interest] Qt can't read JPG image that QCameraImageCapture saved.

Guys, this is fixed in 5.5.1 https://bugreports.qt.io/browse/QTBUG-47476 2015-09-25 11:54 GMT+03:00 Portale Alessandro < alessandro.port...@theqtcompany.com>: > Hi, > > could you upload such a jpeg image in a task on https://bugreports.qt.io/ > ? It sounds like a bug when Qt cannot read an image

Re: [Interest] Qt can't read JPG image that QCameraImageCapture saved.

Hi, could you upload such a jpeg image in a task on https://bugreports.qt.io/ ? It sounds like a bug when Qt cannot read an image which itselft saves. Thanks, Alessandro Von: interest-bounces+alessandro.portale=theqtcompany@qt-project.org im Auftra

Re: [Interest] Qt/D3D integration through ANGLE PBuffer

That didn't help, unfortunately. I tried moving the setAttribute to no effect. If I try dereferencing the eglDisplay and eglConfig values like this: EGLDisplay* eglDisplay = static_cast(nativeInterface-> nativeResourceForContext("eglDisplay", m_glContext)); EGLConfig* eglConfig = static_

Re: [Interest] Qt/D3D integration through ANGLE PBuffer

QCoreApplication::setAttribute(Qt::AA_UseOpenGLES); This should be set before constructing the QGuiApplication. EGLSurface pbuffer = eglCreatePbufferSurface(m_eglDisplay, m_eglConfig, attribs); This should be eglCreatePbufferSurface(*m_eglDisplay, *m_eglConfig, attribs). Note that you ma

Re: [Interest] Qt/D3D integration through ANGLE PBuffer

Now I've tried a lot of other things, but I'm still not there... I've tried using eglChooseConfig on the eglDisplay I got from the QPlatformNativeInterface (with different variations of the attribList below) const EGLint attribList[] = { EGL_SURFACE_TYPE, EGL_PBUFFER_BIT,