Uploaded image for project: 'Qt'
  1. Qt
  2. QTBUG-41611

macdeployqt should also deploy QtWebEngineProcess and required files

    XMLWordPrintable

Details

    • Bug
    • Resolution: Done
    • P1: Critical
    • 5.4.0
    • 5.4.0 Alpha
    • None
    • OSX 10.9 and 10.10.
    • 66cd31938c4dc97a32a094d3906c21ecdd034f95 8af12f0c9ee0cfdf28f557e96086bb7b08d786bc (QtWebEngine) 5060a0ec7dcb26826b19eefbd6063efcbde6101f (macdeployqt)

    Description

      If your application includes QtWebEngine the macdeployqt application should also deploy QtWebEngineProcess and the support files needed. Currently this needs to be done manually.

      FOR 5.4 YOU MUST RUN macdeployqt THE FOLLOWING WAY:

      > macdeployqt <TARGET>.app -executable=<TARGET>.app/Contents/MacOS/<TARGET>

      macdeployqt only uses @loader_path when the -executable switch is non-empty, so passing an arbitrary exectable there triggers the behavior we need to let QtWebEngineProcess use the same Qt binaries as the main application executable. The won't be necessary once we support using @rpath, which should be done in Qt 5.5.0.

      Attachments

        Issue Links

          No reviews matched the request. Check your Options in the drop-down menu of this sections header.

          Activity

            People

              jturcott Jocelyn Turcotte
              tobiashieta Tobias Hieta
              Votes:
              0 Vote for this issue
              Watchers:
              13 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved:

                Gerrit Reviews