On Fri, Aug 08, 2014 at 10:29:59PM +0200, Felix Winkelmann wrote:
If it's occasionally useful in general, we can put it behind a
DEBUGBUILD check. Alternatively, the Ant (or whatever) infrastructure
could toggle this via a XML config option or so.
DEBUGBUILD sounds good.
How about the
From: Peter Bex peter@xs4all.nl
Subject: Re: [Chicken-hackers] [PATCH] Don't enable debugging on Android by
default
Date: Sun, 5 Oct 2014 20:43:16 +0200
On Fri, Aug 08, 2014 at 10:29:59PM +0200, Felix Winkelmann wrote:
If it's occasionally useful in general, we can put it behind
On Mon, Aug 04, 2014 at 07:01:03PM +0200, Felix Winkelmann wrote:
From: Moritz Heidkamp moritz.heidk...@bevuta.com
Subject: [Chicken-hackers] [PATCH] Don't enable debugging on Android by
default
Date: Mon, 04 Aug 2014 18:30:44 +0200
This was probably accidentally left in when generating
Has it been useful in practice for debugging your app? Note that I'm not
interested in whether it was useful in getting CHICKEN initially running
on Android (obviously that required some fiddling, and CHICKEN hackers
may be expected to tweak the code a bit to debug stuff), but specifically
This was probably accidentally left in when generating the Android
patch.
--
bevuta IT GmbH - professionelle IT-Lösungen
Marktstraße 10 | http://www.bevuta.com/ | HRB 62476 AG Köln
50968 Köln | Tel.: +49 221 282678-0 | Geschäftsführer: Pablo Beyen
From 8d21fae15e69c65d0b3d1e721de557588f0a4dfa
From: Moritz Heidkamp moritz.heidk...@bevuta.com
Subject: [Chicken-hackers] [PATCH] Don't enable debugging on Android by default
Date: Mon, 04 Aug 2014 18:30:44 +0200
This was probably accidentally left in when generating the Android
patch.
That's mostly correct - I thought it might be handy
