Thanks, Eike, for the comprehensive explanation: added much more info and in more correct way than before to KitDataSource. Only 2 questions:
- I see DebuggerItem allows to get debugger version via QString version() const method, is there something similar for compiler? I see such information is absent in ToolChain class. - ToolChain class allows to get cxxLanguageVersion() or languageVersion(), however not sure what arguments are for these methods? Also they are return enums, good to have QString() analogues - are there something available? -- Best regards, Aleksey Linked in https://www.linkedin.com/in/alekseykontsevich 10.10.2018, 10:53, "Eike Ziller" <eike.zil...@qt.io>: >> On 7. Oct 2018, at 23:53, Aleksey Kontsevich <tantr...@ya.ru> wrote: >> >> Hi Eike, >> >> I see there is no documentation about QtSupport namesapce or >> QtKitInformation? >> >> Also it is not clear how to get other information like: >> - compiler > > e.g. > ToolChainKitInformation::toolChain(kit, > ProjectExplorer::Constants::CXX_LANGUAGE_ID) > >> - debugger > > DebuggerKitInformation::debugger(kit) > >> - target platform > > Possibly DeviceTypeKitInformation::deviceTypeId(kit) > >> - make system (qmake, qbs, cmake, etc) > > Possibly something like SessionManager::projects() + project->id() (which is > more a type ID) > >> Could You provide more info please? Thanks! >> >> -- >> Best regards, >> Aleksey >> Linked in https://www.linkedin.com/in/alekseykontsevich >> >> 12.09.2018, 14:20, "Eike Ziller" <eike.zil...@qt.io>: >>> If your question is about kits, generally the KitManager provides the list >>> of defined Kits. >>> Kits are composed of data generated by KitInformation classes. >>> A specific KitInformation class can be used to provide specific info about >>> a kit, e.g. QtKitInformation::qtVersion(kit) returns the Qt version >>> specified in the kit. >>> >>> Br, Eike >>> >>>> On 11. Sep 2018, at 14:29, Aleksey Kontsevich <tantr...@ya.ru> wrote: >>>> >>>> Hi all, >>>> >>>> I need to implement KitDataSource for new ConnectedCreatorPlugin which >>>> will be officially shipped with QtC distribution. This data source gather >>>> information about compilers, platforms, target platforms, debuggers, etc >>>> used by a QtC user. I've found ProjectExplorer Namespace documentation >>>> (https://doc-snapshots.qt.io/qtcreator-extending/projectexplorer.html#namespaces) >>>> with classes which contains this information however documentation is >>>> still very poor and there are very many classes so it is not quite clear >>>> which one to use, how to use and how they are connected to each other. So >>>> question is: >>>> - how better organize these information gathering >>>> - which classes to use >>>> - which signals, methods >>>> - when to gather the information: on a project open, kit setup, etc? >>>> >>>> Gould you guide me a little on this please? Thanks! >>>> >>>> -- >>>> Best regards, >>>> Aleksey >>>> Linked in https://www.linkedin.com/in/alekseykontsevich >>>> _______________________________________________ >>>> Qt-creator mailing list >>>> Qt-creator@qt-project.org >>>> http://lists.qt-project.org/mailman/listinfo/qt-creator >>> >>> -- >>> Eike Ziller >>> Principal Software Engineer >>> >>> The Qt Company GmbH >>> Rudower Chaussee 13 >>> D-12489 Berlin >>> eike.zil...@qt.io >>> http://qt.io >>> Geschäftsführer: Mika Pälsi, >>> Juha Varelius, Mika Harjuaho >>> Sitz der Gesellschaft: Berlin, Registergericht: Amtsgericht >>> Charlottenburg, HRB 144331 B > > -- > Eike Ziller > Principal Software Engineer > > The Qt Company GmbH > Rudower Chaussee 13 > D-12489 Berlin > eike.zil...@qt.io > http://qt.io > Geschäftsführer: Mika Pälsi, > Juha Varelius, Mika Harjuaho > Sitz der Gesellschaft: Berlin, Registergericht: Amtsgericht Charlottenburg, > HRB 144331 B _______________________________________________ Qt-creator mailing list Qt-creator@qt-project.org http://lists.qt-project.org/mailman/listinfo/qt-creator
