public inbox for kawa@sourceware.org
 help / color / mirror / Atom feed
From: "F. Rafael Leon" <teflon@ucdavis.edu>
To: kawa@sourceware.org
Subject: Re: Pluvia 3D real-time Android weather app released, written in Kawa Scheme.
Date: Thu, 03 Mar 2016 04:37:00 -0000	[thread overview]
Message-ID: <CALPCXwi2ioZxN4dxPeO0z+d_nAEtKcJPB1zfZ1+f-c0=uxPuKw@mail.gmail.com> (raw)
In-Reply-To: <56D74D20.4070604@bothner.com>

On Wed, Mar 2, 2016 at 3:29 PM, Per Bothner <per@bothner.com> wrote:
> Perhaps you might consider writing an article about your experience,
> for some website you're familiar with?

I most definitely will once I resolve my build system issues.

The app code itself is respectable and clean. The "live coding"
development experience within emacs using a telnet REPL is also
smooth.   I can write many happy interesting words on these topics.

However, for final production compiling and publishing to Google Play,
I used a spaghetti-code build system of Makefiles and gradle files
which set variables and tasks for the Android gradle plugin.

The build system is not in a good state and needs work.  Because of
the situation, ProGuard, resources/R.java, Google Play Services,
appcompat and NDK support are suffering or unstable.

Notably, if I had been using straight Java instead of Kawa, my
problems would have been far more serious because I would have
struggled with the build system daily instead of for a few hours at
the end of a project.

I am looking forward to a "build system epiphany" to complement the
other epiphanies that I have had using Kawa.

Specifically, the final solution will likely involve these two web pages:

https://en.wikipedia.org/wiki/Directed_acyclic_graph

http://geosoft.no/development/android.html

    -Rafael

      reply	other threads:[~2016-03-03  4:37 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-03-02 14:46 F. Rafael Leon
2016-03-02 20:29 ` Per Bothner
2016-03-03  4:37   ` F. Rafael Leon [this message]

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='CALPCXwi2ioZxN4dxPeO0z+d_nAEtKcJPB1zfZ1+f-c0=uxPuKw@mail.gmail.com' \
    --to=teflon@ucdavis.edu \
    --cc=kawa@sourceware.org \
    /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).