无法在 OS X 上使用 Qt 框架签署应用程序包 10.10

2 回答

• 3

  在进一步挖掘之后，我弄清楚第七节中的问题是什么：一些 Qt 框架在 Info.plist 文件中包含错误信息(框架名称以_debug 结尾)

  我推出了这个修复所有问题的脚本(还有一些硬编码的值可能会通过对脚本的一些改进来处理)

  #!/bin/bash
  # Script name: deploy.sh
  
  # Following environment variables must be defined:
  # - QT_FRAMEWORK_PATH
  # - QT_BIN_PATH
  # - CERTIFICATE
  # - FRAMEWORKS
  # - BAD_FRAMEWORKS
  
  # retrieve bundle name from first parameter
  BUNDLE_NAME=$1
  
  # Run QT tool to deploy
  ${QT_BIN_PATH}/macdeployqt $BUNDLE_NAME
  
  # FIX ISSUE 6
  # Please note that Qt5 frameworks have incorrect layout after SDK build, so this isn't just a problem with `macdeployqt` but whole framework assembly part.
  # Present
  #   QtCore.framework/
  #       Contents/
  #           Info.plist
  #       QtCore    -> Versions/Current/QtCore
  #       Versions/
  #           Current -> 5
  #           5/
  #               QtCore
  # After macdeployqt
  #   QtCore.framework/
  #       Resources/
  #       Versions/
  #           5/
  #               QtCore
  #
  # Expected
  #   QtCore.framework/
  #       QtCore    -> Versions/Current/QtCore
  #       Resources -> Versions/Current/Resources
  #       Versions/
  #           Current -> 5
  #           5/
  #               QtCore
  #               Resources/
  #                   Info.plist
  # So in order to comply with expected layout: https://developer.apple.com/library/mac/documentation/MacOSX/Conceptual/BPFrameworks/Concepts/FrameworkAnatomy.html
  
  for CURRENT_FRAMEWORK in ${FRAMEWORKS}; do
      echo "Processing framework: ${CURRENT_FRAMEWORK}"
  
      echo "Deleting existing resource folder"
      rmdir ${BUNDLE_NAME}/Contents/Frameworks/${CURRENT_FRAMEWORK}.framework/Resources
  
      echo "create resource folder"
      mkdir -p ${BUNDLE_NAME}/Contents/Frameworks/${CURRENT_FRAMEWORK}.framework/Versions/5/Resources
  
      echo "create copy resource file"
      cp ${QT_FRAMEWORK_PATH}/${CURRENT_FRAMEWORK}.framework/Contents/Info.plist $BUNDLE_NAME/Contents/Frameworks/${CURRENT_FRAMEWORK}.framework/Versions/5/Resources/
  
      echo "create symbolic links"
      ln -nfs 5                                     ${BUNDLE_NAME}/Contents/Frameworks/${CURRENT_FRAMEWORK}.framework/Versions/Current
      ln -nfs Versions/Current/${CURRENT_FRAMEWORK} ${BUNDLE_NAME}/Contents/Frameworks/${CURRENT_FRAMEWORK}.framework/${CURRENT_FRAMEWORK}
      ln -nfs Versions/Current/Resources            ${BUNDLE_NAME}/Contents/Frameworks/${CURRENT_FRAMEWORK}.framework/Resources
  done
  
  # FIX ISSUE 7
  echo "***** Correct Frameworks Info.plist file*****"
  
  for CURRENT_FRAMEWORK in ${BAD_FRAMEWORKS}; do
      echo "Correcting bad framework Info.plist: ${CURRENT_FRAMEWORK}"
      TMP=$(sed 's/_debug//g' ${BUNDLE_NAME}/Contents/Frameworks/${CURRENT_FRAMEWORK}.framework/Resources/Info.plist)
      echo "$TMP" > ${BUNDLE_NAME}/Contents/Frameworks/${CURRENT_FRAMEWORK}.framework/Resources/Info.plist
  done
  
  # SIGNING FIXED FRAMEWORK
  CODESIGN_OPTIONS="--verbose=4"
  
  #echo "******* Sign QtWebEngineProcess ***********"
  #codesign --force --verify ${CODESIGN_OPTIONS} --sign "$CERTIFICATE" $BUNDLE_NAME/Contents/Frameworks/QtWebEngineCore.framework/Versions/Current/Helpers/QtWebEngineProcess.app
  echo "******* Sign Frameworks-subApps ***********"
  codesign --force --verify ${CODESIGN_OPTIONS} --sign "$CERTIFICATE" $BUNDLE_NAME/Contents/Frameworks/*.framework/Versions/*/*/*.app
  
  echo "******* Signing Frameworks ***********"
  for CURRENT_FRAMEWORK in ${FRAMEWORKS}; do
      echo "Signing framework: ${CURRENT_FRAMEWORK}"
      codesign --force --verify ${CODESIGN_OPTIONS} --sign "$CERTIFICATE" $BUNDLE_NAME/Contents/Frameworks/${CURRENT_FRAMEWORK}.framework
  done
  
  # Sign plugins
  echo "******* Signing Plugins ***********"
  codesign --force --verify ${CODESIGN_OPTIONS} --sign "${CERTIFICATE}" ${BUNDLE_NAME}/Contents/Plugins/*/*.dylib
  
  # Sign bundle itself
  echo "******* Signing Bundle ***********"
  codesign --force --verify ${CODESIGN_OPTIONS} --sign "$CERTIFICATE" $BUNDLE_NAME
  
  # Verify
  
  echo "******* Verify Bundle ***********"
  codesign --verify --deep ${CODESIGN_OPTIONS} $BUNDLE_NAME
  
  echo "******* Verify Bundle using dpctl ***********"
  spctl -a -vvvv $BUNDLE_NAME
  

  至于调用脚本：

  # Define environment variables
  export QT_FRAMEWORK_PATH=/Path/To/Qt_5.3.2/5.3/clang_64/lib
  export QT_BIN_PATH=/Path/To/Qt_5.3.2/5.3/clang_64/bin
  export CERTIFICATE="Developer ID Application: My Certificate"
  export FRAMEWORKS="QtCore QtGui QtPrintSupport QtWidgets"
  export BAD_FRAMEWORKS="QtPrintSupport"
  
  # Call itself
  deploy.sh SimpleHello.app
  

  使用此脚本，最终输出为：

  SimpleHello.app/: accepted
  source=Developer ID
  origin=Developer ID Application: My Certificate (HASH)
  

  回复于 2024-04-19T15:48:59+08:00
• 0

  我运行 macdeployqt 后运行类似于此的脚本：

  #!/bin/bash
  
  #copy .plist files to frameworks
  cp "/usr/local/Trolltech/Qt-4.8.5/lib/QtCore.framework/Contents/Info.plist" "SimpleHello.app/Contents/Frameworks/QtCore.framework/Resources/Info.plist"
  #copy folders to proper location
  cp -r "SimpleHello.app/Contents/Frameworks/QtCore.framework/Resources" "SimpleHello.app/Contents/Frameworks/QtCore.framework/Versions/4/Resources"
  #delete old folders
  rm -rf "SimpleHello.app/Contents/Frameworks/QtCore.framework/Resources"
  #create symlinks
  ln -s "Versions/4/Resources" "SimpleHello.app/Contents/Frameworks/QtCore.framework/Resources"
  

  之后，我使用：

  codesign --deep -f -s
  

  它工作正常，只需以类似的方式添加缺少的框架。我没有用 qt 5 尝试过，但它可能适用于它。

  回复于 2024-04-19T15:48:59+08:00