On 19 Jun, Ben Avison wrote in message
<1691d959-4512-4d1b-7969-3091a9090...@riscosopen.org>:
> The usual way to handle this is to use POSIX-style filenames in the actual
> source code and let the tools detect that a subdirectory is in use instead
> of an extension. asasm appears to do this both as a native RISC OS tool
> and when used in a cross-compilation environment. If objasm compatibility
> matters to you, note that it only tries to interpret the filename as
> POSIX-style if it contains a slash, i.e. you'd need to use "GET
> ./include.h".
Thanks; that makes sense. The source code that I've got is all laid out
POSIX-style, so I've not knowingly encountered a situation when it would
need to translate.
--
Steve Fryatt - Leeds, England
http://www.stevefryatt.org.uk/
_______________________________________________
GCCSDK mailing list gcc@gccsdk.riscos.info
Bugzilla: http://www.riscos.info/bugzilla/index.cgi
List Info: http://www.riscos.info/mailman/listinfo/gcc
Main Page: http://www.riscos.info/index.php/GCCSDK
