On Mon, Apr 27, 2009 at 10:55 AM, Christian W. Damus
<cdamus@xxxxxxx> wrote:
Hi, Doug,
Why build a tool chain with Java code? It should be described as an instance of an EMF model.
Christian, could you please elaborate on the reasons to use EMF.
At run time an EMF model is just a set of Java classes, so support for tool chain EMF models implies an ability to build a tool chain in pure Java.
cW
-sergey
On Mon, 2009-04-27 at 13:44 -0400, Doug Schaefer wrote:
This is definitely one area I want to enhance with a new rev of the build model. There are limits to what you can do with the dynamicElementProvider, for whatever reason. I'd like to be able to express my entire tool chain using Java. That needs to be made easier.
Doug.
On Mon, Apr 27, 2009 at 1:09 PM, Chris Recoskie <recoskie@xxxxxxxxxx> wrote:
The buildDefinitions extension point has a provision for this... the dynamicElementProvider. However, I don't think anyone has used this in quite some time and so I'm not sure it's fully functional any more.
This is from the extention point description:
<!ELEMENT dynamicElementProvider EMPTY>
<!ATTLIST dynamicElementProvider
class CDATA #REQUIRED
name CDATA #REQUIRED>
An optional element that allows a tool implementor to supply a class that creates one or more dynamic toolchain elements. For example, the class might create a new tool reference based on the contents of a special file, and a new target that uses that reference.
- class - The class that implements the IManagedConfigElementProvider interface. The logic of determining the elements is left to the implementer, but they must be correctly formed or the build model will have trouble loading.
- name - A meaningful name for the type of element being provided.
===========================
Chris Recoskie
Team Lead, IBM CDT and RDT
IBM Toronto
Mike Wrighton <mike.wrighton@xxxxxxxxxxxxxx>
Hi,
Does anyone know if there's a way to create (or populate) tool options
at runtime? I need to query the toolchain for a list of supported
targets and display them in a combo.
Cheers,
Mike
_______________________________________________
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
_______________________________________________
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