Building Hammerhead

vandys

I'm trying to follow the recipe for building a Nexus 5 Hammerhead image. I'm all the way up to envsetup.sh, which does not pull in lge_hammerhead options. In fact, the lge_hammerhead part of the tree is on cm12.1, but the vendorsetup.sh file apparently needed by envsetup.sh does not exist until the cm13 branch.

Here's what device/lge/hammerhead has:

ubports$ pwd
/home/vandys/phablet/device/lge/hammerhead

ubports$ git branch -a

cm-12.1
cm-13.0
remotes/cm/cm-11.0
remotes/cm/cm-12.0
remotes/cm/cm-12.1
remotes/cm/cm-13.0
remotes/cm/cm-13.0-prereset
remotes/cm/cm-14.1
remotes/cm/stable/cm-11.0
remotes/cm/stable/cm-11.0-XNG3C
remotes/cm/stable/cm-12.0-YNG3C
remotes/cm/stable/cm-12.0-YNG4N
remotes/cm/stable/cm-12.1-YOG4P
remotes/cm/stable/cm-12.1-YOG7D
remotes/cm/stable/cm-13.0-ZNH0E
remotes/cm/stable/cm-13.0-ZNH2K
remotes/cm/stable/cm-13.0-ZNH5Y
remotes/cm/staging/cm-12.0-caf
remotes/cm/staging/cm-12.1
remotes/cm/staging/cm-14.0
remotes/m/ubp-5.1 -> cm/cm-12.1

(I actually think it was on no branch until I started playing.)

And:

ubports$ git remote -v
cm http://github.com/CyanogenMod/android_device_lge_hammerhead (fetch)
cm http://github.com/CyanogenMod/android_device_lge_hammerhead (push)

What'd I do wrong? Thanks in advance!

doniks

what does lunch offer you?

vandys

@doniks said in Building Hammerhead:

what does lunch offer you?

Oh, yes, this is what made me start looking:
ubports$ . ./build/envsetup.sh
including vendor/cm/vendorsetup.sh
including sdk/bash_completion/adb.bash
including vendor/cm/bash_completion/git.bash
including vendor/cm/bash_completion/repo.bash

and then
ubports$ lunch

You're building on Linux

Lunch menu... pick a combo:

aosp_arm-eng 3. aosp_mips-eng 5. aosp_x86-eng
aosp_arm64-eng 4. aosp_mips64-eng 6. aosp_x86_64-eng

I'm pretty sure I'm not seeing the Hammerhead support honored....

vandys

If somebody with access to the official build tree could go into device/lge/hammerhead and tell me what "git branch" and "git remote -v" tell you? I suspect I haven't grabbed the right bits, but not sure what I did wrong.

Thanks!

doniks

@vandys said in Building Hammerhead:

@doniks said in Building Hammerhead:

what does lunch offer you?

Oh, yes, this is what made me start looking:
ubports$ . ./build/envsetup.sh
including vendor/cm/vendorsetup.sh
including sdk/bash_completion/adb.bash
including vendor/cm/bash_completion/git.bash
including vendor/cm/bash_completion/repo.bash

and then
ubports$ lunch

You're building on Linux

Lunch menu... pick a combo:

aosp_arm-eng 3. aosp_mips-eng 5. aosp_x86-eng

aosp_arm64-eng 4. aosp_mips64-eng 6. aosp_x86_64-eng

I'm pretty sure I'm not seeing the Hammerhead support honored....

What I did over here

https://forums.ubports.com/topic/271/building-for-nexus-7-deb

For my N7 build was essentially guessing the right add_lunch_combo command and that did allow me to proceed. If you read my thread you see my hypothesis about how the cyanogenmod to lineage transition might be breaking the paths right now but with that little command it did work anyway even though I don't fully understand why or how, but it was good enough for me

Hth

vandys

Thanks for that pointer, applying it to my Hammerhead tree did permit a build. What would have been my "hands on" Nexus 5 is busy with some highly interesting notification experiments, but I'll see if my built images boot RSN.