Eclipse Community Forums
Forum Search:

Search      Help    Register    Login    Home
Home » Eclipse Projects » DSDP - Real-Time Software Components (RTSC) » recommended way to put XDC paths in a file?
recommended way to put XDC paths in a file? [message #760] Tue, 13 January 2009 13:07 Go to next message
Alan Campbell is currently offline Alan Campbell
Messages: 3
Registered: July 2009
Junior Member
hello,

What's the recommended way to put a big long XDC path in a file? I've seen
a few diff't ways hence thot I'd ask i.e.

1. TI DM6437 EVM DVSDK CCS 3.3 pjt files use: -
--xdcpathsfile="xdcpaths.dat"
where xdcpaths.dat contains
xdcpaths = "a/packages" + "b/packages" + "";

What's nice here is that cos its Javascript can set a var at top-level and
dodge hardcoded paths

But OTOH --xdcpathsfile is not documented in
http://rtsc.eclipse.org/docs-tip/Command_-_xdc hence is it only a CCS 3.3
Built Tools Interface thing?

2. Use xs @paths.txt
where @paths.txt =

--xdcpath
/all/pkg/paths/in/1/big/long/line

Disadvantage here is hardcoded paths & "1 big long line"

Don't see any options in the BTI in CCSv4 Beta 2.1 for this so not sure
what the recommendation is.

Thanks.
Re: recommended way to put XDC paths in a file? [message #767 is a reply to message #760] Tue, 13 January 2009 13:47 Go to previous message
Dave Russo is currently offline Dave Russo
Messages: 172
Registered: July 2009
Senior Member
Alan Campbell wrote:
> hello,
>
> What's the recommended way to put a big long XDC path in a file? I've
> seen a few diff't ways hence thot I'd ask i.e.
>
> 1. TI DM6437 EVM DVSDK CCS 3.3 pjt files use: -
> --xdcpathsfile="xdcpaths.dat"
> where xdcpaths.dat contains xdcpaths = "a/packages" + "b/packages" + "";
>
> What's nice here is that cos its Javascript can set a var at top-level
> and dodge hardcoded paths
>
> But OTOH --xdcpathsfile is not documented in
> http://rtsc.eclipse.org/docs-tip/Command_-_xdc hence is it only a CCS
> 3.3 Built Tools Interface thing?
>
It seems to be, yes. I'm not aware of a --xdcpathsfile option.

> 2. Use xs @paths.txt
> where @paths.txt =
> --xdcpath
> /all/pkg/paths/in/1/big/long/line
>
> Disadvantage here is hardcoded paths & "1 big long line"
Yep, the syntax of "@" files is very primitive and can certainly be
improved.

It is relatively easy to enhance the syntax of the lines supported in
"@" files. One obvious enhancement is to define a '\' at the end of a
line to be a "line continuation" character.

The other enhancement I've always wanted is to support environment
variable expansion. So a line such as "$(TOOLS)/packages" would expand
into the current value of the TOOLS environment variable followed by
"/packages".

Bugzilla enhancement requests are welcome;
https://bugs.eclipse.org/bugs/enter_bug.cgi?bug_severity=enh ancement&bug_status=NEW&component=Core&contentty pemethod=autodetect&contenttypeselection=text%2Fplain&am p;form_name=enter_bug&op_sys=All&priority=P3&pro duct=RTSC&rep_platform=All&version=unspecified


>
> Don't see any options in the BTI in CCSv4 Beta 2.1 for this so not sure
> what the recommendation is.
>
> Thanks.
>
Previous Topic:preserving package/info/*.js in xdc clean
Next Topic:Async errors
Goto Forum:
  


Current Time: Fri Apr 18 06:35:26 EDT 2014

Powered by FUDForum. Page generated in 0.02535 seconds