Thanks,
If you really want to split the app into binary and config etc, you can do it with the current versions using a LDCad.cfg in the same location as the main executable (this is essentially what the windows setup version does, as it's exe etc is identical to the archive one).
In the LDCad.cfg you just point to the absolute locations of the various locations.
Example LDCad.cfg (only config is redirected, rest uses the default)
This is somewhat untested for the linux version though.
If you really want to split the app into binary and config etc, you can do it with the current versions using a LDCad.cfg in the same location as the main executable (this is essentially what the windows setup version does, as it's exe etc is identical to the archive one).
In the LDCad.cfg you just point to the absolute locations of the various locations.
Example LDCad.cfg (only config is redirected, rest uses the default)
Code:
[paths]
logDir=<appDir>/logs
cfgDir=/path/to/config/location
guiDir=<appDir>/gui
resourcesDir=<appDir>/resources
colorBinDir=<appDir>/colorBin
partBinDir=<appDir>/partBin
examplesDir=<appDir>/examples
templatesDir=<appDir>/templates
donorsDir=<appDir>/donors
shadowDir=<appDir>/shadow
dirSeeds=<appDir>/seedsThis is somewhat untested for the linux version though.