[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
Re: [cdt-dev] Creating tool options programatically
|
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
![Inactive hide details for Mike Wrighton <mike.wrighton@xxxxxxxxxxxxxx>]()
Mike Wrighton <mike.wrighton@xxxxxxxxxxxxxx>
Mike Wrighton <mike.wrighton@xxxxxxxxxxxxxx>
Sent by: cdt-dev-bounces@xxxxxxxxxxx
04/27/2009 12:30 PM
Please respond to
"CDT General developers list." <cdt-dev@xxxxxxxxxxx> |
|
|
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
![GIF image](gifFFRNG0uriE.gif)
![GIF image](gifN9vmRJVkpn.gif)
![GIF image](gifJqdIaz6f_U.gif)