I am hoping, but not sure, that using an Electron portable build for GDevelop will either directly make GDevelop portable or render the environment variable technique effective. I think the problem is that Electron bypasses the settings of the relevant Windows environment variables.
I also tried to make GDevelop portable, but failed. (Sorry, new users can only put 2 links in a post.) Here are the posts I made for the two applications I mentioned: But it is possible to redirect the files to the application or other directory using Windows environment variables. These applications normally use the Windows AppData folder for storage. I can't pack a Microsoft.NET executable outright since reflection doesn't work when the executable is packed using Enigma Virtual Box and had to create a native launcher. It supports Microsoft.NET v3.0, v3.5, and v9. I have made portable a number of applications, such as digiKam and KMyMoney. It uses Enigma Virtual Box for file and registry virtualization. Perhaps this should be added to the above line: -win portable I am guessing that line 65 in Gdevelop-master\.circleci\config.yml is relevant to Windows portability:Ĭommand: export NODE_OPTIONS="–max-old-space-size=7168" & cd newIDE/electron-app & npm run build – -mac zip -win -linux tar.gz -publish=never I confess that I have not built an Electron application and am out of my depth. The Enigma forum shows that creating portable apps with Enigma is a challenge for many users.
Windows version - use zipped binaries instead of setup.exe #469ĭistribute GDevelop 5 in zipped binaries on Windows in addition to executable I could then submit it for possible inclusion in The Portable Freeware Collection.
ENIGMA VIRTUAL BOX MAC ARCHIVE
The asset would be in an archive format (probably ZIP) and portable.
I suggest that an additional Windows asset be added for users to download.
0 kommentar(er)
