[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
RE: [cdt-dev] Behavior of ${value} in tool options
|
As far as I know anything with a browseType of file or directory should
have the quotes automatically put on there for you if you actually
browsed to the file. Is this not the case anymore?
___________________________________________
Chris Recoskie
Software Designer
Texas Instruments, Toronto
http://eclipse.org/cdt
> -----Original Message-----
> From: cdt-dev-bounces@xxxxxxxxxxx [mailto:cdt-dev-bounces@xxxxxxxxxxx]
On
> Behalf Of dmsubs
> Sent: Thursday, December 08, 2005 11:39 AM
> To: 'Treggiari, Leo'; 'CDT General developers list.'
> Subject: RE: [cdt-dev] Behavior of ${value} in tool options
>
> Leo,
>
> Thanks for the suggestion, but unfortunately backslashes are stripped
from
> ${value}. This means "c:\top level\filename" becomes "c:top
> levelfilename".
> Which is not what I want!
>
> Chris has suggested that I enclose the string in quotes manually. This
is
> a
> workaround, but its not at all nice - having browsed to a file, the
user
> then needs to add the quotes - yuk!
>
> Is this worthy of a bugzilla enhancement request?
>
> ---
> Derek
>
> > -----Original Message-----
> > From: Treggiari, Leo [mailto:leo.treggiari@xxxxxxxxx]
> > Sent: 08 December 2005 16:28
> > To: Derek.Morris@xxxxxxxxxxxxx; CDT General developers list.
> > Subject: RE: [cdt-dev] Behavior of ${value} in tool options
> >
> > Hi Derek,
> >
> > Try
> > command='--reportpath="${value}"'
> >
> > Regards,
> > Leo
> >
> > -----Original Message-----
> > From: cdt-dev-bounces@xxxxxxxxxxx
[mailto:cdt-dev-bounces@xxxxxxxxxxx]
> > On Behalf Of dmsubs
> > Sent: Thursday, December 08, 2005 11:20 AM
> > To: 'CDT General developers list.'
> > Subject: [cdt-dev] Behavior of ${value} in tool options
> >
> > Hi,
> >
> > With my tool, there is an option to output a report file. The
> > syntax is:
> >
> > toolname --reportfile="path" ...
> >
> > In my plugin, I have created an option like this:
> > <option
> > browseType='file'
> > category='toolchain.optionCategory.output'
> > command='--reportpath="${value}"'
> > id='toolchain.output.reportpath'
> > name='Report file'
> > resourceFilter='all'
> > valueType='string'
> > ></option>
> >
> > Under Windows, the selected filename (${value}) is placed
> > into the command stripped of backslashes.
> >
> > If I change the command to:
> > command='--reportpath='
> > Then the filename is appended to the command. However, if the
> > filename contains spaces (e.g. c:\Documents and Settings...)
> > then my tool does not parse the command line properly.
> >
> > Can anybody suggest how I can overcome this problem?
> >
> > Thanks,
> >
> > ---
> > Derek
> >
> >
> > _______________________________________________
> > 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
