I am using the current AOSP build instructions, and using either “make -jX” or “make bootimage -jX” does not work. I am familiar with building android from doing it with my phones, but every time I try to make the boot image, the command just sayings nothing to do. Any help would be appreciated.
I was able to take the latest boot.img from the online archives for the db410c, unpack it, and replace the ramdisk and kernel, as well as update The kernel command line arguments and have confirmed the resulting packed boot.img works with the latest master aosp source, but I have to manually create this, as I cannot create a boot image using the make command
I’m afraid I don’t know what is going in here but assuming that “from the online archives” means http://snapshots.linaro.org/96boards/dragonboard410c/linaro/aosp-master/latest/ then I can, at least, help you see how these assets are built (which makes it easier for you to play spot the difference).
You could try experimenting with http://snapshots.linaro.org/96boards/dragonboard410c/linaro/aosp-master/latest/linaro_android_build_cmds.sh . That is a shell script that, at least in principle, will build exactly the same code as it found in the releases. If you can get that to run (and then simplify it a bit) it is a great way to see what is different for you.
The other thing you can find in linaro_android_build_cmds.sh (although only if you know to look for it) is a link back to the original CI job which allows you see exactly how we build the snapshots, complete with build logs:
https://ci.linaro.org/job/96boards-dragonboard410c-aosp-master/201/
Yes, that is correct, I am referring to the latest boot.img from http://snapshots.linaro.org/96boards/dragonboard410c/linaro/aosp-master/latest/
The problem that I am having is when in the root Android directory, and doing either the make or make bootimage commands, my out directory does not include a generated boot.img based on the prebuilt kernel. So when building Android off the Master AOSP sources at the moment, no boot.img is generated, and I had to manually generate it based off unpacking and repacking an older one with the gz-dtb prebuilt file and generated ramdisk in my out directory.
