mirrors/cdt
1
0
Fork 0
mirror of https://github.com/eclipse-cdt/cdt synced 2025-06-07 09:46:02 +02:00
Code Issues Wiki Activity
cdt/qt/org.eclipse.cdt.qt.core/plugin.xml

226 lines
8.4 KiB
XML
Raw Normal View History

Added support for Qt. Extended AddFiles template to change start/end patterns.
2013-01-12 00:54:08 -05:00
<?xml version="1.0" encoding="UTF-8"?>
<?eclipse version="3.4"?>
<plugin>
Tighter integration of new build system with cdt.core. Move the new build system to cdt.core and remove the previous plugins. Hook the new system into scanner info and environment variable manager. Clean up API in preparation for Neon and API lockdown. Hook up Qt to the new APIs. Add discovery of MSYS2's toolchain and Qt and Qt's MinGW toolchain. Change-Id: I85b1a91da4a44e86f0e9da9310f8106c894623e0
2016-03-31 11:28:28 -04:00
<extension-point id="qtInstallProvider" name="Qt Install Provider" schema="schema/qtInstallProvider.exsd"/>
<extension-point id="qtToolChainMapper" name="Qt ToolChain Mapper" schema="schema/qtToolChainMapper.exsd"/>
Bug 422797 - API for retrieving QMake information from Qt project API is located at org.eclipse.cdt.qt.core.index package. Entry point is QMakeProjectInfoFactory.getForActiveConfigurationIn method that provides ability to retrieve QMake information (IQMakeInfo interface) for active project configuration of a specified project. Also allows to listen on changes of such information. qmakeEnvProvider extensions allows CDT build-system to provide environment for QMake runs within their build-system. Information is gather by parsing output of: 1) qmake -query 2) qmake -E file.pro // only for QMake version 3.0 Change-Id: Iae569bdbc89dc26d60530596b66b5227f36dfae6 Signed-off-by: David Kaspar <dkaspar@blackberry.com> Reviewed-on: https://git.eclipse.org/r/19082 Reviewed-by: Andrew Eidsness <eclipse@jfront.com> Tested-by: Hudson CI Reviewed-by: Doug Schaefer <dschaefer@qnx.com> IP-Clean: Doug Schaefer <dschaefer@qnx.com>
2013-11-28 19:58:37 +01:00
Added support for Qt. Extended AddFiles template to change start/end patterns.
2013-01-12 00:54:08 -05:00
<extension
point="org.eclipse.cdt.core.templates">
Bug 418406: Qt4 and Qt5 specific HelloWorld project wizards This replaces the QtQuick2 project wizard with Qt4 and Qt5 wizards that include the old content as well as: 1) Make targets to build and clean the project 2) Sample interaction between C++ and QML 3) A Qt header path provider so that paths from the Qt installation are properly resolved in the project. Item 3 is particularly important for using the 'New Class' wizard with QObject as the base class. Unless the Qt paths are pre-populated the QObject base class will not be found and the New Class wizard's Finish button will be disabled. The Qt headers are resolved by running `qmake -query QT_INSTALL_HEADERS` and then creating IncludePath entries for all sub-folders. This list of include paths is persisted with other shared language settings into a file in the workspace metadata area. The persisted data is reloaded when any of the following change: - the modification time of the qmake binary - the modification time of the reported QT_INSTALL_HEADERS folder The persisted node is ignored when the target qmake binary no longer exists. The node is removed from the persisted form the next time that the shared settings are persisted. Change-Id: Ic82fdb147e6a69060f93e2e9aed2e919139a0ae9 Signed-off-by: Andrew Eidsness <eclipse@jfront.com> Reviewed-on: https://git.eclipse.org/r/16909 Reviewed-by: Doug Schaefer <dschaefer@qnx.com> IP-Clean: Doug Schaefer <dschaefer@qnx.com> Tested-by: Doug Schaefer <dschaefer@qnx.com>
2013-10-23 07:12:25 -04:00
<template
filterPattern=".*g\+\+"
id="org.eclipse.cdt.qt.core.template.helloWorld.Qt5"
location="templates/project/Qt5/template.xml"
projectType="org.eclipse.cdt.build.makefile.projectType"/>
Added support for Qt. Extended AddFiles template to change start/end patterns.
2013-01-12 00:54:08 -05:00
</extension>
<extension
point="org.eclipse.cdt.core.templateAssociations">
Bug 418406: Qt4 and Qt5 specific HelloWorld project wizards This replaces the QtQuick2 project wizard with Qt4 and Qt5 wizards that include the old content as well as: 1) Make targets to build and clean the project 2) Sample interaction between C++ and QML 3) A Qt header path provider so that paths from the Qt installation are properly resolved in the project. Item 3 is particularly important for using the 'New Class' wizard with QObject as the base class. Unless the Qt paths are pre-populated the QObject base class will not be found and the New Class wizard's Finish button will be disabled. The Qt headers are resolved by running `qmake -query QT_INSTALL_HEADERS` and then creating IncludePath entries for all sub-folders. This list of include paths is persisted with other shared language settings into a file in the workspace metadata area. The persisted data is reloaded when any of the following change: - the modification time of the qmake binary - the modification time of the reported QT_INSTALL_HEADERS folder The persisted node is ignored when the target qmake binary no longer exists. The node is removed from the persisted form the next time that the shared settings are persisted. Change-Id: Ic82fdb147e6a69060f93e2e9aed2e919139a0ae9 Signed-off-by: Andrew Eidsness <eclipse@jfront.com> Reviewed-on: https://git.eclipse.org/r/16909 Reviewed-by: Doug Schaefer <dschaefer@qnx.com> IP-Clean: Doug Schaefer <dschaefer@qnx.com> Tested-by: Doug Schaefer <dschaefer@qnx.com>
2013-10-23 07:12:25 -04:00
<template id="org.eclipse.cdt.qt.core.template.helloWorld.Qt5">
Added support for Qt. Extended AddFiles template to change start/end patterns.
2013-01-12 00:54:08 -05:00
<toolChain id="cdt.managedbuild.toolchain.gnu.mingw.base"/>
<toolChain id="cdt.managedbuild.toolchain.gnu.base"/>
Bug 418406: Qt4 and Qt5 specific HelloWorld project wizards This replaces the QtQuick2 project wizard with Qt4 and Qt5 wizards that include the old content as well as: 1) Make targets to build and clean the project 2) Sample interaction between C++ and QML 3) A Qt header path provider so that paths from the Qt installation are properly resolved in the project. Item 3 is particularly important for using the 'New Class' wizard with QObject as the base class. Unless the Qt paths are pre-populated the QObject base class will not be found and the New Class wizard's Finish button will be disabled. The Qt headers are resolved by running `qmake -query QT_INSTALL_HEADERS` and then creating IncludePath entries for all sub-folders. This list of include paths is persisted with other shared language settings into a file in the workspace metadata area. The persisted data is reloaded when any of the following change: - the modification time of the qmake binary - the modification time of the reported QT_INSTALL_HEADERS folder The persisted node is ignored when the target qmake binary no longer exists. The node is removed from the persisted form the next time that the shared settings are persisted. Change-Id: Ic82fdb147e6a69060f93e2e9aed2e919139a0ae9 Signed-off-by: Andrew Eidsness <eclipse@jfront.com> Reviewed-on: https://git.eclipse.org/r/16909 Reviewed-by: Doug Schaefer <dschaefer@qnx.com> IP-Clean: Doug Schaefer <dschaefer@qnx.com> Tested-by: Doug Schaefer <dschaefer@qnx.com>
2013-10-23 07:12:25 -04:00
<toolChain id="cdt.managedbuild.toolchain.llvm.clang.macosx.base"/>
Added support for Qt. Extended AddFiles template to change start/end patterns.
2013-01-12 00:54:08 -05:00
</template>
</extension>
Added content types for .pro and .qml files for Qt.
2013-01-12 16:10:21 -05:00
<extension
point="org.eclipse.core.contenttype.contentTypes">
<content-type
base-type="org.eclipse.core.runtime.text"
file-extensions="pro"
id="qtProjectFile"
name="%qtProjectFile.name"
priority="normal">
</content-type>
<content-type
base-type="org.eclipse.core.runtime.text"
file-extensions="qml"
id="qmlFile"
name="%qmlFile.name"
priority="normal">
</content-type>
Bug 478231 - Hook up .qrc files to the XML Editor Change-Id: I41b8e07474b608d8311fbc3f117f9386e73b5305 Signed-off-by: Matthew Bastien <mbastien@blackberry.com>
2015-09-23 16:51:29 -04:00
<content-type
base-type="org.eclipse.core.runtime.xml"
file-extensions="qrc"
id="qrcFile"
name="%qrcFile.name"
priority="normal">
</content-type>
Added content types for .pro and .qml files for Qt.
2013-01-12 16:10:21 -05:00
</extension>
Added template process to add nature. Added Qt nature.
2013-01-17 15:20:49 -05:00
<extension
id="qtNature"
point="org.eclipse.core.resources.natures">
<runtime>
<run
Start of work on doing Qt the new way. Change-Id: Icc891538549485f9ad99614f36262ed218fb0609
2015-08-26 16:58:18 -04:00
class="org.eclipse.cdt.internal.qt.core.QtNature">
Added template process to add nature. Added Qt nature.
2013-01-17 15:20:49 -05:00
</run>
</runtime>
Start of work on doing Qt the new way. Change-Id: Icc891538549485f9ad99614f36262ed218fb0609
2015-08-26 16:58:18 -04:00
<builder
id="org.eclipse.cdt.qt.core.qtBuilder">
</builder>
Added template process to add nature. Added Qt nature.
2013-01-17 15:20:49 -05:00
</extension>
qt slot/signal auto-complete Tags signal and slot methods when the index is created. Uses these tags to suggest values inside of SIGNAL and SLOT macro expansions. Enabled only for projects with the QtNature. Recognizes QObject::connect function calls and suggests SIGNAL(a) and SLOT(a) for the 2nd and 4th parameters. When expanding the SIGNAL and SLOT macros within a call to QObject::connect, suggests signals and slots based on the type of the previous parameter. E.g. in QObjectA a; QObjectB b; QObject::connect( &a, SIGNAL(*), &b, SLOT(**) ); The content assistant will suggest the methods of type QObjectA that have been marked as signals at *, and the methods of QObjectB that have been marked as slots at **. Change-Id: Ia6aaa71724547b0977e322399a500f072004767a Reviewed-on: https://git.eclipse.org/r/10532 Reviewed-by: Doug Schaefer <dschaefer@qnx.com> IP-Clean: Doug Schaefer <dschaefer@qnx.com> Tested-by: Doug Schaefer <dschaefer@qnx.com>
2013-02-20 13:23:40 -05:00
<extension
Bug 422841: Initial implementation of QtIndex This uses the new PDOMASTProcessor extension point to create a Qt-specifc PDOMLinkage. This initial version of the linkage only stores QObjects and their base classes. Later commits will fill out other details and introduce classes that use this data for things like Content Assistance and Codan checking. This patch introduces the following: 1) QtIndex: This is an index that provides access to Qt-specific data. The index is mostly a wrapper on the CDT's existing IIndex, but it provides very specific information about the Qt elements. The only data that can be accessed from the QtIndex (in this patch) is a QObject and the QObject's that appear in its base class specifier list. 2) QtPDOMLinkage: This linkage is implemenated as an extension of the PDOMCPPLinkage. In some cases it adds references to Qt names from the C++ bindings. 3) Test suite: The test suite has some base classes for parsing the Qt source code. The only test case is for the simple functionality that is being added in this patch -- examining the base class specifier list of QObjects. These areas will be extended in later patches. Change-Id: I13fb83beb7f50cd2efb1de97b562245dc642468d Signed-off-by: Andrew Eidsness <eclipse@jfront.com> Reviewed-on: https://git.eclipse.org/r/19113 Tested-by: Hudson CI Reviewed-by: Doug Schaefer <dschaefer@qnx.com> IP-Clean: Doug Schaefer <dschaefer@qnx.com>
2013-11-29 08:28:51 -05:00
point="org.eclipse.cdt.core.PDOMASTProcessor"
id="qt.PDOMASTProcessor"
name="Qt PDOM AST Processor">
<processor
Fix Qt plugin's project structure The Qt plugins have been naming internal packages using two different prefixes: cdt.qt.internal cdt.internal.qt This renames all packages to cdt.internal.qt, which seems to be the convention for other projects. I've increased the Qt plugin versions because alot of new API has been added, especially to the qt.core plugin. I increased the version in the MANIFEST.MF and pom.xml files. I've also fixed the MANIFEST.MF files to take CDT out of the plugin names. I've also replaced a call to CCorePlugin.log(Exception) with a call to QtUIPlugin.log (and added the logging functions to QtUIPlugin. Change-Id: I1e3e7b2a42c2eb79fe33608c14a1abcf013a9f2c Signed-off-by: Andrew Eidsness <eclipse@jfront.com> Reviewed-on: https://git.eclipse.org/r/19698 Tested-by: Hudson CI Reviewed-by: Doug Schaefer <dschaefer@qnx.com> IP-Clean: Doug Schaefer <dschaefer@qnx.com>
2013-12-12 07:40:51 -05:00
class="org.eclipse.cdt.internal.qt.core.pdom.QtPDOMASTProcessor">
qt slot/signal auto-complete Tags signal and slot methods when the index is created. Uses these tags to suggest values inside of SIGNAL and SLOT macro expansions. Enabled only for projects with the QtNature. Recognizes QObject::connect function calls and suggests SIGNAL(a) and SLOT(a) for the 2nd and 4th parameters. When expanding the SIGNAL and SLOT macros within a call to QObject::connect, suggests signals and slots based on the type of the previous parameter. E.g. in QObjectA a; QObjectB b; QObject::connect( &a, SIGNAL(*), &b, SLOT(**) ); The content assistant will suggest the methods of type QObjectA that have been marked as signals at *, and the methods of QObjectB that have been marked as slots at **. Change-Id: Ia6aaa71724547b0977e322399a500f072004767a Reviewed-on: https://git.eclipse.org/r/10532 Reviewed-by: Doug Schaefer <dschaefer@qnx.com> IP-Clean: Doug Schaefer <dschaefer@qnx.com> Tested-by: Doug Schaefer <dschaefer@qnx.com>
2013-02-20 13:23:40 -05:00
<enablement>
<with variable="projectNatures">
<iterate operator="or">
<equals value="org.eclipse.cdt.qt.core.qtNature"/>
</iterate>
</with>
</enablement>
Bug 422841: Initial implementation of QtIndex This uses the new PDOMASTProcessor extension point to create a Qt-specifc PDOMLinkage. This initial version of the linkage only stores QObjects and their base classes. Later commits will fill out other details and introduce classes that use this data for things like Content Assistance and Codan checking. This patch introduces the following: 1) QtIndex: This is an index that provides access to Qt-specific data. The index is mostly a wrapper on the CDT's existing IIndex, but it provides very specific information about the Qt elements. The only data that can be accessed from the QtIndex (in this patch) is a QObject and the QObject's that appear in its base class specifier list. 2) QtPDOMLinkage: This linkage is implemenated as an extension of the PDOMCPPLinkage. In some cases it adds references to Qt names from the C++ bindings. 3) Test suite: The test suite has some base classes for parsing the Qt source code. The only test case is for the simple functionality that is being added in this patch -- examining the base class specifier list of QObjects. These areas will be extended in later patches. Change-Id: I13fb83beb7f50cd2efb1de97b562245dc642468d Signed-off-by: Andrew Eidsness <eclipse@jfront.com> Reviewed-on: https://git.eclipse.org/r/19113 Tested-by: Hudson CI Reviewed-by: Doug Schaefer <dschaefer@qnx.com> IP-Clean: Doug Schaefer <dschaefer@qnx.com>
2013-11-29 08:28:51 -05:00
</processor>
</extension>
<extension point="org.eclipse.cdt.core.language">
<pdomLinkageFactory
id="Qt"
Fix Qt plugin's project structure The Qt plugins have been naming internal packages using two different prefixes: cdt.qt.internal cdt.internal.qt This renames all packages to cdt.internal.qt, which seems to be the convention for other projects. I've increased the Qt plugin versions because alot of new API has been added, especially to the qt.core plugin. I increased the version in the MANIFEST.MF and pom.xml files. I've also fixed the MANIFEST.MF files to take CDT out of the plugin names. I've also replaced a call to CCorePlugin.log(Exception) with a call to QtUIPlugin.log (and added the logging functions to QtUIPlugin. Change-Id: I1e3e7b2a42c2eb79fe33608c14a1abcf013a9f2c Signed-off-by: Andrew Eidsness <eclipse@jfront.com> Reviewed-on: https://git.eclipse.org/r/19698 Tested-by: Hudson CI Reviewed-by: Doug Schaefer <dschaefer@qnx.com> IP-Clean: Doug Schaefer <dschaefer@qnx.com>
2013-12-12 07:40:51 -05:00
class="org.eclipse.cdt.internal.qt.core.pdom.PDOMQtLinkageFactory"/>
qt slot/signal auto-complete Tags signal and slot methods when the index is created. Uses these tags to suggest values inside of SIGNAL and SLOT macro expansions. Enabled only for projects with the QtNature. Recognizes QObject::connect function calls and suggests SIGNAL(a) and SLOT(a) for the 2nd and 4th parameters. When expanding the SIGNAL and SLOT macros within a call to QObject::connect, suggests signals and slots based on the type of the previous parameter. E.g. in QObjectA a; QObjectB b; QObject::connect( &a, SIGNAL(*), &b, SLOT(**) ); The content assistant will suggest the methods of type QObjectA that have been marked as signals at *, and the methods of QObjectB that have been marked as slots at **. Change-Id: Ia6aaa71724547b0977e322399a500f072004767a Reviewed-on: https://git.eclipse.org/r/10532 Reviewed-by: Doug Schaefer <dschaefer@qnx.com> IP-Clean: Doug Schaefer <dschaefer@qnx.com> Tested-by: Doug Schaefer <dschaefer@qnx.com>
2013-02-20 13:23:40 -05:00
</extension>
Bug 418406: Qt4 and Qt5 specific HelloWorld project wizards This replaces the QtQuick2 project wizard with Qt4 and Qt5 wizards that include the old content as well as: 1) Make targets to build and clean the project 2) Sample interaction between C++ and QML 3) A Qt header path provider so that paths from the Qt installation are properly resolved in the project. Item 3 is particularly important for using the 'New Class' wizard with QObject as the base class. Unless the Qt paths are pre-populated the QObject base class will not be found and the New Class wizard's Finish button will be disabled. The Qt headers are resolved by running `qmake -query QT_INSTALL_HEADERS` and then creating IncludePath entries for all sub-folders. This list of include paths is persisted with other shared language settings into a file in the workspace metadata area. The persisted data is reloaded when any of the following change: - the modification time of the qmake binary - the modification time of the reported QT_INSTALL_HEADERS folder The persisted node is ignored when the target qmake binary no longer exists. The node is removed from the persisted form the next time that the shared settings are persisted. Change-Id: Ic82fdb147e6a69060f93e2e9aed2e919139a0ae9 Signed-off-by: Andrew Eidsness <eclipse@jfront.com> Reviewed-on: https://git.eclipse.org/r/16909 Reviewed-by: Doug Schaefer <dschaefer@qnx.com> IP-Clean: Doug Schaefer <dschaefer@qnx.com> Tested-by: Doug Schaefer <dschaefer@qnx.com>
2013-10-23 07:12:25 -04:00
<extension point="org.eclipse.cdt.core.LanguageSettingsProvider">
<provider
Fix Qt plugin's project structure The Qt plugins have been naming internal packages using two different prefixes: cdt.qt.internal cdt.internal.qt This renames all packages to cdt.internal.qt, which seems to be the convention for other projects. I've increased the Qt plugin versions because alot of new API has been added, especially to the qt.core plugin. I increased the version in the MANIFEST.MF and pom.xml files. I've also fixed the MANIFEST.MF files to take CDT out of the plugin names. I've also replaced a call to CCorePlugin.log(Exception) with a call to QtUIPlugin.log (and added the logging functions to QtUIPlugin. Change-Id: I1e3e7b2a42c2eb79fe33608c14a1abcf013a9f2c Signed-off-by: Andrew Eidsness <eclipse@jfront.com> Reviewed-on: https://git.eclipse.org/r/19698 Tested-by: Hudson CI Reviewed-by: Doug Schaefer <dschaefer@qnx.com> IP-Clean: Doug Schaefer <dschaefer@qnx.com>
2013-12-12 07:40:51 -05:00
class="org.eclipse.cdt.internal.qt.core.QtIncludePathsProvider"
Bug 418406: Qt4 and Qt5 specific HelloWorld project wizards This replaces the QtQuick2 project wizard with Qt4 and Qt5 wizards that include the old content as well as: 1) Make targets to build and clean the project 2) Sample interaction between C++ and QML 3) A Qt header path provider so that paths from the Qt installation are properly resolved in the project. Item 3 is particularly important for using the 'New Class' wizard with QObject as the base class. Unless the Qt paths are pre-populated the QObject base class will not be found and the New Class wizard's Finish button will be disabled. The Qt headers are resolved by running `qmake -query QT_INSTALL_HEADERS` and then creating IncludePath entries for all sub-folders. This list of include paths is persisted with other shared language settings into a file in the workspace metadata area. The persisted data is reloaded when any of the following change: - the modification time of the qmake binary - the modification time of the reported QT_INSTALL_HEADERS folder The persisted node is ignored when the target qmake binary no longer exists. The node is removed from the persisted form the next time that the shared settings are persisted. Change-Id: Ic82fdb147e6a69060f93e2e9aed2e919139a0ae9 Signed-off-by: Andrew Eidsness <eclipse@jfront.com> Reviewed-on: https://git.eclipse.org/r/16909 Reviewed-by: Doug Schaefer <dschaefer@qnx.com> IP-Clean: Doug Schaefer <dschaefer@qnx.com> Tested-by: Doug Schaefer <dschaefer@qnx.com>
2013-10-23 07:12:25 -04:00
id="org.eclipse.cdt.qt.core.QtPathsProvider"
name="%QtInstallHeaders.pathProvider.name"
prefer-non-shared="false">
<language-scope id="org.eclipse.cdt.core.g++"/>
</provider>
</extension>
Clean up the API around QtNature. Add isProject expr def.
2013-12-13 17:03:52 -05:00
<extension point="org.eclipse.core.expressions.definitions">
<definition id="org.eclipse.cdt.qt.core.isQtProject">
<with variable="projectNatures">
<iterate operator="or">
<equals value="org.eclipse.cdt.qt.core.qtNature"/>
</iterate>
</with>
</definition>
</extension>
Bug 424824: Codan checker for Qt This implements a Codan checker for QObject::connect and disconnect function calls. There are several overloads for each function, but the basic call looks like: Q * q; QObject::connect( q, SIGNAL( sign() ), q, SLOT( slot() ) ); This function calls requires that Q have a Qt signal called sign and a Qt slot called slot, e.g., class Q : public QObject { Q_OBJECT Q_SIGNAL void sign(); Q_SLOT void slot(); }; The Qt checker raises a warning if either condition is not true. It also raises a warning for SIGNAL or SLOT expansions without a parameter. Change-Id: If68a5bcdabb3f118801675e46ae926e6a250378a Signed-off-by: Andrew Eidsness <eclipse@jfront.com> Reviewed-on: https://git.eclipse.org/r/20231 Tested-by: Hudson CI Reviewed-by: Doug Schaefer <dschaefer@qnx.com> IP-Clean: Doug Schaefer <dschaefer@qnx.com>
2014-01-02 17:06:05 -05:00
<extension
point="org.eclipse.cdt.codan.core.checkers"
id="org.eclipse.cdt.core.qt.SyntaxCheckers">
<category
id="org.eclipse.cdt.qt.core.qtproblemcategory"
name="Qt Problems">
</category>
<checker
id="org.eclipse.cdt.core.qt.connectfunctioncallchecker"
name="Qt Connect Function Call Checker"
class="org.eclipse.cdt.internal.qt.core.codan.QtSyntaxChecker">
<problem
category="org.eclipse.cdt.qt.core.qtproblemcategory"
defaultEnabled="true"
defaultSeverity="Warning"
id="org.eclipse.cdt.qt.core.qtproblem"
markerType="org.eclipse.cdt.qt.core.qtproblem"
messagePattern="{0}"
name="Qt Syntax Problem">
</problem>
</checker>
</extension>
<extension
point="org.eclipse.core.resources.markers"
id="qtproblem"
name="Qt C/C++ Problem">
<super type="org.eclipse.cdt.codan.core.codanProblem"/>
<persistent value="true"/>
</extension>
Start of work on doing Qt the new way. Change-Id: Icc891538549485f9ad99614f36262ed218fb0609
2015-08-26 16:58:18 -04:00
<extension
id="qtBuilder"
Bug 481978 - Big overhaul of new build system to work with Qt. Moved new build system to it's own plug-ins. Cleaned up the root build configuration and toolchain classes and use them for Qt local run builds. Also hooks Qt local run launch delegate to launch target manager and associated delegate interface. Change-Id: I0c0f711ee53005edd399f6d24ba96658d606e1e5
2015-11-24 14:56:37 -05:00
name="Qt Builder"
Start of work on doing Qt the new way. Change-Id: Icc891538549485f9ad99614f36262ed218fb0609
2015-08-26 16:58:18 -04:00
point="org.eclipse.core.resources.builders">
<builder
callOnEmptyDelta="true"
hasNature="true"
isConfigurable="true"
supportsConfigurations="true">
<run
class="org.eclipse.cdt.internal.qt.core.build.QtBuilder">
</run></builder>
</extension>
Starting to put Qt onto the new build system and launch. Change-Id: I3e65f5d69bfb35d16b2d1135f99517c7a2b2c437
2015-09-25 17:01:37 -04:00
<extension
point="org.eclipse.launchbar.core.launchBarContributions">
<descriptorType
class="org.eclipse.cdt.internal.qt.core.launch.QtLaunchDescriptorType"
id="org.eclipse.cdt.qt.core.launchDescriptorType"
priority="10">
<enablement>
<instanceof
value="org.eclipse.core.resources.IProject">
</instanceof>
<test
forcePluginActivation="true"
property="org.eclipse.core.resources.projectNature"
value="org.eclipse.cdt.qt.core.qtNature">
</test>
</enablement>
</descriptorType>
<configProvider
Bug 481978 - Lots of clean-up to the Qt Build and Launch. Especially launch. Now have local and QNX launches (which are in our internal repo) working. Change-Id: I97bacc520cc6806fe9622700b2bb3f544e4aad94
2015-11-26 16:20:37 -05:00
class="org.eclipse.cdt.internal.qt.core.launch.QtLocalLaunchConfigationProvider"
Starting to put Qt onto the new build system and launch. Change-Id: I3e65f5d69bfb35d16b2d1135f99517c7a2b2c437
2015-09-25 17:01:37 -04:00
descriptorType="org.eclipse.cdt.qt.core.launchDescriptorType"
priority="10">
</configProvider>
</extension>
Bug 486509 - Add support for debugging local Qt apps. We reuse GDBLaunch but need to override some settings that are normally in the launch configuration. These things are calculated at launch time. Note there is also an added dependency to the launch bar core to make GDBLaunch a targeted launch so we can set the target properly. At some point we'll move this launch target stuff lower down, maybe to the debug platform. Change-Id: Ibbf6b794a9ecf25b79d46093cc624ea69dc04641
2016-01-25 15:00:32 -05:00
<extension
point="org.eclipse.debug.core.launchConfigurationTypes">
<launchConfigurationType
Qt - cleanup build cases. Add method to GDBLaunch. Clean up cases when Qt installs aren't registered for a given config. Fix bug on first scanner info request in build config. Clean up the Qt Run launch delegate in extension. Also added a method to GDBLaunch to allow subclasses to override what the default gdb path is. Change-Id: Icf158633e1c1327cc87ce59c1605bb26258f8708
2016-02-02 16:42:06 -05:00
delegate="org.eclipse.cdt.internal.qt.core.launch.QtLocalRunLaunchConfigDelegate"
Bug 486509 - Add support for debugging local Qt apps. We reuse GDBLaunch but need to override some settings that are normally in the launch configuration. These things are calculated at launch time. Note there is also an added dependency to the launch bar core to make GDBLaunch a targeted launch so we can set the target properly. At some point we'll move this launch target stuff lower down, maybe to the debug platform. Change-Id: Ibbf6b794a9ecf25b79d46093cc624ea69dc04641
2016-01-25 15:00:32 -05:00
id="org.eclipse.cdt.qt.core.launchConfigurationType"
Qt - cleanup build cases. Add method to GDBLaunch. Clean up cases when Qt installs aren't registered for a given config. Fix bug on first scanner info request in build config. Clean up the Qt Run launch delegate in extension. Also added a method to GDBLaunch to allow subclasses to override what the default gdb path is. Change-Id: Icf158633e1c1327cc87ce59c1605bb26258f8708
2016-02-02 16:42:06 -05:00
modes="run"
Bug 486509 - Add support for debugging local Qt apps. We reuse GDBLaunch but need to override some settings that are normally in the launch configuration. These things are calculated at launch time. Note there is also an added dependency to the launch bar core to make GDBLaunch a targeted launch so we can set the target properly. At some point we'll move this launch target stuff lower down, maybe to the debug platform. Change-Id: Ibbf6b794a9ecf25b79d46093cc624ea69dc04641
2016-01-25 15:00:32 -05:00
name="Qt Local Application"
Qt - cleanup build cases. Add method to GDBLaunch. Clean up cases when Qt installs aren't registered for a given config. Fix bug on first scanner info request in build config. Clean up the Qt Run launch delegate in extension. Also added a method to GDBLaunch to allow subclasses to override what the default gdb path is. Change-Id: Icf158633e1c1327cc87ce59c1605bb26258f8708
2016-02-02 16:42:06 -05:00
public="true"
sourceLocatorId="org.eclipse.cdt.debug.core.sourceLocator"
sourcePathComputerId="org.eclipse.cdt.debug.core.sourcePathComputer">
Bug 486509 - Add support for debugging local Qt apps. We reuse GDBLaunch but need to override some settings that are normally in the launch configuration. These things are calculated at launch time. Note there is also an added dependency to the launch bar core to make GDBLaunch a targeted launch so we can set the target properly. At some point we'll move this launch target stuff lower down, maybe to the debug platform. Change-Id: Ibbf6b794a9ecf25b79d46093cc624ea69dc04641
2016-01-25 15:00:32 -05:00
</launchConfigurationType>
</extension>
<extension
point="org.eclipse.debug.core.launchDelegates">
<launchDelegate
delegate="org.eclipse.cdt.internal.qt.core.launch.QtLocalDebugLaunchConfigDelegate"
id="org.eclipse.cdt.qt.core.launchDelegate.debug.local"
modes="debug"
name="Qt Local Debug launcher"
type="org.eclipse.cdt.qt.core.launchConfigurationType">
</launchDelegate>
</extension>
Tighter integration of new build system with cdt.core. Move the new build system to cdt.core and remove the previous plugins. Hook the new system into scanner info and environment variable manager. Clean up API in preparation for Neon and API lockdown. Hook up Qt to the new APIs. Add discovery of MSYS2's toolchain and Qt and Qt's MinGW toolchain. Change-Id: I85b1a91da4a44e86f0e9da9310f8106c894623e0
2016-03-31 11:28:28 -04:00
<extension
point="org.eclipse.cdt.core.buildConfigProvider">
<provider
class="org.eclipse.cdt.internal.qt.core.build.QtBuildConfigurationProvider"
id="org.eclipse.cdt.qt.core.qtBuildConfigProvider"
natureId="org.eclipse.cdt.qt.core.qtNature">
</provider>
</extension>
<extension
point="org.eclipse.cdt.core.toolChainProvider">
<provider
Modernize Arduino plug-ins. Adjust APIs to suite. Change-Id: Ic877c8f0992874e647d4b464502165d7bd3ebe0e
2016-04-27 16:44:47 -04:00
class="org.eclipse.cdt.qt.core.QtMinGWToolChainProvider"
id="org.eclipse.cdt.qt.core.qtMinGWProvider">
Tighter integration of new build system with cdt.core. Move the new build system to cdt.core and remove the previous plugins. Hook the new system into scanner info and environment variable manager. Clean up API in preparation for Neon and API lockdown. Hook up Qt to the new APIs. Add discovery of MSYS2's toolchain and Qt and Qt's MinGW toolchain. Change-Id: I85b1a91da4a44e86f0e9da9310f8106c894623e0
2016-03-31 11:28:28 -04:00
</provider>
</extension>
<extension
point="org.eclipse.cdt.qt.core.qtInstallProvider">
<provider
class="org.eclipse.cdt.internal.qt.core.provider.Msys2QtInstallProvider">
</provider>
<provider
class="org.eclipse.cdt.internal.qt.core.provider.HomebrewQtInstallProvider">
</provider>
<provider
class="org.eclipse.cdt.internal.qt.core.provider.QtInstallProvider">
</provider>
</extension>
<extension
point="org.eclipse.cdt.qt.core.qtToolChainMapper">
<mapping
spec="macx-clang">
<property
key="os"
value="macosx">
</property>
<property
key="arch"
value="x86_64">
</property>
</mapping>
</extension>
Added support for Qt. Extended AddFiles template to change start/end patterns.
2013-01-12 00:54:08 -05:00
</plugin>
Reference in a new issue Copy permalink