Re: Executable & libraries in one folder, but force it's output into different folder
The setup is totally non-Unixish. Even on Windows now it's a capital sin to mix user data and executable code in the same directories.... if only because as you saw this often puts your data in jeopardy.
You don't tell us why it writes files in specific directories. Is it because it is the current directory when it starts? Or because it finds it using the location of the executable itself? If the latter there are likely ways to trick it using links in the proper directories. Typically you would set up a directory for data and put in it links to the executable files installed elsewhere. This way you can put th executable files in a public place, and keep the data separately (and each user with his own set of data). Of course you would start the application using the "user" links.
Warning: unless noted otherwise, code in my posts should be understood as "coding suggestions", and its use may require more neurones than the two necessary for Ctrl-C/Ctrl-V.
Bookmarks