Hi Chris,
Thanks for the review and comments.
>InputDetail Schema
>Just a comment: although I can
imagine some interesting ways of utilizing it,
>I don’t know how much people are
going to use the Input etail element in their
>toolchain plugins as a static definition.
This is probably the source of some
>of Lars’ confusion. I am
assuming Leo is not really intending this element
>for this purpose and really this is
intended for use as an internal model
>element which is going to be utilized
by some sort of “link order properties
>editor” type thing. The idea is
that this element would be created on a per-
>resource basis prior to project build
as the user changes the settings on
>various source files to exclude them
from build, customize their link order,
>etc.
That's exactly right Chris. That can be
done since the XML schema in the
manifest file (plugin.xml) and the XML
schema in the project file (.cdtbuild) are
identical.
>Q: What are we doing to provide for a
default GUI for editing the input
>ordering?
I haven't thought about it yet, but it
will support:
- ordering some or all of the files
- excluding files
>OutputType Schema
>Re: the “option” element,
what happens if I specify null? Does this still put
>the name of the output on the command
line? A lot of our tools will
>automagically name the output files
based on the output file and don’t allow
>you to specify the output name of
these files, so not only can you not provide
>the filename with a flag, but you
can’t provide the name at all as this is
>illegal usage of the tool.
Would it meet your needs if
primaryOutput=False and option not specified
meant to not add the output file to the
command line at all?
Regards,
Leo
From: cdt-dev-admin@xxxxxxxxxxx
[mailto:cdt-dev-admin@xxxxxxxxxxx] On Behalf
Of Recoskie, Chris
Sent: Friday, March 11, 2005 3:32
PM
To: cdt-dev@xxxxxxxxxxx
Subject: RE: [cdt-dev] Feedback on
"Multiple Tool Inputs and Outputs design"
In addition to the feedback from Lars (who
thought of a lot of the same things I did so I won’t bother rehasing
them):
InputDetail
Schema
- Just
a comment: although I can imagine some interesting ways of utilizing
it, I don’t know how much people are going to use the Input etail
element in their toolchain plugins as a static definition. This is
probably the source of some of Lars’ confusion. I am
assuming Leo is not really intending this element for this purpose and
really this is intended for use as an internal model element which is
going to be utilized by some sort of “link order properties
editor” type thing. The idea is that this element would be
created on a per-resource basis prior to project build as the user changes
the settings on various source files to exclude them from build, customize
their link order, etc.
- Q:
What are we doing to provide for a default GUI for editing the input
ordering?
OutputType Schema
- Re:
the “option” element, what happens if I specify null?
Does this still put the name of the output on the command line?
A lot of our tools will automagically name the output files based on
the output file and don’t allow you to specify the output name of
these files, so not only can you not provide the filename with a flag, but
you can’t provide the name at all as this is illegal usage of the
tool.
___________________________________________
Chris Recoskie
Texas Instruments, Toronto
From:
cdt-dev-admin@xxxxxxxxxxx [mailto:cdt-dev-admin@xxxxxxxxxxx] On Behalf Of Lars.Kurth@xxxxxxxxxxx
Sent: Friday, March 11, 2005 2:15
PM
To: cdt-dev@xxxxxxxxxxx
Subject: Re: [cdt-dev] Feedback on
"Multiple Tool Inputs and Outputs design"
Leo,
please
find attached some feedback. The proposal looks good (-:
Regards
--
Lars
"Treggiari, Leo"
<leo.treggiari@xxxxxxxxx>
Sent
by: cdt-dev-admin@xxxxxxxxxxx
10/03/2005
17:25
Please respond
to
cdt-dev@xxxxxxxxxxx
|
|
To
|
<cdt-dev@xxxxxxxxxxx>
|
cc
|
|
Subject
|
[cdt-dev] (no subject)
|
|
Hi All,
I have
added a Bugzilla enhancement request with the Multiple Tool Inputs and Outputs design
attached - see the Bug 87673:
(https://bugs.eclipse.org/bugs/show_bug.cgi?id=87673)
The
multiple tool inputs and outputs support is one of the MBS enhancements planned
to be implemented in the Managed Build System (MBS) for
the
CDT 3.0 release (see also "Proposed Managed Build System functionality for
CDT 3.0" ( https://bugs.eclipse.org/bugs/show_bug.cgi?id=81450 ))
Thanks,
Leo
**********************************************************************
Symbian Software Ltd is a company registered in England and Wales with
registered number 4190020 and registered office at 2-6 Boundary Row, Southwark,
London, SE1 8HP, UK. This message is intended only for use by the named
addressee and may contain privileged and/or confidential information. If you
are not the named addressee you should not disseminate, copy or take any action
in reliance on it. If you have received this message in error please notify
postmaster@xxxxxxxxxxx and delete the message and any attachments accompanying
it immediately. Neither Symbian nor any of its subsidiaries accepts liability
for any corruption, interception, amendment, tampering or viruses occurring to
this message in transit or for any message sent by its employees which is not
in compliance with Symbian corporate policy.
**********************************************************************