Problems with Open-Source Downloads read https://www.qt.io/blog/problem-with-open-source-downloads and https://forum.qt.io/post/638946

Qt 5.3 Build Error for iOS - ATSFont



  • I recently tried compiling Qt 5.3.0-alpha for iOS and ran into a number of build errors related to ATSFont declarations:

    https://gist.github.com/bdentino/9592695

    It looked like all of these errors were caused by attempting to compile code only processed when the HAVE_ATS macro is nonzero. So I found where it is actually defined (qcoretextfontdatabase_p.h : line 46) and explicitly set it to 0.

    @
    #define HAVE_ATS 0//QT_MAC_PLATFORM_SDK_EQUAL_OR_ABOVE(__MAC_10_5, __IPHONE_NA)
    @

    After making that change, I was able to successfully build, but now I am running into a number of undefined symbol errors in libqios.a while building qtdeclarative:

    https://gist.github.com/bdentino/9592701

    I'm hoping someone out there can help me determine if this is a bug or if my build is just misconfigured. Specifically, is HAVE_ATS supposed to be defined for the iOS build? If so, do the above font errors make any sense? Could the change that I made to explicitly set HAVE_ATS to 0 be related to the undefined symbol errors?

    I'm setup on OSX 10.9.2, Xcode 5.1, and iOS SDK 7.1. Here is the command I used to configure the build:

    @
    ../Source/configure -developer-build -opensource -nomake examples -nomake tests -prefix $PWD/qtbase -debug-and-release -xplatform macx-ios-clang -openssl -I /Users/bdentino/Documents/GitHub/OpenSSL-for-iPhone/include/ -confirm-license
    @

    Anyone have any insight?

    UPDATE:
    I was able to successfully build qtdeclarative by clearing out my qtbase build and starting from scratch after making the aforementioned change to HAVE_ATS (previously I had started building, saw that it failed, made the adjustments, and ran make again without cleaning).

    I would still be very interested to know more about this HAVE_ATS macro. Does the fact that this was non-zero for an iOS-configured build constitute a bug? Or should I expect any undefined Qt behavior as a result of explicitly setting it to 0 for this build?


  • Lifetime Qt Champion

    Hi,

    Since it's beta related you should rather ask this on the interest mailing list, you'll find there Qt's developers/maintainers (this forum is more user oriented)



  • Thanks @SGaist! Just joined the interest mailing list and sent this question out there.


Log in to reply