| AW: [cdt-dev] Using 2.1.1 managed build definitions to 3.0 |
|
Leo,
thank you for your support. I have now adopted the simple
solution of just leaving the deprecated fields blank since they are defined to
my satisfaction by the superclass (which I had not realized
before).
So I learned a little more about my own definitions and can
wait for the base definitions to be migrated (if they will ever
be).
Tnx
Norbert Von: cdt-dev-bounces@xxxxxxxxxxx [mailto:cdt-dev-bounces@xxxxxxxxxxx] Im Auftrag von Treggiari, Leo Gesendet: Dienstag, 3. Mai 2005 14:26 An: CDT General developers list. Betreff: RE: [cdt-dev] Using 2.1.1 managed build definitions to 3.0 Hi
Norbert, - is it wise at all to
migrate to the new schema at this point or am I working with an alpha
release? You are working with an
alpha release, but I expect what you are trying to do to
work. - will support for the
deprecated attributes be removed for the CTD 3.0 release? (The documentation
seems to say: no) The deprecated
attributes will not be removed in 3.0, and will never be removed unless it
becomes impractical to support them. - will there be more
detailed documentation for the migration at a later point? (Like an overhaul of
the extensibility document) Yes, there will be an
overhaul of the existing tool-integrator document, but that wont happen until
around GA time. ========snip=========== <tool
id="de.siemens.rmos.crossdevel.simulation.tools.compiler"
superClass="cdt.managedbuild.tool.gnu.c.compiler.cygwin.exe.debug"
command="/bin/gcc"
headerExtensions="h,H"
name="GCC C Compiler"
outputFlag="-o"
natureFilter="cnature">
<inputType Im not sure what the problem is.
Are you also defining your own linker tool definition? If yes,
please let me see that also. If no, try
adding:
buildVariable=OBJS to your outputType definition.
I havent tested using old-style and new style attributes in the same tool
chain, but that needs to be supported. Also:
dependencyExtensions="o"
dependencyExtensions="h,H" Thanks, Leo From:
cdt-dev-bounces@xxxxxxxxxxx [mailto:cdt-dev-bounces@xxxxxxxxxxx] On Behalf Of Ploett Norbert Hi
Leo, seeing the design
document is helpful, but I still can't get anything working. So my first
questions are - is it wise at all to
migrate to the new schema at this point or am I working with an alpha
release? - will support for the
deprecated attributes be removed for the CTD 3.0 release? (The documentation
seems to say: no) - will there be more
detailed documentation for the migration at a later point? (Like an overhaul of
the extensibility document) If you think it is
worthwhile to make the attempt now, here is a snippet from my build
definitions: ========snip=========== <tool
id="de.siemens.rmos.crossdevel.simulation.tools.compiler"
superClass="cdt.managedbuild.tool.gnu.c.compiler.cygwin.exe.debug"
command="/bin/gcc"
headerExtensions="h,H"
name="GCC C Compiler"
outputFlag="-o"
natureFilter="cnature">
<inputType The symptoms I see are
simply that the compiler is not started anymore. When I start a rebuild the
linker is called right away. I tried a few variations of the above, but always
with the same result. During my previous
attempts with managed builder definitions I have found that many problems are
resolved when I find the right superclass for an element. This was not possible
at this time since the org.eclipse.cdt.managedbuilder.ui plugin.xml, which
contains all the base definitions, does not yet have any inputType and
outputType definitions. What is your (or
anybody else's) advice? - Leave it for a
while. - Get newer
sources. - Change my definitions
(please specify which ones). Thanks for your
help Norbert
Ploett Von:
cdt-dev-bounces@xxxxxxxxxxx [mailto:cdt-dev-bounces@xxxxxxxxxxx] Im Auftrag von Hi
Norbert, There isnt any How
To documentation yet. Take a look at the design document in bugzilla
87673. Basically you should define an InputType and an OutputType as
children of the Tool. The attributes that you mention have moved
there. Regards, Leo From:
cdt-dev-bounces@xxxxxxxxxxx [mailto:cdt-dev-bounces@xxxxxxxxxxx] On Behalf Of Ploett Norbert Hello
folks, I am trying some managed build
definitions I wrote for CDT 2.1.1 in CDT 3.0 from the weekly build of April 25.
They all do work, but some attributes are flagged as deprecated.
Specifically, in a "tool" definiton
the attributes "outputs", "sources" and "headerExtensions" are flagged. Is there
any documentation available about how I can make my definitions conform to the
CDT 3.0? Or any simple hints? Bye Norbert
Ploett ======================= Dr.-Ing. Norbert
Plött Siemens A&D ATS
1 Gleiwitzer Str.
555 90475
Nürnberg Tel.: +49 911 895
3484 Fax: +49 911 895
3715 |