Skip to content
Snippets Groups Projects
  1. Jan 26, 2017
  2. Jan 19, 2017
  3. Jan 17, 2017
  4. Jan 16, 2017
  5. Jan 13, 2017
  6. Jan 12, 2017
  7. Jan 11, 2017
  8. Jan 10, 2017
  9. Jan 06, 2017
  10. Jan 05, 2017
  11. Jan 02, 2017
    • Kari Oikarinen's avatar
      Change USB vendor ID used by qdbd · 6dc4f687
      Kari Oikarinen authored
      
      Rather than using Google's ID, let's pick an unused one.
      
      We are not reserving an official USB vendor ID, since this is only used
      for development and Qt for Device Creation users will use their own USB
      IDs in the final devices.
      
      Also always use a fixed product ID, since ADB_PRODUCTID value will make
      no sense with the changed vendor ID.
      
      Change-Id: I69ed1bcfbe3e17b5faebf4b3b71f691778776da7
      Reviewed-by: default avatarMikko Gronoff <mikko.gronoff@qt.io>
      Reviewed-by: default avatarSamuli Piippo <samuli.piippo@qt.io>
      6dc4f687
  12. Dec 22, 2016
  13. Dec 20, 2016
  14. Dec 19, 2016
  15. Dec 16, 2016
  16. Dec 14, 2016
  17. Dec 09, 2016
  18. Dec 01, 2016
  19. Nov 29, 2016
  20. Nov 23, 2016
  21. Nov 21, 2016
    • Mikko Gronoff's avatar
      qt5: update submodules · 9e2f18f4
      Mikko Gronoff authored
      
      Change-Id: I5ac8a0f31b2553575cbab782cb2ed8a7e42f4eea
      Reviewed-by: default avatarSamuli Piippo <samuli.piippo@qt.io>
      9e2f18f4
    • Samuli Piippo's avatar
      Add support for creating QBSP package · 1a9ad489
      Samuli Piippo authored
      
      QBSP is a Qt specific Board Support Package that can be installed with
      the Qt SDK or MaintenanceTool and contains a system image and a toolchain.
      The toolchain is automatically registered to the QtCreator.
      
      The recipes used for creating the system image and the toolchain can be
      configured with QBSP_IMAGE_TASK and QBSP_SDK_TASK. The files wanted for
      the system image can be further configured with QBSP_IMAGE_CONTENT,
      with a list of files located in DEPLOY_DIR_IMAGE folder. By default,
      .img and .conf files are used from the selected image recipe.
      
      QBSP_INSTALLER_COMPONENT defines the location in the Qt installer tree
      where the QBSP is shown and QBSP_VERSION defines the version for the
      components. The QBSP is installed to path defined by QBSP_INSTALL_PATH.
      
      The regular SDK creation can now reuse the same image package .7z, so
      update upload script to use it instead of creating new package.
      
      Task-number: QTBUG-57018
      Change-Id: Id1e7cc4ab3998a7d450f23ed603b8e676b314d63
      Reviewed-by: default avatarIikka Eklund <iikka.eklund@qt.io>
      Reviewed-by: default avatarTeemu Holappa <teemu.holappa@qt.io>
      1a9ad489
    • Samuli Piippo's avatar
      beaglebone: start qtlauncher only after /dev/fb0 exists · cbb95021
      Samuli Piippo authored
      
      Beaglebone creates /dev/fb0 late in the boot process, which causes
      Qt applications to crash if started too early. Make systemd notice
      fb0 creation and bind application startup to it.
      
      (cherry picked from commit 300a9420)
      Change-Id: I8875334407c5a01bd6597e2c4fc1af96e396c639
      Reviewed-by: default avatarKalle Viironen <kalle.viironen@theqtcompany.com>
      cbb95021
  22. Nov 17, 2016
  23. Nov 14, 2016
  24. Nov 11, 2016
  25. Nov 10, 2016
  26. Nov 04, 2016
  27. Nov 03, 2016
    • Samuli Piippo's avatar
      images: do not explicitly define Qt dependency packages · 57f2d6e8
      Samuli Piippo authored
      
      Remove all Qt dependency packages from machine include files and
      base packagegroups, instead let packagemanager pull in all the
      needed dependent packages. Do not create tar image or bootfs, since
      they are not used anymore.
      
      The old base image is now renamed for CI usage and contains all the
      Qt dependent packages but without any Qt modules. This is achieved
      by first installing all the Qt modules (which pulls in all the
      dependencies) and then removing only Qt modules.
      
      Change-Id: I36d996d4531af42e955f19a487c22d0b90c5ada9
      Reviewed-by: default avatarRisto Avila <risto.avila@qt.io>
      57f2d6e8
    • Samuli Piippo's avatar
      sdk: do not explicitly define Qt dependency packages · d1014d8b
      Samuli Piippo authored
      
      Until now, the toolchain used by CI has been created without Qt, but with
      all (best guess) Qt dependencies. Now toolchain is created with Qt and we
      get all Qt dependencies correctly into the toolchain. As a consequence,
      CI will now need to build Qt, which has not been covered in CI before.
      
      The difference between embedded-sdk and embedded-qt5-sdk is that
      the former does not include files needed for debugging.
      
      Change-Id: Ie2be156c07e51119c0d4782494d6bcde6f34ed60
      Reviewed-by: default avatarRisto Avila <risto.avila@qt.io>
      d1014d8b
Loading