I'm not sure what you are asking. They -are- turned off by default for the
C code, as the comment says. If force them to be turned on... well then
you are forcing them to be turned on, and if you don't want that, then don't
do it. :}
For Java code, NO code should ever be calling Log.v() without an if()
wrapper around it that is turned off by default. For example, you will
typically see:
final static String TAG = "MyClass";
final static boolean localLOGV = false;
...
if (localLOGV) Log.v(TAG, "...");
On Thu, Apr 16, 2009 at 1:01 AM, 袁嵩 Yuan Song <[email protected]> wrote:
>
> In system/core/include/cutils/log.h, it is mentioned in the comments
> as follows:
>
> /*
> * Normally we strip LOGV (VERBOSE messages) from release builds.
> * You can modify this (for example with "#define LOG_NDEBUG 0"
> * at the top of your source file) to change that behavior.
> */
>
> So I tried to put "#define LOG_NDEBUG 0" in frameworks/base/libs/ui/
> EventHub.cpp and re-compile. I do get verbose messages when I do "adb
> logcat EventHub:v".
>
> Now the question is whether there is a way to sort of turn verbose
> messages on during compilation globally, both for "LOGV()" in the C
> file and "Log.v()" in the Java file.
>
> Appreciation for any of your thoughts.
>
> /Song
> >
>
--
Dianne Hackborn
Android framework engineer
[email protected]
Note: please don't send private questions to me, as I don't have time to
provide private support, and so won't reply to such e-mails. All such
questions should be posted on public forums, where I and others can see and
answer them.
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"android-framework" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to
[email protected]
For more options, visit this group at
http://groups.google.com/group/android-framework?hl=en
-~----------~----~----~----~------~----~------~--~---
