You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Essentially, I'd like to have a build option to make the created executable never produce configs in the local folder. Currently, as I can see, it is possible to force such a behavior on the executable, by creating a file named nonportable next to the executable, however, it's not always adequate to place such stub files next to the executable (For example, on linux, all executables installed with package managers are stored in one folder and that folder is intended only for executables).
It seems like this Features thing might be useful to accomplish this task.
The text was updated successfully, but these errors were encountered:
Essentially, I'd like to have a build option to make the created executable never produce configs in the local folder. Currently, as I can see, it is possible to force such a behavior on the executable, by creating a file named
nonportable
next to the executable, however, it's not always adequate to place such stub files next to the executable (For example, on linux, all executables installed with package managers are stored in one folder and that folder is intended only for executables).It seems like this Features thing might be useful to accomplish this task.
The text was updated successfully, but these errors were encountered: