Re: Standard OCIO Directories


Paul Miller <pa...@...>
 

On 4/18/2012 1:35 PM, Brendan Bolles wrote:
On Apr 18, 2012, at 11:06 AM, László Sebő wrote:

1. $OCIO (get the config from the variable)
2. relative search path starting at so/dll folder: OCIOConfigs/configs/<appname>-default (to follow nuke's arbitrary standard)
3. "<user folder>/OCIO/default/config.ocio" (ex: on win7: c:/Users/me/OCIO/default/config.ocio", on linux: ~/.OCIO/default/config.ocio)
4. "<common appdata>/OCIO/default/config.ocio" (ex: on win7: c:/ProgramData/OCIO/default/config.ocio", on linux: /etc/OCIO/default/config.ocio)

Right. I've already got the<common appdata> thing going per your suggestion. I'd like to hear other people's opinions on the others. If this list gets expansive, maybe some official code should be added for getting an array of available configurations.

I'm currently doing<common appdata>/OpenColorIO, not<common appdata>/OCIO. Which do people think would be better?
I like It spelled out OpenColorIO.

How about an additional env var: OCIO_CONFIGS, which can be set to a ;-separated list of paths. The default would be the ones you've been talking about.

Have paths closer to the front of the list override ones further back (so I can stick my own hacked copy of nuke-default in my home directory if I want to).

Join ocio-dev@lists.aswf.io to automatically receive all group messages.