The issue with this is, one may not be able to guarantee the running process will stay in the same current directory during its whole lifetime. So it would be better if it was possible to specify the absolute path of the EFAL data directory independent from the current working directory.
We already talked to the Pitney Bowes support. They confirmed this is currently a missing feature.
One possibility would be a new API call like EFALSetDataDirectory() to configure this path for the EFAL library.Another conceivable possibility would be an environment variable like e.g. EFAL_DATA_DIR.