Environment Variables
Description: C source code API documentation for the Oyranos project.
Keywords: Oyranos,Color Management,Color Management,ICC,CMS,C,doxygen,API,documentation

| Oyranos Color Management System API - Version 0.9.6

Environment Variables

# Path Variables

The XDG variables affect Oyranos' profile search. Oyranos searches under each provided paths color/icc directory, e.g. XDG_DATA_HOME=~/.local/share results in a additional search in ~/.local/share/color/icc. More details can be found in OpenIccDirectoryProposal at ColourWiki.

# Internationalisation Variables

OY_LOCALEDIR is described together with the internal oy_domain_codeset.

# Runtime Variables

OY_MODULE_PATH can contain paths to meta and normal modules together. The given paths are scanned recursively to find the modules.

# Debugging Variables

OY_DEBUG influences the internal oy_debug variable. Its value changes the output level. See as well oyranos_debug.[h,c] . The configure switch –enable-debug enables most of the available output.
OY_DEBUG_MEMORY sets the internal ::oy_debug_memory variable on and helps somewhat in detecting memory leaks. This variable is dangerous and should not to be run for production use.
OY_DEBUG_OBJECTS is used to frequently print infos about objects on stderr. The value of OY_DEBUG_OBJECTS can be a

- Object ID or a
- type name like "oyImage_s","Image" to track all oyImage_s type objects or
- "1" to print track informations about all trackable objects.
- "-1" to omit printing track informations.

OY_DEBUG_SIGNALS sets the internal ::oy_debug_signals variable on and helps in tracing signals. This variable is dangerous and should not to be run for production use.
OY_DEBUG_WRITE together with OY_DEBUG is used to tell, that a file output is appreciated. Writing files will usually slow down debugging.
OY_BACKTRACE can be set to a debug message string and will then place a backtrace text from gdb into the console. That needs the debug message to be visible.