Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!uupsi!sunic!ugle.unit.no!dhmyrdal
From: dhmyrdal@lise.unit.no (Dag H}kon Myrdal)
Newsgroups: comp.sys.acorn
Subject: Re: Freeze - Arc version - Compiling C programs - a standard ?
Keywords: Freeze, C library standard
Message-ID: <1991Jun3.162233.11103@ugle.unit.no>
Date: 3 Jun 91 16:22:33 GMT
References: <&+3_98|@warwick.ac.uk>
Sender: news@ugle.unit.no
Organization: University of Trondheim
Lines: 23

In article <&+3_98|@warwick.ac.uk> maumg@warwick.ac.uk (Pop Mobility Freak) writes:
[...]
>
>However I believe we ought to come to an unoffical standard about using
>operating system variables to locate libraries as everyone will want to store
>the libraries in different places. This would prevent names being hardwired
>into makefiles. I recomend the ones I have used above as a draft standard.
>That is <C$LibRoot> for the CLib and <C$Loc>.<library name> for any others
>(for example RiscOsLib and Utils). So how about it? Anyone got any strong
>feelings either way to adopting this naming convention as an unofficial
>standard? The reason I selected these is they are set during the obey file
>CStart provided with C, although C$Loc is unset again (this can easily be
>removed).
>

Why don't you use <RUN$Path> for utils? Risc OS looks up all
directories in this path automatically when you want to run an
application or utility. I myself set this in my main !boot file 
to point at *all* places where I store utilities, so that if people 
*dont* fuss about putting paths pointing at various utils in makefiles
everything will be OK!

--Dag