mirrors/cdt
1
0
Fork 0
mirror of https://github.com/eclipse-cdt/cdt synced 2025-07-30 20:35:38 +02:00
Code Issues Wiki Activity
cdt/core/org.eclipse.cdt.core/.classpath

22 lines
1 KiB
Text
Raw Normal View History

First commit of CDT code from QNX
2002-06-26 20:29:14 +00:00
<?xml version="1.0" encoding="UTF-8"?>
<classpath>
Patch for Sean Evoy In order to work through CExtensionPoint mechanism, I have to change the existing extension point entries for the Managed and Standard builders to the following (all future builders will have to conform to this as well): <extension id="ManagedBuildManager" point="org.eclipse.cdt.core.ScannerInfoProvider"> <cextension> <run class="org.eclipse.cdt.core.build.managed.ManagedBuildManager"> </run> </cextension> </extension> <extension id="StandardBuildManager" point="org.eclipse.cdt.core.ScannerInfoProvider"> <cextension> <run class="org.eclipse.cdt.core.build.standard.StandardBuildManager"> </run> </cextension> </extension> As well, the ManagedBuildManager and StandardBuildManager must extend AbstractCExtension. The new project wizards for managed and standard projects have to be modified to register the right class as the scanner info providers for the project. The example below shows the managed project wizard code, but the standard project wizard is similar. try { ICDescriptor desc = CCorePlugin.getDefault().getCProjectDescription(project); desc.remove(CCorePlugin.BUILD_SCANNER_INFO_UNIQ_ID); desc.create(CCorePlugin.BUILD_SCANNER_INFO_UNIQ_ID, ManagedBuildManager.INTERFACE_IDENTITY); } <snip> Clients use a new method defined in CCorePlugin public IScannerInfoProvider getScannerInfoProvider(IProject project) { IScannerInfoProvider provider = null; if (project != null) { try { ICDescriptor desc = (ICDescriptor) getCProjectDescription(project); ICExtensionReference[] extensions = desc.get(BUILD_SCANNER_INFO_UNIQ_ID); if (extensions.length > 0) provider = (IScannerInfoProvider) extensions[0].createExtension(); } catch (CoreException e) { } } return provider; } to get the information provider as shown in the updated JUnit test code below: // Find the first IScannerInfoProvider that supplies build info for the project IScannerInfoProvider provider = CCorePlugin.getDefault().getScannerInfoProvider(project); assertNotNull(provider); As is the case now, clients implement the IScannerInfoChangeListener interface and pass themselves to the provider in a subscription message. There is also a new method on the IScannerInfoProvider interface that allows the client to get information immediately as shown below: IScannerInfo currentSettings = provider.getScannerInformation(project); The ManagedBuildManager::getScannerInfo(IResource) method will be deprecated, then removed before the end of this release cycle.
2003-08-13 17:45:38 +00:00
<classpathentry kind="src" path="build/"/>
cleanup
2002-09-17 18:53:40 +00:00
<classpathentry kind="src" path="index/"/>
<classpathentry kind="src" path="model/"/>
<classpathentry kind="src" path="src/"/>
<classpathentry kind="src" path="utils/"/>
Patch for Sean Evoy In order to work through CExtensionPoint mechanism, I have to change the existing extension point entries for the Managed and Standard builders to the following (all future builders will have to conform to this as well): <extension id="ManagedBuildManager" point="org.eclipse.cdt.core.ScannerInfoProvider"> <cextension> <run class="org.eclipse.cdt.core.build.managed.ManagedBuildManager"> </run> </cextension> </extension> <extension id="StandardBuildManager" point="org.eclipse.cdt.core.ScannerInfoProvider"> <cextension> <run class="org.eclipse.cdt.core.build.standard.StandardBuildManager"> </run> </cextension> </extension> As well, the ManagedBuildManager and StandardBuildManager must extend AbstractCExtension. The new project wizards for managed and standard projects have to be modified to register the right class as the scanner info providers for the project. The example below shows the managed project wizard code, but the standard project wizard is similar. try { ICDescriptor desc = CCorePlugin.getDefault().getCProjectDescription(project); desc.remove(CCorePlugin.BUILD_SCANNER_INFO_UNIQ_ID); desc.create(CCorePlugin.BUILD_SCANNER_INFO_UNIQ_ID, ManagedBuildManager.INTERFACE_IDENTITY); } <snip> Clients use a new method defined in CCorePlugin public IScannerInfoProvider getScannerInfoProvider(IProject project) { IScannerInfoProvider provider = null; if (project != null) { try { ICDescriptor desc = (ICDescriptor) getCProjectDescription(project); ICExtensionReference[] extensions = desc.get(BUILD_SCANNER_INFO_UNIQ_ID); if (extensions.length > 0) provider = (IScannerInfoProvider) extensions[0].createExtension(); } catch (CoreException e) { } } return provider; } to get the information provider as shown in the updated JUnit test code below: // Find the first IScannerInfoProvider that supplies build info for the project IScannerInfoProvider provider = CCorePlugin.getDefault().getScannerInfoProvider(project); assertNotNull(provider); As is the case now, clients implement the IScannerInfoChangeListener interface and pass themselves to the provider in a subscription message. There is also a new method on the IScannerInfoProvider interface that allows the client to get information immediately as shown below: IScannerInfo currentSettings = provider.getScannerInformation(project); The ManagedBuildManager::getScannerInfo(IResource) method will be deprecated, then removed before the end of this release cycle.
2003-08-13 17:45:38 +00:00
<classpathentry kind="src" path="search/"/>
<classpathentry kind="src" path="dependency/"/>
Make the parser source folder a separate jar.
2003-11-05 19:22:44 +00:00
<classpathentry kind="src" path="parser"/>
change all external plugin jar references to project references added some missing src paths
2002-06-28 14:20:21 +00:00
<classpathentry kind="src" path="/org.eclipse.core.resources"/>
<classpathentry kind="src" path="/org.eclipse.core.runtime"/>
<classpathentry kind="src" path="/org.apache.xerces"/>
cleanup
2002-09-17 18:53:40 +00:00
<classpathentry kind="src" path="/org.eclipse.search"/>
<classpathentry kind="src" path="/org.eclipse.compare"/>
<classpathentry kind="src" path="/org.eclipse.debug.core"/>
Patch for Keith Campbell. - Add missing plugin dependency to eliminate warnings about undefined extension points.
2003-09-12 18:19:05 +00:00
<classpathentry kind="src" path="/org.eclipse.team.core"/>
change all external plugin jar references to project references added some missing src paths
2002-06-28 14:20:21 +00:00
<classpathentry kind="src" path="/org.eclipse.core.boot"/>
Patch for Sean Evoy In order to work through CExtensionPoint mechanism, I have to change the existing extension point entries for the Managed and Standard builders to the following (all future builders will have to conform to this as well): <extension id="ManagedBuildManager" point="org.eclipse.cdt.core.ScannerInfoProvider"> <cextension> <run class="org.eclipse.cdt.core.build.managed.ManagedBuildManager"> </run> </cextension> </extension> <extension id="StandardBuildManager" point="org.eclipse.cdt.core.ScannerInfoProvider"> <cextension> <run class="org.eclipse.cdt.core.build.standard.StandardBuildManager"> </run> </cextension> </extension> As well, the ManagedBuildManager and StandardBuildManager must extend AbstractCExtension. The new project wizards for managed and standard projects have to be modified to register the right class as the scanner info providers for the project. The example below shows the managed project wizard code, but the standard project wizard is similar. try { ICDescriptor desc = CCorePlugin.getDefault().getCProjectDescription(project); desc.remove(CCorePlugin.BUILD_SCANNER_INFO_UNIQ_ID); desc.create(CCorePlugin.BUILD_SCANNER_INFO_UNIQ_ID, ManagedBuildManager.INTERFACE_IDENTITY); } <snip> Clients use a new method defined in CCorePlugin public IScannerInfoProvider getScannerInfoProvider(IProject project) { IScannerInfoProvider provider = null; if (project != null) { try { ICDescriptor desc = (ICDescriptor) getCProjectDescription(project); ICExtensionReference[] extensions = desc.get(BUILD_SCANNER_INFO_UNIQ_ID); if (extensions.length > 0) provider = (IScannerInfoProvider) extensions[0].createExtension(); } catch (CoreException e) { } } return provider; } to get the information provider as shown in the updated JUnit test code below: // Find the first IScannerInfoProvider that supplies build info for the project IScannerInfoProvider provider = CCorePlugin.getDefault().getScannerInfoProvider(project); assertNotNull(provider); As is the case now, clients implement the IScannerInfoChangeListener interface and pass themselves to the provider in a subscription message. There is also a new method on the IScannerInfoProvider interface that allows the client to get information immediately as shown below: IScannerInfo currentSettings = provider.getScannerInformation(project); The ManagedBuildManager::getScannerInfo(IResource) method will be deprecated, then removed before the end of this release cycle.
2003-08-13 17:45:38 +00:00
<classpathentry kind="con" path="org.eclipse.jdt.launching.JRE_CONTAINER"/>
First commit of CDT code from QNX
2002-06-26 20:29:14 +00:00
<classpathentry kind="output" path="bin"/>
</classpath>
Reference in a new issue Copy permalink