Example of problem
It looks like the expected location of proj.db ./share/proj is not a valid location when installing a macOS package .dmg containing the libproj.
Indeed, macOS package uses completelly different directory architectures, such a file would be expected to be put in ./Resources.
While proj consumer would probably be able to handle that by specifying to proj where to look for proj.db, I think this may the PROJ responsability to pick the right location, or at least to offer a CMake option to select the default behavior.
Current code src/filemanager.cpp:
// The initial path was something like foo/bin/libproj.so"
out += "/share/proj";
return out;
Could be something like:
// The initial path was something like foo/bin/libproj.so"
#if PROJ_MACOS_BUNDLE
out += "/Resources";
#else
out += "/share/proj";
#endif
return out;
Let me know if this is something PROJ should be supporting.
Example of problem
It looks like the expected location of proj.db
./share/projis not a valid location when installing a macOS package .dmg containing the libproj.Indeed, macOS package uses completelly different directory architectures, such a file would be expected to be put in
./Resources.While proj consumer would probably be able to handle that by specifying to proj where to look for proj.db, I think this may the PROJ responsability to pick the right location, or at least to offer a CMake option to select the default behavior.
Current code
src/filemanager.cpp:Could be something like:
Let me know if this is something PROJ should be supporting.