In message <[email protected]>
          Ron <[email protected]> wrote:

> In message <[email protected]>
>           John Tytgat <[email protected]> wrote:
> 
> > 
> > I expect that if you remove c/h/o etc from gcc (and related programs) sfix
> > you can have the RISC OS filenames foo/c and bar.foo/c (instead of c.foo,
> > bar.c.foo) but I never have tried that.  Although I'm not really found
> > of c.foo style of RISC OS filenames, I don't see a point of forcing
> > developers to take another file hierarch approach of their sources then
> > they are used by the Norcroft compiler suite.  It doesn't make sense
> > to break compatibility as there is no gain.
> > 
> > John.
> 
> That is effectively what I have had success with, using a helloworld/c
> type directory system and sfix ="" for the binary line up in !Run.
> It is then neccessary to use gcc helloworld/c (not helloworld.c)
> otherwise you get "file not found", and it appeared to be working
> that way OK. 
<snip first attempt>
It's working as it should now, after setting the !Run file properly.
I was using the line 
Set UnixEnv$gcc$sfix ""
to set the binaries with the standard 
Set UnixEnv$cc1$Sfix <UnixEnv$gcc$sfix>
but this doesn't work.
I now have 
| Set UnixEnv$gcc$sfix     
commented out, and the binaries set directly to ""
Set UnixEnv$cc1$sfix ""
Set ....

and everything is compiling exactly as it would do normally.
I haven't tested extensively, but all the stages are working with
gcc helloworld.c 
and gcc -c helloworld  will output helloworld/o and the linking
finds it Ok too.
This also means that makefiles will work without change and should
work better in the case of 
 y/tab/c   and   y/tab/h which required making the special directories
 and manually moving the object file into place for linking each time. 
Until I remove the upstream special sfixing, I may have to 
Set UnixEnv$yacc$sfix "" so it works with the unix naming as well.
 
Thanks,  RonM.

_______________________________________________
GCCSDK mailing list [email protected]
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

Reply via email to