RE: [cdt-dev] MBS Question

["Treggiari, Leo" <leo.treggiari@xxxxxxxxx>]

Hi Derek,

The primary things that the MBS needs to match up from the .cdtbuild
file to a set of build definitions are the IDs.  When you change IDs,
old projects will not load correctly without using the MBS converter
functionality.

You can look at the Managed Build Extensibility Guide in the on-line
help CDT Plug-in Developer Guide for details.  Two of the important
attributes to look for are the versionsSupported and convertToId
attributes.  If you are simply changing the version suffix of Ids, you
should be able to just use the versionsSupported attribute(s).  If you
are changing your project definition in a more complicated manner,
you'll probably need to use the convertToId attribute and write a
converter.

Regards,
Leo

-----Original Message-----
From: cdt-dev-bounces@xxxxxxxxxxx [mailto:cdt-dev-bounces@xxxxxxxxxxx]
On Behalf Of dmsubs
Sent: Thursday, January 12, 2006 12:20 PM
To: 'CDT General developers list.'
Subject: [cdt-dev] MBS Question

Hi,

Can somebody tell me how the MBS determines if a project is no longer
valid
because of changes to the plugin? Also, how can you translate a project
if
this happens?

For example, I've been developing a plugin for our GNU tools and
creating
projects based on that plugin (it is entirely defined by plugin.xml).
Whilst
in development, I used a Version of 0.0.0, but am now ready for release
and
want to change to a meaningful version number (1.0.0). However, when I
do
that (no other changes), it invalidates my project.

Can somebody help?

Thanks!

---
Derek 

_______________________________________________
cdt-dev mailing list
cdt-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/cdt-dev