Eclipse Community Forums: DSDP - Real-Time Software Components (RTSC)

Home » Archived » DSDP - Real-Time Software Components (RTSC) » How to include opts-file?

How to include opts-file? [message #1917]

Tue, 17 March 2009 14:54

Eclipse User

Champs,

I'm trying to include an opts-file from another opts-file, but I'm getting the following error.

xs.opts
--xdcpath=^/../imports;/db/toolsrc/library/tools/packages;/h ome/xlibrary/trees/avalaprod/avalaprod-d23/product/bios_6_20 _00_23/packages;/home/xlibrary/trees/ipc/ipc-b27/product/ipc _1_00_00_27/packages;^/ti/sdo/fc/utils/bridgeconfig;/db/tool src/library/tools/vendors/ti/edma3_lld/edma3_lld_1_06_00_01/ packages

xdc.opts
@xs.opts
XDCARGS=profile=debug

xdc @$fc/xdc.opts .interfaces -PR .

/db/toolsrc/library/tools/vendors/xdc/xdctools_3_15_00_28/Li nux/xdc: unable to e
xpand command line arguments: can't open argument file

Any suggestions. Thanks.
~ Ramsey

Re: How to include opts-file? [message #1931 is a reply to message #1917]

Wed, 18 March 2009 10:55

Eclipse User

Ramsey Harris wrote:
> Champs,
>
> I'm trying to include an opts-file from another opts-file, but I'm
> getting the following error.
>
> xs.opts
> --xdcpath=^/../imports;/db/toolsrc/library/tools/packages;/h ome/xlibrary/trees/avalaprod/avalaprod-d23/product/bios_6_20 _00_23/packages;/home/xlibrary/trees/ipc/ipc-b27/product/ipc _1_00_00_27/packages;^/ti/sdo/fc/utils/bridgeconfig;/db/tool src/library/tools/vendors/ti/edma3_lld/edma3_lld_1_06_00_01/ packages
>
>
> xdc.opts
> @xs.opts
> XDCARGS=profile=debug
>
> xdc @$fc/xdc.opts .interfaces -PR .
>
> /db/toolsrc/library/tools/vendors/xdc/xdctools_3_15_00_28/Li nux/xdc:
> unable to e
> xpand command line arguments: can't open argument file
>
>
> Any suggestions. Thanks.
> ~ Ramsey
The error indicates that xs.opts file can not be opened. Is it in the
current working directory when you run xdc? It appears that xdc.opts is
not.

Re: How to include opts-file? [message #1945 is a reply to message #1931]

Fri, 27 March 2009 19:50

Eclipse User

dave russo wrote:
> Ramsey Harris wrote:
>> Champs,
>>
>> I'm trying to include an opts-file from another opts-file, but I'm
>> getting the following error.
>>
>> xs.opts
>> --xdcpath=^/../imports;/db/toolsrc/library/tools/packages;/h ome/xlibrary/trees/avalaprod/avalaprod-d23/product/bios_6_20 _00_23/packages;/home/xlibrary/trees/ipc/ipc-b27/product/ipc _1_00_00_27/packages;^/ti/sdo/fc/utils/bridgeconfig;/db/tool src/library/tools/vendors/ti/edma3_lld/edma3_lld_1_06_00_01/ packages
>>
>>
>> xdc.opts
>> @xs.opts
>> XDCARGS=profile=debug
>>
>> xdc @$fc/xdc.opts .interfaces -PR .
>>
>> /db/toolsrc/library/tools/vendors/xdc/xdctools_3_15_00_28/Li nux/xdc:
>> unable to e
>> xpand command line arguments: can't open argument file
>>
>>
>> Any suggestions. Thanks.
>> ~ Ramsey
> The error indicates that xs.opts file can not be opened. Is it in the
> current working directory when you run xdc? It appears that xdc.opts is
> not.

Using a full pathname to xs.opts in xdc.opts worked. I was not in the same directory as the opts files when I ran the xdc command. But it would be more useful if I could specify xs.opts relative to xdc.opts.

Re: How to include opts-file? [message #1956 is a reply to message #1945]

Tue, 31 March 2009 11:01

Eclipse User

Ramsey Harris wrote:
>>> xdc.opts
>>> @xs.opts
>>> XDCARGS=profile=debug
>>>
>>> xdc @$fc/xdc.opts .interfaces -PR .
>>>
>>> /db/toolsrc/library/tools/vendors/xdc/xdctools_3_15_00_28/Li nux/xdc:
>>> unable to e
>>> xpand command line arguments: can't open argument file
>>>
>>>
>>> Any suggestions. Thanks.
>>> ~ Ramsey
>> The error indicates that xs.opts file can not be opened. Is it in the
>> current working directory when you run xdc? It appears that xdc.opts
>> is not.
>
> Using a full pathname to xs.opts in xdc.opts worked. I was not in the
> same directory as the opts files when I ran the xdc command. But it
> would be more useful if I could specify xs.opts relative to xdc.opts.
Agreed. It would also be useful to be able to use environment variables
from within these files.

A useful enhancement request might be to add the ability to reference
environment variables using a syntax similar to make (e.g., $(HOME)).
At the same time we can create a few "builtins" that allow on to
reference the script's location, basename, etc. This would allow you to
easily compose a file that references other opts files in the same or
releated directories.

Previous Topic:	RTSC Tutorial at EclipseCon 2009
Next Topic:	Proper way to configure C only target

Goto Forum:

-=] Back to Top [=-

Current Time: Thu Jul 24 11:13:48 EDT 2025

.:: Contact :: Home ::.

Breadcrumbs

Sign up to our Newsletter