+1 Another aspect of this issue is that it is not possible to specify the server when initiating 'remote debug' (through the "Attach to remote debug server..." action). The only possibility is to create a kit for this purpose only, which is not appropriate IMHO. Especially for embedded projects, i usually connect to systems which do not have SSH, so I cannot even setup a generic target: the solution with earlier versions was to manually attach to remote gdb server, but this is not working anymore with 2.6.
While i generally agree with the kit approach to associate a device (or possibly kind of device) to a build configuration, i don't think the same approach should be used when starting the debugger in a non-standard way. In that case, we should have more flexibility, like in previous QtCreator releases. Best regards, -- Francois On Tue, Nov 13, 2012 at 4:24 PM, Konstantin Tokarev <[email protected]>wrote: > > 12.11.2012, 13:17, "Orgad Shaneh" <[email protected]>: > > Hello,Kits are currently associated with a specific device. That implies > a device-kit 1-n relationship (a single device relates to n kits). > > This looks wrong. In case the user has several identical devices, why > would he need to configure build configuration for each of them? > > IMHO kits should only have device type. The device should be taken out > of kit configuration, and be re-added in run configuration and in debugger > dialogs (filtering devices by the kit's device type). > > +1 from me. > > -- > Regards, > Konstantin > _______________________________________________ > Qt-creator mailing list > [email protected] > http://lists.qt-project.org/mailman/listinfo/qt-creator >
_______________________________________________ Qt-creator mailing list [email protected] http://lists.qt-project.org/mailman/listinfo/qt-creator
