Hi,
I just stumbled upon here for I had similar problem that I was
trying to figure out how to turn on Config.DEBUG, and I am very glad
to share with people had same need: add TARGET_BUILD_TYPE=debug
after your make -j4 when you build the entire android source code.
Plus I had the same
if you could share with me a template of the ant script, it will be
much appreciated!!
On Apr 5, 3:51 pm, Bob Kerns r...@acm.org wrote:
You should ALWAYS look outside the IDE for production builds. Any IDE.
Builds should always be automateable and as automated as possible.
Including managing
why do you think i am not being serious?!
On Apr 4, 9:28 pm, ~ TreKing treking...@gmail.com wrote:
On Sun, Apr 4, 2010 at 9:38 PM, HeHe cnm...@gmail.com wrote:
my apk stills gets a *false* Config.DEBUG value.
Are you being serious? Which part of Xavier's post did you not understand?
So
i set debuggable flag in manifest.xml.
i launched my apk using Run Debug As menu cmd of Eclipse IDE.
could you or Xavier please elaborate what extra procedure (detailed
steps, please) i need to follow to get a true Config.DEBUG value?
thanks a lot!
On Apr 4, 9:28 pm, ~ TreKing
TreKing -- He doesn't understand what a debug build is. The flag
indicates that the DEVICE, not your APPLICATION is a debug build.
HeHe -- That's why you can't get at it with Config.DEBUG -- you'd need
to reflash your device. You don't make this in Eclipse -- or at least
not using the SDK.
What
On Mon, Apr 5, 2010 at 2:00 AM, HeHe cnm...@gmail.com wrote:
why do you think i am not being serious?!
Because you insist on asking the exact same question after an answer was
posted (and then re-posted) about 3 times now.
I thought Xavier's first post about the Config.DEBUG variable
Bob, thanks for reply. i am still still very very confusedthe link
you gave me is a constant FLAG_DEBUGGABLE, indicating the
application is manifested to be debuggable. but what i need is some
info telling my apk that it was a debug or release built without
changing the debuggable attribute in
thanks. now i understand it. Config.DEBUG is for DEVICE and not for
APK.
i need some info to tell my apk which of map api key to use. here are
the 2 cases:
(1). build apk by selecting Eclipse Run Run As or Run Debug As
menu option. in this case, the apk is a DEBUG built and is signed by
Android
On Mon, Apr 5, 2010 at 10:42 AM, HeHe cnm...@gmail.com wrote:
but what i need is some info telling my apk that it was a debug or release
built without changing the debuggable attribute in manifest each time
between debug/release builds.
This is not possible. You will have to make sure to
thanks for the good idea to turn debuggable apk to red. however, the
problem i am experiencing that even after i set debuggable attribute
in manifest to TRUE and build and launch my apk using Eclipse Run
Debug As, my apk still sees Config.DEBUG as FALSE. so right now i
don't know how my apk can
Your application is ALWAYS going to see Config.DEBUG as FALSE. You
seem stuck on that. Config.DEBUG has nothing to do with your
application whatsoever. It has to do with your device.
I need to get breakfast, I'm getting grumpy. In addition to the link I
sent you, look at this link (which is
Bob, sounds like you are going to devise some Makefile to achieve
the purpose and i also have to look outside of Eclipse IDE and my code
to find my machine gun. please forget my problem and have a nice
breakfast :) thanks anyway for your comments.
On Apr 5, 9:49 am, Bob Kerns r...@acm.org wrote:
actually i had the same issue with different Map keys for dev and
production.
My solution was a little bit of code that checks to see if your
running in the emulator or not. It works for at least Android 2.1
update 1:
public static final boolean isEmulator() {
if
Brill, thanks for comment. using your approach, do you run a DEBUG
build on a real device and still succeed in map api?
my apk has no problem telling itself if it is running on emulator or
not, because running on emulator an apk should always assume itself a
debug build. my release build has no
On Mon, Apr 5, 2010 at 12:39 PM, Brill Pappin br...@pappin.ca wrote:
My solution was a little bit of code that checks to see if your running in
the emulator or not.
Running in the emulator IS NOT the same as running in debug. You can run a
release APK on the emulator (and you should be for
thanks and have a nice lunch :)
On Apr 5, 11:55 am, ~ TreKing treking...@gmail.com wrote:
On Mon, Apr 5, 2010 at 12:39 PM, Brill Pappin br...@pappin.ca wrote:
My solution was a little bit of code that checks to see if your running in
the emulator or not.
Running in the emulator IS NOT the
You should ALWAYS look outside the IDE for production builds. Any IDE.
Builds should always be automateable and as automated as possible.
Including managing revision control stategy. IDEs are simply not
designed for repeatability.
However, the main part of the process is vanilla ant script
DEBUG mode doesn't factor into it and gmaps doesn't care.
AFAIK if you are simply trying to change the map key so it works on
the emulator or the device, then this is a reasonable way to do it.
So, to reiterate, it *does not* matter if you are running in debug
mode or not. The emulator uses the
On Mon, Apr 5, 2010 at 11:31 AM, HeHe cnm...@gmail.com wrote:
OR, i should not run a debug build on a real device and hope map api
works...
You seem to think that there is a difference between a debug build and
a release build, when there isn't.
The code itself is always the same, whether you
If you are talking about
http://d.android.com/reference/android/util/Config.html#DEBUG
then it's based on whether the device build is a debug build. It has
nothing to do with your app.
BTW, if Config.DEBUG is true, (for example in the emulator), then
putting debuggable=true in your manifest is
yes, i was talking about Config.DEBUG constant.
how can i make a debug build in Eclipse IDE?
right now, no matter if i use RunRun As or RunDebug As menu
commands, i always see Config.DEBUG == false.
i am using Eclipse v3.4.1 and Android SDK 1.6.
thanks in advance for further answer!!
On Apr
On Sun, Apr 4, 2010 at 6:20 PM, HeHe cnm...@gmail.com wrote:
how can i make a debug build in Eclipse IDE?
Use the debuggable flag in your manifest.
right now, no matter if i use RunRun As or RunDebug As menu
commands, i always see Config.DEBUG == false.
Didn't Xavier just answer this
it does not work. here is the setting in my manifest.xml:
application
android:name=com.xxx.yyy
android:label=@string/app_name
android:icon=@drawable/icon_zzz
android:debuggable=true
my apk stills gets a *false* Config.DEBUG value.
On Apr 4, 6:40 pm,
On Sun, Apr 4, 2010 at 9:38 PM, HeHe cnm...@gmail.com wrote:
my apk stills gets a *false* Config.DEBUG value.
Are you being serious? Which part of Xavier's post did you not understand?
So once again:
On Sun, Apr 4, 2010 at 3:35 PM, Xavier Ducrohet x...@android.com wrote:
If you are talking
thanks.
i did, otherwise ADT build tool would complain it.
do you get a true Config.DEBUG value with your apk?
On Apr 3, 7:53 pm, JP joachim.pfeif...@gmail.com wrote:
On Apr 3, 4:30 pm, HeHe cnm...@gmail.com wrote: yes, the flag is set to
true.
In the right location? In the manifest, it
yes, the flag is set to true.
but Config.DEBUG seems always false no matter what.
On Apr 3, 12:13 pm, ~ TreKing treking...@gmail.com wrote:
On Fri, Apr 2, 2010 at 6:55 PM, HeHe cnm...@gmail.com wrote:
does anyone know how to DEBUG build an APK and launch it directly
with Eclipse?
Is the
On Apr 3, 4:30 pm, HeHe cnm...@gmail.com wrote:
yes, the flag is set to true.
In the right location? In the manifest, it must be placed like this:
application
android:debuggable=true
--
You received this message because you are subscribed to the Google
Groups Android Developers group.
27 matches
Mail list logo
