>>> FWIW I see there is WEBENGINE_CONFIG += use_appstore_compliant_code option >>> present there. No idea if it's sufficient. >> >> FYI, it's not sufficient, which is why I'm considering going back to WebKit. > > Ok. If you don't mind to do some compilation, please get 5.212 branch from > git://code.qt.io/qt/qtwebkit.git > and apply patch https://0x0.st/siPl.txt to it, then build as in [1] but with > additional cmake argument > -DUSE_APPSTORE_COMPLIANT_CODE=ON
It should probable be ok to install ICU with brew or macports if you don't want to build it. And I think advice to use U_DISABLE_RENAMING in the article makes no sense, it's better to keep it as is. > > If you have no interest in use of QML API you can also add > -DENABLE_WEBKIT2=OFF. > > (Depending on kind of your application you may want to cut down some other > stuff, look at public > cmake options with tool like ccmake or cmake-gui) > > [1] https://github.com/annulen/webkit/wiki/Building-QtWebKit-on-OS-X > >> On Sat, Nov 11, 2017 at 9:09 AM, Konstantin Tokarev <[email protected]> >> wrote: >> >>>>> Hi, >>> >>>> Hi, >>> >>>> Please use webkit-qt@ lists.webkit.org mailing list for QtWebKit questions >>>> which don't involve confidential information >>> >>>>> I have an app that I publish on the Mac App Store that used QtWebKit. I >>>>> remember that in order to get it published I had to follow these >>>>> instructions: http://wiki.phisys.com/index.php/How-To_Qt5.3_Mac_AppStore >>> >>>>> Since Qt seemed to be moving forward with WebEngine, I spent a couple >>>>> months refactoring my app to use that instead. However it wasn't until I >>>>> was ready to publish my app that I learned some of the Chromium backend >>>>> uses private API, which is not allowed on the Mac App Store. Ugh! >>> >>>> FWIW I see there is WEBENGINE_CONFIG += use_appstore_compliant_code option >>>> present there. No idea if it's sufficient. >>> >>>>> Now I'm thinking about going BACK to QtWebKit. Do you know if your fork >>>>> is Mac App Store compliant? Do you believe the instructions in the link >>>>> above are still relevant? Any advice? >>> >>>> I'm not aware of any better guide than your link above. See [1]. >>> >>>> I think ICU is still considered private API by Apple, and you have to >>>> build QtWebKit with your own copy of it. I think we can add an option like >>>> aforementioned use_appstore_compliant_code, which will suppress use of >>>> system ICU and maybe do other customizations. >>> >>>> I guess there should not be other issues with code, though structure of >>>> bundles may indeed make correction. >>> >>>> Article says that there is no workaround for WebKit2 (QML API), in fact I >>>> guess bootstrap_look_up2 issue is easy to get rid of by using unix sockets >>>> IPC implementation >>> >>>> [1] https://bugreports.qt.io/browse/QTBUG-31419 >>> >>> Note that I'm talking about QtWebKit 5.212. If you use legacy version e.g. >>> one shipped with Qt 5.9, instructions from article should apply verbatimely >>> >>>>> Thanks, >>> >>>>> Adalid Claure >>> >>>> -- >>> >>>> Regards, >>> >>>> Konstantin >>> >>>> _______________________________________________ >>> >>>> webkit-qt mailing list >>> >>>> [email protected] >>> >>>> https://lists.webkit.org/mailman/listinfo/webkit-qt >>> >>> -- >>> >>> Regards, >>> >>> Konstantin > > -- > Regards, > Konstantin > _______________________________________________ > webkit-qt mailing list > [email protected] > https://lists.webkit.org/mailman/listinfo/webkit-qt -- Regards, Konstantin _______________________________________________ webkit-qt mailing list [email protected] https://lists.webkit.org/mailman/listinfo/webkit-qt
