[Interest] Qt 5.5 for ios: frameworks support seems to be broken
Nuno Santos
nunosantos at imaginando.pt
Fri Jul 10 08:55:55 CEST 2015
Curiously, it seems that qmake whipes the reference to Parse framework. Whenever -framework Parse is referenced, it removes Parse.
Before -framework Bolts there was -framework Parse, if I move the -framework Parse after the Bolts, then the next one will have problems.
If I remove the -frameworks Parse I will obviously have undefined references to some Parse functions and i’m having a couple others that I still don’t know where they come from:
Undefined symbols for architecture armv7:
"_OBJC_CLASS_$_XCTestCase", referenced from:
_OBJC_CLASS_$_QtTestLibWrapper in libQt5Test_debug.a(qxctestlogger.o)
_OBJC_CLASS_$_QtTestLibTest in libQt5Test_debug.a(qxctestlogger.o)
"_OBJC_CLASS_$_XCTestSuite", referenced from:
objc-class-ref in libQt5Test_debug.a(qxctestlogger.o)
_OBJC_CLASS_$_QtTestLibTests in libQt5Test_debug.a(qxctestlogger.o)
"_OBJC_CLASS_$_XCTestDriver", referenced from:
objc-class-ref in libQt5Test_debug.a(qxctestlogger.o)
"_OBJC_METACLASS_$_XCTestSuite", referenced from:
_OBJC_METACLASS_$_QtTestLibTests in libQt5Test_debug.a(qxctestlogger.o)
"_OBJC_CLASS_$_XCTestProbe", referenced from:
objc-class-ref in libQt5Test_debug.a(qxctestlogger.o)
"_OBJC_CLASS_$_Parse", referenced from:
objc-class-ref in LKAppDelegate.o
"_OBJC_CLASS_$_PFPush", referenced from:
objc-class-ref in LKAppDelegate.o
"_OBJC_METACLASS_$_XCTestCase", referenced from:
_OBJC_METACLASS_$_QtTestLibWrapper in libQt5Test_debug.a(qxctestlogger.o)
_OBJC_METACLASS_$_QtTestLibTest in libQt5Test_debug.a(qxctestlogger.o)
"_OBJC_CLASS_$_PFInstallation", referenced from:
objc-class-ref in LKAppDelegate.o
** BUILD FAILED **
Any ideas?
Thanks,
Nuno
> On 10/07/2015, at 01:05, Thiago Macieira <thiago.macieira at intel.com> wrote:
>
> On Friday 10 July 2015 00:43:48 Nuno Santos wrote:
>> -u _qt_registerPlatformPlugin -framework -framework Bolts
>
> There's one extra -framework there, so this is telling the linker to link to
> framework "-framework" and then use a local file called "Bolts" as input
> object.
>
> If you run qmake with the -d -d options, you'll see how it processes. Search
> for what came before that double -framework and you'll find out what was the
> framework that got dropped.
>
> If you look for the first occurrence of "-framework -framework", you'll find the
> place where the framework got dropped or failed to be added.
> --
> Thiago Macieira - thiago.macieira (AT) intel.com
> Software Architect - Intel Open Source Technology Center
>
> _______________________________________________
> Interest mailing list
> Interest at qt-project.org
> http://lists.qt-project.org/mailman/listinfo/interest
More information about the Interest
mailing list