Dear Andreas,

Great, thank you very much! I just realised that this works for any data in x-ozlib://. For example, I created a test file $OZHOME/cache/ x-ozlib/myfile.xml (i.e. not in ~/.oz) and

  {Resolve.localize 'x-ozlib://myfile.xml'}

returned the correct path -- wow!

Just mkdir -p $OZHOME/cache/x-ozlib and put your functors there.

ozmake kindly supports the option --prefix, which makes it even simpler / more clean.

Best
Torsten

On Sep 11, 2007, at 4:32 PM, Andreas Franke wrote:
Torsten Anders wrote:
As far as I understand, 'x-ozlib://' is a platform independent path
which points, e.g., into ~/.oz/1.3.2/cache/x-ozlib. So, if I want to
import functors using this platform independent path 'x-ozlib://',
then they must be installed for every user in its home directory? Yes?
[...]
'x-oz' points into Mozarts installation directory, but naturally we
don't want to store user functors there...

I think the story is a different one.  The environment variable
OZ_SEARCH_LOAD (or OZ_LOAD or OZLOAD) determines
where functors are searched, defaulting to

        'cache='#OZ_DOTOZ#'/cache'#[PATH_SEPARATOR]#
        'cache='#OZ_HOME#'/cache'

(see share/lib/init/Prop.oz).
So unless the user has one of these environment variables set,
any functor is first looked for in ~/.oz/1.3.2/foo,
and if that fails, in $OZHOME/cache/foo.

Just mkdir -p $OZHOME/cache/x-ozlib
and put your functors there.  Of course, this
allows users to override your global installation.

Gruss,
Andreas

______________________________________________________________________ ___________ mozart-users mailing list mozart- [EMAIL PROTECTED]
http://www.mozart-oz.org/mailman/listinfo/mozart-users

--
Torsten Anders
Interdisciplinary Centre for Computer Music Research
University of Plymouth
http://strasheela.sourceforge.net
http://www.torsten-anders.de


_________________________________________________________________________________
mozart-users mailing list                               
[email protected]
http://www.mozart-oz.org/mailman/listinfo/mozart-users

Reply via email to