[Development] iOS Qt 5.3 CI broken
Knoll Lars
Lars.Knoll at digia.com
Thu Sep 4 09:34:10 CEST 2014
On 04/09/14 03:19, "Jake Petroules" <jake.petroules at petroules.com> wrote:
>On 2014-09-03, at 07:58 PM, Thiago Macieira <thiago.macieira at intel.com>
>wrote:
>
>> Could someone either fix it or disable iOS builds in the CI for 5.3?
>>
>>
>>/Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctool
>>chain/usr/bin/clang
>> -c -pipe -fvisibility=hidden -fpascal-strings -fmessage-length=0 -Wno-
>> trigraphs -Wreturn-type -Wparentheses -Wswitch -Wno-unused-parameter
>>-Wunused-
>> variable -Wunused-value -Wno-shorten-64-to-32 -Wno-sign-conversion -
>> fexceptions -fasm-blocks -Wno-missing-field-initializers -Wno-missing-
>> prototypes -Wno-implicit-atomic-properties -Wformat -Wno-missing-braces
>>-Wno-
>> unused-function -Wno-unused-label -Wuninitialized -Wno-unknown-pragmas
>>-Wno-
>> shadow -Wno-four-char-constants -Wno-sign-compare -Wpointer-sign
>>-Wno-newline-
>> eof -Wdeprecated-declarations -Winvalid-offsetof -Wno-conversion
>>-fvisibility-
>> inlines-hidden -Wno-non-virtual-dtor -Wno-overloaded-virtual
>>-Wno-exit-time-
>> destructors -Wno-arc-abi -fobjc-nonfragile-abi -fobjc-legacy-dispatch
>>-Wno-
>> deprecated-implementations -Wprotocol -Wno-selector
>>-Wno-strict-selector-match
>> -Wno-undeclared-selector -arch i386 -O2 -isysroot
>>
>>/Applications/Xcode.app/Contents/Developer/Platforms/iPhoneSimulator.plat
>>form/Developer/SDKs/iPhoneSimulator7.0.sdk
>> -std=c++11 -stdlib=libc++ -mios-simulator-version-min=5.0
>>-fvisibility=hidden
>> -fvisibility-inlines-hidden -Wall -W -DDARWIN_NO_CARBON -DQT_NO_PRINTER
>>-
>> DQT_NO_PRINTDIALOG -DQT_NO_MTDEV -DQT_NO_LIBUDEV -DQT_NO_EVDEV -
>> DQT_NO_EXCEPTIONS -D_LARGEFILE64_SOURCE -D_LARGEFILE_SOURCE
>>-DQT_NO_DEBUG -
>> DQT_STATICPLUGIN -DQT_PLUGIN -DQT_PLATFORMSUPPORT_LIB -DQT_GUI_LIB -
>> DQT_CORE_LIB -I../../../../mkspecs/macx-ios-clang -I. -
>> I/work/build/qt/qtbase/mkspecs/macx-ios-clang/ios -I../../../../include
>>-
>> I../../../../include/QtPlatformSupport -
>> I../../../../include/QtPlatformSupport/5.3.3 -
>> I../../../../include/QtPlatformSupport/5.3.3/QtPlatformSupport -
>> I../../../../include/QtGui/5.3.3
>>-I../../../../include/QtGui/5.3.3/QtGui -
>> I../../../../include/QtCore/5.3.3
>>-I../../../../include/QtCore/5.3.3/QtCore -
>> I../../../../include/QtGui -I../../../../include/QtCore -I.moc
>>qiosscreen.mm -
>> o .obj/qiosscreen.o
>> qiosscreen.mm:299:49: error: no member named 'MV_IOS_8_0' in 'QSysInfo'
>> qiosscreen.mm:299:73: error: property 'nativeBounds' not found on
>>object of
>> type 'UIScreen *'
>>
>> --
>> Thiago Macieira - thiago.macieira (AT) intel.com
>> Software Architect - Intel Open Source Technology Center
>>
>> _______________________________________________
>> Development mailing list
>> Development at qt-project.org
>> http://lists.qt-project.org/mailman/listinfo/development
>
>MV_IOS_8_0 was introduced in dev after 5.3 was branched (and thus isn't
>in 5.3), and new enum values cannot be added to 5.3.x. I've therefore
>"moved" the offending commit to dev.
>
>https://codereview.qt-project.org/#/c/93956/ (reverted offending commit
>in 5.3)
>https://codereview.qt-project.org/#/c/93957/ (cherry-picked offending
>commit to dev)
Wouldn't 5.4 make more sense than dev?
Cheers,
Lars
More information about the Development
mailing list