To avoid possible clashes, it has been recommended to allow for custom namespace setting.
Currently MaterialX has a hard-coded name space but this could be settable via a Cmake option
as is done for OCIO. Then each integration can set it's own namespace to help avoid clashes if MaterialX
is pulled in via multiple integrations.
To avoid possible clashes, it has been recommended to allow for custom namespace setting. Currently MaterialX has a hard-coded name space but this could be settable via a Cmake option as is done for OCIO. Then each integration can set it's own namespace to help avoid clashes if MaterialX is pulled in via multiple integrations.