This is the mail archive of the
kawa@sourceware.org
mailing list for the Kawa project.
Re: first Android app - Didn't find class
- From: "F. Rafael Leon" <teflon at ucdavis dot edu>
- To: Per Bothner <per at bothner dot com>
- Cc: kawa at sourceware dot org
- Date: Sun, 17 Apr 2016 02:41:46 -0400
- Subject: Re: first Android app - Didn't find class
- Authentication-results: sourceware.org; auth=none
- References: <CAPg6usCBguqE3oB8LBuZgPZ9G43n7sTbRf8YBn5wO7sY-T=JgA at mail dot gmail dot com> <CALPCXwjiLJHDv7hrh_H1VuJi3fdBMYKaUS+nFSME7xGenhOciw at mail dot gmail dot com> <57131D2E dot 1040705 at bothner dot com>
On Sun, Apr 17, 2016 at 1:20 AM, Per Bothner <per@bothner.com> wrote:
> Would it make sense to update the Kawa/Android instructions to use Gradle
> rather than Ant?
The answer is yes. Gradle is the accepted standard.
For introducing current Android developers to Kawa, gradle would be
the path of least friction.
The minimal "kawaBuild" task from this gradle file should still work:
https://github.com/rafleon/KawaDroid/blob/master/app/build.gradle
preDexDebug doesn't exist in gradle anymore, so the new dependency is:
project.afterEvaluate{
compileDebugSources.dependsOn kawaBuild
compileReleaseSources.dependsOn kawaBuild
}
That should do it. I haven't pushed updates to github in awhile.
Gradle has some faults (slow, complicated, bloated, etc), but it is
indeed the current Android standard.
They are legitimately working on improving it, so it should be fine eventually.
For example, this new feature is an enormous step in the right direction:
http://tools.android.com/tech-docs/instant-run
Instant Run pushes fresh compiled classes into the context of a
running mobile app.
It is not immediately obvious what the relationship could be between
Instant Run and a Kawa REPL,
but interesting tricks should be possible once the official build
tools are stable.
-Rafael