Le 9 nov. 2017 à 10:18, Guillermo Polito <guillermopolito@gmail.com> a écrit :
- launching Pharo from the pharo launcher (taken from this thread) Apparently the pharo launcher is launching the image from a directory internal to the launcher.
In the Pharo launcher, I explicitly set the current working directory to the VM directory so that the VM can find its files.
This means that the working directory will be assigned to that directory. I'd expect that the directory structure is private to the launcher... I find even strange that the launcher puts pharo-local where the image isâ¦
Pharo Launcher does not choose where to put pharo-local. It just stands in the standard place aside the launched image.
Given this, possible solutions are: - On fileout, chose a correct directory when launched from double click - Make the pharo launcher set a well-known working directory when launching an image - one possibility is to set $HOME - another possibility is to set the image directory (this will keep backwards compatibility)
I think the last solution: set the working directory to the image directory is the best option. It will require to find another way to get the vm find its files (probably with LD_LIBRARY_PATH, do not know if it will be enough) and a lot of testing. I will try to work on it next week. Stephan, could you open an issue for that on GH?