-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

nelson sandalwood <nel### [at] zoismorg> wrote:
> 
> Is this right?  Shouldn't it just look in the library path for any .ini
> file, and why does it not need the .ini for a full path?

Your little problem sounded kinda interesting, so I spent some more of
the little time that I don't have to try to see why povray doesn't look
in the ini directory for ini files.  The answer's pretty simple, so if
it sounds confusing, it's just because I'm tired and I need to go to bed
:).

So here's the deal:  From what I can tell, povray does not know that it
has a default library path.  It loads it library path from the command
line or from an ini file.  So, simply put, without knowing exactly where
the ini file is, povray can't load the Library_Path to know where to
look for the ini file.  Yes, the program could be modified to look in
the .../share/ini directory for ini files until it successfully loads
one, but it doesn't and the change would not be trivial.

There is supposed to be one way you could get things to work the way you
want, but there seems to be a bug (at least in my build) that prevents
it from working.  What you should be able to do is create a basic ini
file that simply set the Library_Path so that povray could find other
ini files.  Set the environment variable POVINI to the full path of this
ini file, then try running povray as you did before.  The $POVINI file
should be loaded before povray goes out looking for slow.ini, and so it
should search the library paths you list.  However, as I was saying,
povray is throwing an assertion whenever I set POVINI, so there seems to
be a bug hiding somewhere in there that needs to be fixed first.

Hope That Helped,
  Karmix
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.7 (GNU/Linux)

iD8DBQE/FoDn8/zoYc8slRERAqrHAJ4seAAsgDZ/rgSUHpOO5Sf/xbtoyQCfVIGe
Dh0jQhnbkr9N5PwZgZNcYEI=
=DZiY
-----END PGP SIGNATURE-----

Post a reply to this message