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

Android: Some Qt modules get broken install rules on Windows

    XMLWordPrintable

Details

    • Bug
    • Resolution: Done
    • P1: Critical
    • 5.3.0 RC1
    • 5.3.0 Beta1
    • QPA
    • None
    • Android
    • a162a3cbbc3c27b42c86f870aba051a408f04ed4

    Description

      This is reproducible e.g. when cross-compiling the Qt Purchasing API for Android on Windows, but it has also been reported for other external modules.

      The Makefile gets the following in its "install_target":

      install_target: first FORCE
      [...]
              -$(INSTALL_PROGRAM) "..\..\lib\$(TARGET)" "D:$(INSTALL_ROOT)\releasetesting\5.3.0beta\5.3\android_armv7\lib\$(TARGET)"
              -$(SYMLINK) "$(TARGET)" "D:$(INSTALL_ROOT)\releasetesting\5.3.0beta\5.3\android_armv7\lib\$(TARGET0)"
              -$(SYMLINK) "$(TARGET)" "D:$(INSTALL_ROOT)\releasetesting\5.3.0beta\5.3\android_armv7\lib\$(TARGET1)"
              -$(SYMLINK) "$(TARGET)" "D:$(INSTALL_ROOT)\releasetesting\5.3.0beta\5.3\android_armv7\lib\$(TARGET2)"
      

      The $(TARGET), which is libQt5FooBar.so.5.3.0, is correctly installed from "../../lib", but the subsequent rules for the symlinks try to get $(TARGET) from the current directory, and fail. On Android, the libQt5FooBar.so is the only one that matters, so applications using the module will fail on startup since this library is not found.

      Attachments

        Issue Links

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

          Activity

            People

              esabraha Eskil Abrahamsen Blomfeldt
              esabraha Eskil Abrahamsen Blomfeldt
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved:

                Gerrit Reviews

                  There are no open Gerrit changes