ouille wrote:
I don't want to have n bin directorys, and i can't set all dll in the system as it is more problematic to check dll dependency.
Regarding to the DLL location: Isn't it possible to have all dependencies in one directory, e. g. the folder from the SDK and only create a symbolic link or alias - whatever it is called under Windows to share the files, so you're able to work and test the application outside the mainline production?
Hope this is useful for you, I'll give a short view about my handling object procedure:
- All Raydium dependencies are located globally in /opt/raydep/*/{i386,ppc,universal}/{include,lib}.
- Application directory contains an alias locally to the needed dependencies, e. g. "ln -s /opt/raydep/*/universal/* ." under *nix.
- On package progress the links are resolved to the real files whenever needed.
Regarding to the data path settings, I'm not using a bin folder for my binaries, so I'm able to use raydium_path_add("Resources"); after the Raydium initialization, because Raydium automatically changes to the right directory, where the files are located "*.app/Contents/{MacOS/Binary,Resources/Data.*}".
I hope this is helpful for you, since I don't really understand what do you want to do.
