1. 08 Jan, 2015 10 commits
  2. 07 Jan, 2015 23 commits
  3. 06 Jan, 2015 7 commits
    • Marco Bubke's avatar
      Ignore code coverage files · d9b3c99c
      Marco Bubke authored
      Change-Id: I6f97356af49f6f6ffa0241f2b527c1bf33b0a279
      Reviewed-by: default avatarTim Jenssen <tim.jenssen@theqtcompany.com>
    • Christian Stenger's avatar
      BareMetal: Fix compile for older compiler · b71462d4
      Christian Stenger authored
      Introduced with 165f008d
      Change-Id: Idc5b00313de807857bcd4deaaf99cabf95e81c6a
      Reviewed-by: default avatarhjk <hjk@theqtcompany.com>
    • Tobias Hunger's avatar
      Svn: Fix warning about overriding virtual methods · ece37338
      Tobias Hunger authored
      ... with a method that has different arguments.
      Change-Id: Iae3238d8feeb2602cb4ab39502a74f039c850933
      Reviewed-by: Orgad Shaneh's avatarOrgad Shaneh <orgads@gmail.com>
    • Tobias Hunger's avatar
      Fix clang warning about uninitialized variable · 1a89f7c7
      Tobias Hunger authored
      Change-Id: I9cdfa51dadf1014ee21a37ed97f4c543eb5c8fbb
      Reviewed-by: default avatarChristian Kandeler <christian.kandeler@theqtcompany.com>
    • hjk's avatar
      Welcome: clean up welcomeplugin.cpp · 0be4f01c
      hjk authored
      Namespaces, style, dead code, unneeded comments, ...
      Change-Id: Iaad9623c2c0c1f0ca76d604d493f406f23a6acf2
      Reviewed-by: default avatarChristian Stenger <christian.stenger@theqtcompany.com>
      Reviewed-by: default avatarThomas Hartmann <Thomas.Hartmann@digia.com>
    • Denis Shienkov's avatar
      BareMetal: Allow to manage configurations of HW GDB servers · 165f008d
      Denis Shienkov authored
      The user has only one possibility to setup of the remote GDB server
      when a new device is created (or to modify it for existing device).
      It is possible only in the host/port fields for connection to the
      GDB server. It is a little inconvenient for the user. If the user
      wants to use other configuration of the GDB server, then need every
      time to edit the current configuration.
      Improving this it is introduction a new concept with a new entity
      named as "GDB server provider". Now to the device debugging purpose
      the user can choose any of the GDB provider from the list (by analogy
      with toolchain and so on). Each configuration of GDB provider is
      created by the user manually on the new "GDB Server Provider" options
      page. This can be made before or after creation of device.
      A GDB server provider can work in three startup modes (depends on
      implementation of concrete provider):
      1) NoStartup mode.
      This means that we do not want to startup a provider, we just trying
      to connect to the already started GDB provider server. This mode uses
      the TCP/IP connection with manually specifying of remote host and port.
      2) StartupOnNetwork mode.
      This means that we want to launch of the GDB provider automatically
      before connect to it in process of remote debugging. This mode also
      uses the TCP/IP protocol. In addition to it, a GDB provider can has
      additional options which are contains a paths to provider executable
      file, to configuration files and so on (it is depends on concrete
      provider implementation). This mode (with NoStartup) covers about 90%
      of usecase, and is supported by most set of the GDB server providers.
      3) StartupOnPipe mode.
      This is similar to StartupOnNetwork mode and we also automatically
      starts the GDB server provider before debugging. But in this case is
      used the Pipe mode instead of TCP/IP. Not each of the GDB provider
      can support debugging via pipes.
      This patch has concrete implementations for a following set of the
      GDB server providers:
      * "Default" provider which supports only the NoStartup mode.
      * "Open On-Chip Debugger" (http://openocd.sourceforge.net/)
        provider which supports all modes.
      * "STLinkUtil" (https://github.com/texane/stlink
        provider which supports NoStartup and StartupOnNetwork modes.
      Tested on Windows and Linux with:
      * target HW: ARM Stm32F4Discovery board with HW debugger STLink-v2
      * provider: OpenOCD v0.8.0 (tested on Windows and Linux)
      * provider: STLink-Util (tested on Linux only)
      * toolchain: ARM GCC v4.9.2
      * debugger: GDB v7.8.1 (with Python support)
      * QtCreator with QBS project
      Task-number: QTCREATORBUG-13686
      Change-Id: I59c775d91b0a4227d931188879850c536290e1ba
      Reviewed-by: default avatarLeena Miettinen <riitta-leena.miettinen@theqtcompany.com>
      Reviewed-by: default avatarhjk <hjk@theqtcompany.com>
    • Thomas Hartmann's avatar
      QmlDesigner.PropertyEditor: Fix control for saturation · bced09cd
      Thomas Hartmann authored
      If the lightness or saturation are 0 then hue is undefined.
      If lightness is 0 then saturation is undefined/0.
      Nevertheless we should keep the old values in the ui, because
      the user should not loose the values in case he increases lightness
      or saturation later.
      Change-Id: I9fd80f6ca84fa08ef62d9fbb6dd4afce992c3546
      Reviewed-by: default avatarTim Jenssen <tim.jenssen@theqtcompany.com>