Re: [android-building] Building the AOSP sources for the Galaxy Nexus (maguro)

[bcbuc...@gmail.com]

Try make otapackage ?

On Fri, Jul 6, 2012 at 11:44 AM, Shiba <aki...@gmail.com> wrote:
> All,
>
> I'm attempting to generate an OTA-compatible update ZIP, targeting the
> Galaxy Nexus. After extracting the vendor's proprietary binaries, here is
> what I've done:
>
> export PATH="${HOME}/Downloads/jdk1.6.0_33/bin:${PATH}"
> repo init -u https://android.googlesource.com/platform/manifest -b
> android-4.0.4_r2.1
> repo sync
> . build/envsetup.sh
> lunch full_maguro-userdebug
> make -j8 dist
>
> After checking the build tool versions, it displays a warning: "No private
> recovery resources for TARGET_DEVICE maguro". However, the build continues
> and appears to successfully generate the desired zip archives. I then try
> to generate an OTA update package using sign_target_files_apks, but it fails
> with the following error: "can't find recovery API version in input
> target-files". Looking through core/Makefile, it appears that these two
> events are related; the following line is observed:
>
> echo "$(PRIVATE_RECOVERY_API_VERSION)" >
> $(zip_root)/META/recovery-api-version.txt.
>
> It appears that sign_target_files_apks requires this file,
> recovery-api-version.txt, but it is not being generated by "make dist".
> I've tried looking through a mirror of the PDK, which was taken offline by
> Google, here, but it looks like it is outdated:
>
> http://www.kandroid.org/online-pdk/guide/release_keys.html
>
> I would sincerely appreciate it if someone could enlighten me as to how this
> process is done properly, or point me to whatever updated documentation
> replaces the PDK.
>
> TIA,
>
> Mike
>
> --
> 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

[Chandra Gopalaiah]

Hi Mike,

Sometime back I faced the same issue.

But I did make-clean and again issue make command to generate a build.

make-clean cleared my out directory.

Hopefully this will help you.

Thanks,

Chandra

On Sat, Jul 7, 2012 at 9:47 PM, Shiba <aki...@gmail.com> wrote:

That doesn't seem to help; running that in a tree with a completed build yields this:

$ make otapackage
============================================
PLATFORM_VERSION_CODENAME=REL
PLATFORM_VERSION=4.0.4
TARGET_PRODUCT=full_maguro
TARGET_BUILD_VARIANT=userdebug
TARGET_BUILD_TYPE=release
TARGET_BUILD_APPS=
TARGET_ARCH=arm
TARGET_ARCH_VARIANT=armv7-a-neon
HOST_ARCH=x86
HOST_OS=linux
HOST_BUILD_TYPE=release
BUILD_ID=IMM76L
============================================

No private recovery resources for TARGET_DEVICE maguro

make: Nothing to be done for `otapackage'.

I see that same exact output for another 'make dist' in this directory.  Where exactly do device vendors get documentation to do this type of work?

Thanks,
Mike

On Friday, July 6, 2012 12:19:23 PM UTC-7, Ben Buchacher wrote:

Try make otapackage ?

[Magnus Bäck]

On Sunday, July 08, 2012 at 00:47 EDT,

Shiba <aki...@gmail.com> wrote:

> That doesn't seem to help; running that in a tree with a completed
> build yields this:
>
> $ make otapackage
> ============================================
> PLATFORM_VERSION_CODENAME=REL
> PLATFORM_VERSION=4.0.4
> TARGET_PRODUCT=full_maguro
> TARGET_BUILD_VARIANT=userdebug
> TARGET_BUILD_TYPE=release
> TARGET_BUILD_APPS=
> TARGET_ARCH=arm
> TARGET_ARCH_VARIANT=armv7-a-neon
> HOST_ARCH=x86
> HOST_OS=linux
> HOST_BUILD_TYPE=release
> BUILD_ID=IMM76L
> ============================================

> No private recovery resources for TARGET_DEVICE maguro

> make: Nothing to be done for `otapackage'.
>
> I see that same exact output for another 'make dist' in this directory.

This indicates that all necessary files already are available.
Going back to your original question, is your problem that
recovery-api-version.txt is missing from the resulting zip archive?
AFAICT, recovery-api-version.txt was removed in Gingerbread, and the
makefile line you quoted in your first message in the thread doesn't
exist in IMM76L.

> Where exactly do device vendors get documentation to do this type of
> work?

Not all vendors use this method of generating OTA packages, but those
who do will presumably read the makefiles and the rest of the source
code. I'm not aware of any documentation of these pieces.

--
Magnus Bäck
ba...@google.com

[Magnus Bäck]

On Monday, July 09, 2012 at 16:20 EDT,
Shiba <aki...@gmail.com> wrote:

> On Monday, July 9, 2012 9:27:47 AM UTC-7, Magnus Bäck wrote:
>
> > Not all vendors use this method of generating OTA packages, but
> > those who do will presumably read the makefiles and the rest of the
> > source code. I'm not aware of any documentation of these pieces.
>

> That might be a solution if you have a staff of 50-100 full-time,
> dedicated software engineers working on a product. I am a single
> programmer working on this project alone at the moment, in my spare
> time. It isn't feasible for me to read through 50,000+ Makefiles in
> this situation. I was hoping that something like the PDK was now
> available with updated information. I do appreciate your feedback and
> time.

Let's not paint things black here. Figuring out how the OTA packages are
generated probably doesn't require you to read more than a handful of
makefiles and a few scripts.

Now, judging by the findings in my last message, it seems you're having
other issues since you're asking about lines in a makefile that don't
actually exist in the source code you're building. It looks like you
have a mismatch somewhere.

--
Magnus Bäck
ba...@google.com