Alena Laskavaia wrote:
It is called automatically also when toolchain version is lower than current one. There is no way to make it called if version does not change.
thanks for the reply. If that is the case it is music to my ears. Please forgive my ignorance, but where is the "toolchain version" specified?
I'm using the extension point "org.eclipse.cdt.managedbuilder.core.buildDefinitions" and have based my whole plugin on org.eclipse.cdt.managedbuilder.gnu.ui. hence none of the "versionsSupported" fields are populated.
So if I wanted my converter to be triggered using my new plugin version (call it 4.1.1 for arguments sake) where would I have to specify that version number?
I've tried populating various parts of my plugin with versionsSupported=4.1.1 and opening my workspace containing old projects in a runtime workbench, but I'm not seeing my converter being called automatically.
cheers john
You can install listener on resource change events (this is how auto-converter implemented). On Wed, Oct 21, 2009 at 11:37 AM, John MOULE <john.moule@xxxxxx> wrote:Hi, Using the extension point, org.eclipse.cdt.managedbuilder.core.projectConverter, to provide a project converter I only see my converter being called when the user selects the project context menu "Convert to...". Is there a way to get project conversion done automatically when a user opens a workspace, opens a closed project or imports a project? Do I have to install listeners manually myself in those places? Any tips on how to proceed if that is the case please? cheers john p.s. using [Eclipse 3.4.2, CDT 5.0.2] _______________________________________________ cdt-dev mailing list cdt-dev@xxxxxxxxxxx https://dev.eclipse.org/mailman/listinfo/cdt-dev_______________________________________________ cdt-dev mailing list cdt-dev@xxxxxxxxxxx https://dev.eclipse.org/mailman/listinfo/cdt-dev
--
john moule
software engineer
stmicroelectronics ltd
1000 aztec west
bristol bs32 4sq
uk
t +44 (0)1454 462481
TINA 065 2481
