Currently, Constructor uses a path directly to where runtimes are located. This, in theory, made sense in the case your runtimes were to be found somewhere random on your system...but that doesn't really make sense in GMEdit's usecase - Igor alone may be located anywhere for a CI release, but in using GMEdit a runtime should always be expected to be located in the user's GM User Folder generated by the IDE; of which is required anyway to create a project in the first place.
Getting the user folder means access to the IDE's runtime listing rather than trying to parse them from a folder manually, it also means getting access to Devices.json, which is a critical missing piece for getting remote SSH compiles working, iOS and Android support.
The license.plist file here is also what the older LTS Igor branch (see #5) needs to compile projects.
Currently, Constructor uses a path directly to where runtimes are located. This, in theory, made sense in the case your runtimes were to be found somewhere random on your system...but that doesn't really make sense in GMEdit's usecase - Igor alone may be located anywhere for a CI release, but in using GMEdit a runtime should always be expected to be located in the user's GM User Folder generated by the IDE; of which is required anyway to create a project in the first place.
Getting the user folder means access to the IDE's runtime listing rather than trying to parse them from a folder manually, it also means getting access to
Devices.json, which is a critical missing piece for getting remote SSH compiles working, iOS and Android support.The
license.plistfile here is also what the older LTS Igor branch (see #5) needs to compile projects.