![]() Not enabled (Default, enable with WEBENGINE_CONFIG+=use_native_spellchecker)Īnd I see the spellchecker is still enabled. Not enabled (Default, enable with WEBENGINE_CONFIG+=use_appstore_compliant_code) Not enabled (Default, enable with WEBENGINE_CONFIG+=use_proprietary_codecs) I see: Info: creating cache file /Users/Me/Downloads/qt-everywhere-opensource-src-5.8.0/.qmake.cache qtbase/bin/qmake WEBENGINE_CONFIG+=no_spellcheck QtWebEngine I think my problem is that I'm not setting up the config right. usr/bin/codesign -deep -sign -entitlements /QtWebEngineProcess.appīut still, the same problem persists. So I tried inserting a step before the last one: And Console reports the same thing:Ĥ/23/17 09:00:49.103 sandboxd: () QtWebEngineProce(14028) deny forbidden-sandbox-reinitĤ/23/17 09:00:49.122 sandboxd: () QtWebEngineProce(14029) deny forbidden-sandbox-reinit I launch the app and I see the same results. Run /usr/bin/codesign -deep -sign -entitlements MyApp.appĬode signing reports no errors and runs fine.Run macdeployqt /MyApp.app -appstore-compliant -qmldir= (Making sure to use the macdeployqt that I just built.).chdir into macdeployqt's folder, which may or not may not be necessary some people on Stackoverflow mentioned they were having trouble without doing this, so I make sure to do it.Then I run my packaging script which does the following: So I reset my CMake paths (I'm using CMake), generate the Xcode project and verify through Xcode's settings that I'm linking this new Qt build (which I am). Great, so then I:Īnd now I have Qt in /usr/local/Qt5.8.0. I woke up this morning and this completed overnight. make -jobs=16 (this was before I saw that I only need to rebuild the QtWebEngine module).qtbase/bin/qmake WEBENGINE_CONFIG+=use_appstore_compliant_code (using the qmake that. configure (and accepted all the license stuff) Last night I downloaded the Qt source and run the following commands in order: Is there any documentation or psuedo code for writing these build/signing procedures? How exactly should everything in the package be signed? Is doing one signing of MyProgram.app ok? Do I need to sign everything individually? Maybe certain frameworks need different entitlements? I don't know. Which I can see in Console as: 4/21/17 23:55:06.020 sandboxd: () QtWebEngineProce(4543) deny forbidden-sandbox-reinitĤ/21/17 23:55:06.023 sandboxd: () QtWebEngineProce(4544) deny forbidden-sandbox-reinit Presumably because QtWebEngineProcess fails to run. The QWebEngine based control never renders anything. Yet, when I run the program my C++ and Qml widgets all render perfectly. Then I the only other thing I sign is my app's main bundle:.My command looks like this (Python code) subprocess.call([r'/usr/bin/codesign',īundleFolder + '/MyProgram.app/Contents/Frameworks/amework/Versions/5/Helpers/QtWebEngineProcess.app/Contents/MacOS/QtWebEngineProcess' Next, I sign that QtWebEngineProcess specifically with these QtWebEngineProcess-specific entitlements:.This puts the QtWebEngineProcess into my app's bundle, as well as many other files. I run the resulting bundle through macdeployqt.I build my Release build (MyProgram.app) through Xcode, with no signing.So obviously this has something to do with how I am signing the everything. ![]() QtWebEngineProce(1818) deny forbidden-sandbox-reinitĪnd the process never starts. The logs say what the problem is pretty clearly: ![]() app bundel, the app loads and everything EXCEPT the QWebEngine portions look fine. I run macdeployqt on my app and all is well. I have run into the same problem that a few others have run into however their fixes are either ambiguous or did not help me.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |