On Sun, Feb 01, 2015 at 02:02:48PM -0000, WPB wrote:
> What would be great is if there was a way to make the dependencies
> output use a RISC OS system variable -- ideally GCCbin$Path looks
> the most sensible -- so that absolute paths aren't hard-coded into
> the dependencies file in the first place. Is there a way to do this?
> And will it resolve the colon problem anyway?
There's a variable RO_ENV, for example
RO_ENV=/home/riscos/env
Then you can use /home/riscos/env/foo/bar/baz and it'll get translated into
foo:bar.baz in RISC OS land. I think the Unix paths get compiled into the
executable and then fixed up at runtime.
It appears RO_ENV is a build-time constant rather than a Unix environment
variable, since the check against RO_ENV happens at RISC OS runtime.
However, that block of code
http://www.riscos.info/websvn/filedetails.php?repname=gccsdk&path=%2Ftrunk%2Fgcc4%2Frecipe%2Ffiles%2Fgcc%2Flibunixlib%2Fcommon%2Friscosify.c
is surrounded by:
/* FIXME: the __ELF__ test is a hack until our ELF build system @ GCCSDK 4
has a concept of RO_ENV. Also test/filename/testriscosify.c needs to be
changed. */
#ifndef __ELF__
/* /home/riscos/env/xxx. (or configured path) Try matching
xxx segment. */
which suggests this has been removed in GCCSDK 4. Anyone know whether
GCCSDK 'has a concept of RO_ENV' yet? In other words, a way for UnixLib
when building to embed GCCSDK_INSTALL_ENV inside it?
Theo
_______________________________________________
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
No comments:
Post a Comment