search

exokitxr / exokit-frontend

Frontend for exokit. Turns exokit into a spatial web browser. 🦎
7 stars 3 forks source link

Export to executable/package #9

Open chrislatorres opened 5 years ago

chrislatorres commented 5 years ago

from: https://github.com/exokitxr/exokit/pull/1002#issuecomment-489343732

We will want package export functionality implemented from the menut; something like

Export > Android APK...

And we probably want that for all platforms.

In general we want to avoid a full build in this export process, so the easiest path is to download the latest built asset (or the one most closely matching the currently running release), and repack that binary into a new package with the user's desired app assets.

For APK's and MPK's, the path is clear: these files are just .zip files which are signed, so we can repack them with the app assets under /app and re-pack and re-sign with the SDK signing tools.

However, for desktop, which uses installers, we probably will need a way to extract the installer/DMG to get at the files (or have a separate release that contains the files in a usable form that is not an installer, like a .zip). We can then ship Exokit with just the needed scripts to do the packaging phase of the install (either the InnoDB install maker, or the MacOS DMG maker). And then the desktop cases reduces to the mobile one, where we are just repacking assets.

The main purpose of doing it this way is to not have any build dependencies on the user side for doing the export.

In either case we will need a way to input the user's certificate to do the signing procedure.

chrislatorres commented 5 years ago

Marking this issue as a bug since the "SDK Paths..." settings in Studio currently just re-uses the "Settings..." menu.