public inbox for kawa@sourceware.org
 help / color / mirror / Atom feed
From: "F. Rafael Leon" <teflon@ucdavis.edu>
To: Per Bothner <per@bothner.com>
Cc: kawa@sourceware.org
Subject: Re: first Android app - Didn't find class
Date: Sun, 17 Apr 2016 06:42:00 -0000	[thread overview]
Message-ID: <CALPCXwif+ADUoKoBtAXG0Avzm++TBzsAZhnLfHqxTMjac8o7KA@mail.gmail.com> (raw)
In-Reply-To: <57131D2E.1040705@bothner.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

  reply	other threads:[~2016-04-17  6:42 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-04-17  1:48 Claude Marinier
2016-04-17  4:23 ` F. Rafael Leon
2016-04-17  5:17   ` Per Bothner
2016-04-17  5:21   ` Per Bothner
2016-04-17  6:42     ` F. Rafael Leon [this message]
2016-04-24 16:10       ` Adrián Medraño Calvo
     [not found]   ` <CAPg6usC95-BBUniSY_hHFJvGm160kLwi7eYNybFj08Uhm9pgFw@mail.gmail.com>
2016-04-17 20:11     ` Fwd: " Claude Marinier
     [not found]       ` <CALPCXwjLYwFBx2zpS6B-xmqYAFps3yGtrUKG=_eUzmt3chfSZg@mail.gmail.com>
2016-04-17 23:50         ` Claude Marinier
2016-04-18  0:05       ` Fwd: " Per Bothner

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=CALPCXwif+ADUoKoBtAXG0Avzm++TBzsAZhnLfHqxTMjac8o7KA@mail.gmail.com \
    --to=teflon@ucdavis.edu \
    --cc=kawa@sourceware.org \
    --cc=per@bothner.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).