Skip to content

fix(core): make material resource file handling project independent

Description

Make resources.cfg path treatment independent of the working dir. Indeed, the present behavior uses the working dir for the absolute path generation. However, as this is done inside sight code, the prefix corresponds to the sight install path, and not the loading module-specific path. As a result, files that are not installed in the sight install dir can not be loaded.

It is safer to rely on the module name, and get its specific path.

Closes #734 (closed)

How to test it?

Use an application that has specific ogre materials or shaders.

  • Build, run it and verify that the resources files are correctly loaded.
  • Download, install and run packaged applications from Owncloud (they are already generated with the id 21.0.0.beta-523-gb9ea387223
Edited by Flavien BRIDAULT

Merge request reports