|
|
@@ -158,7 +158,6 @@ the command line:
|
|
|
- Set `ANDROID_KEYSTORE_PASS` to the keystore password. This can be used in multiple ways,
|
|
|
described in [Creating a Keystore](#creating-a-keystore) below.
|
|
|
- Optional: Set `ANDROID_MANIFEST` to use a custom Android manifest XML file.
|
|
|
-- Optional: Set `ANDROID_PACKAGE` to change the package name from `org.lovr.app`.
|
|
|
- Optional: Set `ANDROID_ASSETS` to include extra assets (e.g. a project folder) in the APK.
|
|
|
- Windows: Make sure you add `-G "Unix Makefiles"` so it doesn't try to use Visual Studio.
|
|
|
|
|
|
@@ -205,6 +204,12 @@ Although LÖVR provides a default `AndroidManifest.xml`, you can also use your o
|
|
|
path as the `ANDROID_MANIFEST` option to CMake. This can be used to request extra permissions,
|
|
|
change the package ID or app name, etc.
|
|
|
|
|
|
+### Changing the Package ID
|
|
|
+
|
|
|
+LÖVR extracts the package name from the `AndroidManifest.xml` file (`org.lovr.app` by default). To
|
|
|
+use a different package id, edit `etc/AndroidManifest.xml`, or set the `ANDROID_MANIFEST` CMake
|
|
|
+variable to set a custom manifest with a different package id.
|
|
|
+
|
|
|
### Creating a Keystore
|
|
|
|
|
|
APKs must be signed to work properly. First, generate a keystore file using Java's `keytool` tool:
|
bjorn