[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
RE: [cdt-dev] Feedback on "Multiple Tool Inputs and Outputs design"
|
Ah right... forgot about that. Doh.
___________________________________________
Chris Recoskie
Software Designer
IDE Frameworks Group
Texas Instruments, Toronto
> -----Original Message-----
> From: cdt-dev-admin@xxxxxxxxxxx [mailto:cdt-dev-admin@xxxxxxxxxxx] On
> Behalf Of Treggiari, Leo
> Sent: Monday, March 14, 2005 1:40 PM
> To: cdt-dev@xxxxxxxxxxx
> Subject: RE: [cdt-dev] Feedback on "Multiple Tool Inputs and Outputs
> design"
>
> Hi Chris,
>
> You should be able to prevent the output file from appearing on the
> command line by specifying for the Tool:
>
> commandLinePattern="${COMMAND} ${FLAGS} ${INPUTS}"
>
> Please give that a try and see if it works for your tools.
>
> Regards,
> Leo
>
> ________________________________________
> From: cdt-dev-admin@xxxxxxxxxxx [mailto:cdt-dev-admin@xxxxxxxxxxx] On
> Behalf Of Recoskie, Chris
> Sent: Monday, March 14, 2005 8:29 AM
> To: cdt-dev@xxxxxxxxxxx
> Subject: RE: [cdt-dev] Feedback on "Multiple Tool Inputs and Outputs
> design"
>
> In the case of our linker it's actually fine as we can specify the output
> file, but our compilers and assemblers, for whatever arcane reasons, don't
> allow you to specify the name of the .obj files (although you can specify
> the directory where they will be output to).
>
> Right now to deal with this I have my own makefile generator that is 90% a
> clone of the stock one, and in that generator I just don't put the output
> file on the command line.
>
> ___________________________________________
>
> Chris Recoskie
> Software Designer
> IDE Frameworks Group
> Texas Instruments, Toronto
>
>
> ________________________________________
> From: cdt-dev-admin@xxxxxxxxxxx [mailto:cdt-dev-admin@xxxxxxxxxxx] On
> Behalf Of Treggiari, Leo
> Sent: Monday, March 14, 2005 8:11 AM
> To: cdt-dev@xxxxxxxxxxx
> Subject: RE: [cdt-dev] Feedback on "Multiple Tool Inputs and Outputs
> design"
>
> Hi Chris,
>
> A primary output does need to be specified. The additional (non-primary)
> outputs also need to be specified, if they are inputs to other tools.
> This would allow these secondary outputs to be "silent" as far as the
> command line is concerned. How do your tools handle the primary output?
> Does it appear on the command line?
>
> Leo
>
> ________________________________________
> From: cdt-dev-admin@xxxxxxxxxxx [mailto:cdt-dev-admin@xxxxxxxxxxx] On
> Behalf Of Recoskie, Chris
> Sent: Monday, March 14, 2005 7:52 AM
> To: cdt-dev@xxxxxxxxxxx
> Subject: RE: [cdt-dev] Feedback on "Multiple Tool Inputs and Outputs
> design"
>
> >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?
>
> Won't this mess up the dependency rules then if there is no primary
> output? You also need this so that MBS can determine the build artifact.
>
> ___________________________________________
>
> Chris Recoskie
> Software Designer
> IDE Frameworks Group
> Texas Instruments, Toronto
>
> _______________________________________________
> cdt-dev mailing list
> cdt-dev@xxxxxxxxxxx
> http://dev.eclipse.org/mailman/listinfo/cdt-dev
