Too much of log in AOSP Build

[Ashish Kumar]

Hi,

I am a newbie to AOSP, and trying to build Android from source on my Mac. I am facing couple of problems in building, debugging and running emulator. So, thought of going through build log, but build has generated more than 22K of lines, and it's really hard to read all that and pin-point the exact problem for a newbie. Is there any way to reduce number of lines in build log? Something like setting log level to error or fetal, so that logs of higher priority get logged, while logs of lower priority can be ignored.

Thanks.
Ashish

[Conley Owens]

Is your build completing? If it isn't, you should try doing:
"make -j<num> -k" where <num> is the number of threads you want make to run
"make" The build log should be small and contain your error.

If you aren't sure what failed, you can run "make showcommands" to see
what exactly the build system was trying to do.

~cco3

> --
> You received this message because you are subscribed to the "Android
> Building" mailing list.
> To post to this group, send email to android-...@googlegroups.com
> To unsubscribe from this group, send email to
> android-buildi...@googlegroups.com
> For more options, visit this group at
> http://groups.google.com/group/android-building?hl=en

[Jean-Baptiste Queru]

Are you trying to run an emulator that was built on MacOs 10.7 and/or
XCode 4? Those are known to fail to work, even when the build is
perfectly successful.

JBQ

On Mon, Mar 5, 2012 at 4:09 PM, Ashish Kumar <aky.i...@gmail.com> wrote:

> --
> You received this message because you are subscribed to the "Android
> Building" mailing list.
> To post to this group, send email to android-...@googlegroups.com
> To unsubscribe from this group, send email to
> android-buildi...@googlegroups.com
> For more options, visit this group at
> http://groups.google.com/group/android-building?hl=en

--
Jean-Baptiste M. "JBQ" Queru
Software Engineer, Android Open-Source Project, Google.

Questions sent directly to me that have no reason for being private
will likely get ignored or forwarded to a public forum with no further
warning.

[John Kirk]

Use search in your text editor. All errors actually report using the word error. If you use make with no j switch the log will be more orderly. I run make that way on the first few builds.

[Ashish Kumar]

Thanks Conley. This helped.

On Monday, March 5, 2012 4:33:11 PM UTC-8, Conley Owens wrote:

Is your build completing?  If it isn't, you should try doing:
"make -j<num> -k" where <num> is the number of threads you want make to run
"make" The build log should be small and contain your error.

If you aren't sure what failed, you can run "make showcommands" to see
what exactly the build system was trying to do.

~cco3

On Mon, Mar 5, 2012 at 4:09 PM, Ashish Kumar <aky.i...@gmail.com> wrote:
> Hi,
>
> I am a newbie to AOSP, and trying to build Android from source on my Mac. I
> am facing couple of problems in building, debugging and running emulator.
> So, thought of going through build log, but build has generated more than
> 22K of lines, and it's really hard to read all that and pin-point the exact
> problem for a newbie. Is there any way to reduce number of lines in build
> log? Something like setting log level to error or fetal, so that logs of
> higher priority get logged, while logs of lower priority can be ignored.
>
> Thanks.
> Ashish
>
> --
> You received this message because you are subscribed to the "Android
> Building" mailing list.

> To post to this group, send email to android-building@googlegroups.com

> To unsubscribe from this group, send email to

> android-building+unsubscribe@googlegroups.com