46
edits
(Added link to App Structure page) |
|||
| Line 41: | Line 41: | ||
This follows the normal mach based process, and then starts a gradle based build which takes the (mach build) gecko libraries as an input. | This follows the normal mach based process, and then starts a gradle based build which takes the (mach build) gecko libraries as an input. | ||
In future we want to be able to avoid using mach for the android part of the process. These builds are experimental, and can be run by adding the following to your mozconfig: | In future we want to be able to avoid using mach for the android part of the process. These builds are '''experimental''', and can be run by adding the following to your mozconfig: | ||
ac_add_options --with-gradle | ac_add_options --with-gradle | ||
You can now run |mach build|, followed by |mach package|, which will produce apk's in the same location as a mach build. | You can now run |mach build|, followed by |mach package|, which will produce apk's in the same location as a mach build. | ||
'''TODO:''' add explanation of what actually happens in practice? | |||
Note that these builds do not interact with the usual gradle builds, see the following email for more information: | Note that these builds do not interact with the usual gradle builds, see the following email for more information: | ||
edits