1. 13 May, 2013 - 2 commits
  2. 10 May, 2013 - 1 commit
    • Matt Fischer's avatar
      Improve support for <MODULE>_PATH options · d37dc751
      Matt Fischer authored
      
      Several modules, including DBus, MySQL, and OpenSSL have
      configure options of the form <MODULE>_PATH, which is used
      on Windows (where pkg-config is not present) to specify the
      locations of third-party libraries.  These switches had been
      implemented by adding extra variables which were referenced
      in .pro files, to add the appropriate compiler and linker
      switches.  This is undesirable because it means there are
      two independent paths for adding the switches to the build,
      which can get out of sync with each other, and indeed this
      had happened for some of the DBus tools.
      
      To remedy the situation, all three of the switches were
      reworked so that they added values directly to the principal
      variables that are used in the project files.  This reduces
      maintenance, by ensuring that the pkg-config and non-pkg-config
      paths appear the same to the rest of the build system.
      
      Change-Id: Iae342f1d14b79fbcfef9fe38aadc803ad3141799
      Reviewed-by: default avatarOswald Buddenhagen <oswald.buddenhagen@digia.com>
      d37dc751
  3. 09 May, 2013 - 1 commit
  4. 22 Apr, 2013 - 1 commit
  5. 15 Apr, 2013 - 1 commit
  6. 08 Apr, 2013 - 1 commit
  7. 02 Apr, 2013 - 1 commit
  8. 28 Mar, 2013 - 1 commit
  9. 26 Mar, 2013 - 1 commit
  10. 20 Mar, 2013 - 1 commit
  11. 15 Mar, 2013 - 1 commit
  12. 12 Mar, 2013 - 1 commit
  13. 28 Feb, 2013 - 1 commit
  14. 27 Feb, 2013 - 1 commit
  15. 20 Feb, 2013 - 2 commits
  16. 19 Feb, 2013 - 1 commit
  17. 18 Feb, 2013 - 1 commit
  18. 15 Feb, 2013 - 1 commit
    • Kai Koehne's avatar
      Place libexec binaries into lib folder on Windows · 3f471c06
      Kai Koehne authored
      
      Change the default libexec directory to 'lib' on Windows for default
      configurations. This makes sure that e.g. qtwebprocess can actually
      find & load the right Qt libs.
      
      A separate libexec directory was introduced to avoid conflicts between
      a system-wide Qt in PATH and a custom Qt installation. However, since
      there are no system wide Qt installations on Windows this isn't an
      issue, but getting the executables to find its Qt libraries is.
      
      Alternatively we could have also placed it in the 'bin' directory.
      However, putting it in the 'lib' folder carries the notion that,
      unlike the binaries in the bin, the libexec executables might have
      to be deployed with a target application.
      
      The exception is when a separate archdata prefix is specified, and
      $$archdata/lib won't contain Qt libraries. In this case we use libexec
      like on the other platforms too.
      
      ChangeLog: [Qt for Windows] Fixed launching of QtWebProcess.exe by
      changing default libexec directory to 'lib'.
      Task-number: QTBUG-29661
      Change-Id: Icbb15fb98474d6fef8ac9310f2e2b482d3282f79
      Reviewed-by: default avatarOswald Buddenhagen <oswald.buddenhagen@digia.com>
      Reviewed-by: default avatarJocelyn Turcotte <jocelyn.turcotte@digia.com>
      Reviewed-by: default avatarJoerg Bornemann <joerg.bornemann@digia.com>
      3f471c06
  19. 11 Feb, 2013 - 1 commit
  20. 01 Feb, 2013 - 2 commits
  21. 28 Jan, 2013 - 1 commit
  22. 24 Jan, 2013 - 1 commit
  23. 23 Jan, 2013 - 1 commit
  24. 18 Jan, 2013 - 1 commit
  25. 11 Jan, 2013 - 1 commit
  26. 04 Jan, 2013 - 1 commit
  27. 18 Dec, 2012 - 1 commit
  28. 11 Dec, 2012 - 1 commit
  29. 10 Dec, 2012 - 1 commit
    • Miikka Heikkinen's avatar
      Add QT_DEFAULT_QPA_PLUGIN to generated qconfig.pri · 903fa2e4
      Miikka Heikkinen authored
      
      Configure will now generate QT_DEFAULT_QPA_PLUGIN qmake variable
      to specify the default QPA plugin.
      
      "CONFIG += qpa_default_plugin" statement in application .pro file
      will add the default QPA plugin into QTPLUGINS.
      
      "CONFIG += qpa_minimal_plugin" statement in application .pro file
      will add the minimal QPA plugin into QTPLUGINS.
      
      Task-number: QTBUG-28131
      Change-Id: I12a241005f30b37467d783b50f0369b47e605e68
      Reviewed-by: default avatarOswald Buddenhagen <oswald.buddenhagen@digia.com>
      903fa2e4
  30. 06 Dec, 2012 - 2 commits
  31. 05 Dec, 2012 - 1 commit
  32. 30 Nov, 2012 - 2 commits
  33. 28 Nov, 2012 - 1 commit
    • Thiago Macieira's avatar
      Add a -libexecdir option to the configures · 5dcc36b1
      Thiago Macieira authored
      
      User applications are those that users run directly, whether it be for
      development or not. The executable binaries that the user does not
      usually run but is still required for proper functioning are called
      "program executables" in Autoconf and they are placed in libexec.
      
      This commit adds support for "program executables" in Qt by adding the
      -libexecdir option to the configures, the qmake variable
      QT_INSTALL_LIBEXECS (note the plural, to match all other properties),
      and QLibraryInfo::LibraryExecutables.
      
      At the time of this commit, the only expected "program executable" is
      the QtWebProcess, the WebKit2 helper process from QtWebKit.
      
      Change-Id: I66c3a3e0cf7f9d93b5f88f55f18e957faff608fc
      Reviewed-by: default avatarLars Knoll <lars.knoll@digia.com>
      5dcc36b1
  34. 19 Nov, 2012 - 1 commit
  35. 16 Nov, 2012 - 1 commit