Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Instructions do not work #150

Open
mschwart opened this issue Oct 16, 2018 · 4 comments
Open

Instructions do not work #150

mschwart opened this issue Oct 16, 2018 · 4 comments

Comments

@mschwart
Copy link

When following the instructions from the README.md I end up with the following error:

$ build/kati/m2n --kati_stats --goma
using /run/user/314079/goma_schwartzmi as tmpdir
Auto update is skipped because latest/MANIFEST was updated recently.
Using goma VERSION=163 (latest)
GOMA version fdabf1b6311be985cf5e8c8483fafab271828dff@1537516851

goma is already running.

*kati*: Stack size: 8376320 bytes
[1/1] initializing build system ...
build/make/core/config.mk:53: *** unknown variable: OUT_DIR

Instrumenting a normal build and passing the variables results in more errors.

Also notable is that both methods provided in README are marked as deprecated.

What is the right way to invoke this tool?
@danw
Copy link
Collaborator

danw commented Oct 16, 2018

That's the deprecated instructions (for Android M or earlier). Newer versions use kati automatically (either from source build/kati for Android-N or as a prebuilt in prebuilts/build-tools/linux-x86/bin/ckati for later versions)

danw added a commit that referenced this issue Oct 16, 2018
@danw
Update README.md
0d8f27c 
Make it clear that Android-N and later use ckati and ninja automatically.

Also remove the reference to goma in the deprecated instructions, since those branches are old enough that they're unlikely to work with goma anymore.

Fixes #150
@danw danw mentioned this issue Oct 16, 2018
Merged
@mschwart
Copy link
Author

Can we also get instructions on how to use gdb when building Android? That was the intent behind trying to directly invoke anyway... I see that now soong is making the invocation so it looks like it might not be trivial.

@danw
Copy link
Collaborator

danw commented Oct 16, 2018

Yeah, that's not necessarily easy, depending on how true you want to keep the environment. It's generally a lot easier to debug a smaller example build if you can create one.

To debug kati within soong_ui, it's probably best to create an option that pauses execution with SIGSTOP, or spins (etc) waiting for gdb to connect.

@danw danw closed this as completed in #151 Oct 17, 2018
@danw
Copy link
Collaborator

danw commented Oct 17, 2018

Reopening to handle the gdb request

@danw danw reopened this Oct 17, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@danw @mschwart