ubuntu-phone team mailing list archive

[Ricardo Salveti de Araujo <ricardo.salveti@xxxxxxxxxxxxx>]

On Wed, Jul 17, 2013 at 1:41 AM, David Hacker <davidhackerdvm@xxxxxxxxx> wrote:
> Are there any plans to have the actual ubuntu-boot.img in the flashable zip
> for ports instead of the android boot.img? Seems it would make more sense

Yeah, I'm currently busy working on getting the 'phablet-saucy' branch
in phablet.ubuntu.com updated, which should bring the ubuntu boot
image by default (which some other more intrusive changes that will be
flipped compatible only).

And also making a rebase on top of CM 10.1.2, to be easier for porters
to know what is supported by us.

Hopefully the new porting guide for flipped images should be in place
later this week. We also have a goal of making it easier for us to
support more community builds, and even try to get them installed
automatically via phablet-flash (for the ones with enough quality).

More to come over the next few days.

Cheers,

Ricardo

> On Jul 16, 2013 11:38 PM, "Ricardo Salveti de Araujo"
> <ricardo.salveti@xxxxxxxxxxxxx> wrote:
>>
>> On Sun, Jul 14, 2013 at 9:17 PM, scott <meandmine63@xxxxxxxxx> wrote:
>> > -----BEGIN PGP SIGNED MESSAGE-----
>> > Hash: SHA1
>> >
>> > I just started back to work on porting the Fascinate. Did a repo sync
>> > with phablet-dev-bootstrap which pulled in a bunch of new files. I
>> > double checked all the recommended patches and they are still there.
>> > Except, now it will not compile. I get:
>> >   "make: *** No rule to make target
>> > `/out/target/product/fascinatemtd/ubuntu-boot.img', needed by
>> >
>> > `/out/target/product/fascinatemtd/obj/PACKAGING/target_files_intermediates/cm_fascinatemtd-target_files-eng.scott.zip'.
>> >  Stop."
>> >
>> > I've looked around a little and can't seem to find exactly what's
>> > causing it. Any ideas?
>>
>> That's a regression because your device is a 'mtd' kind, and probably
>> uses a custom mkimage tool to create the boot image.
>>
>> See if your device config file
>> (device/<manufacturer>/<device>/BoardConfig.mk) defines
>> BOARD_CUSTOM_BOOTIMG_MK, if so that might be the reason.
>>
>> Taking from the epicmtd device:
>> $ grep -R BOARD_CUSTOM_BOOTIMG_MK
>> BoardConfig.mk:BOARD_CUSTOM_BOOTIMG_MK :=
>> device/samsung/epicmtd/shbootimg.mk
>>
>> $ cat shbootimg.mk
>> LOCAL_PATH := $(call my-dir)
>>
>> INSTALLED_BOOTIMAGE_TARGET := $(PRODUCT_OUT)/boot.img
>> $(INSTALLED_BOOTIMAGE_TARGET): $(TARGET_PREBUILT_KERNEL)
>> $(recovery_ramdisk) $(INSTALLED_RAMDISK_TARGET)
>> $(PRODUCT_OUT)/utilities/erase_image $(PRODUCT_OUT)/utilities/busybox
>> $(PRODUCT_OUT)/utilities/make_ext4fs
>>     $(call pretty,"Boot image: $@")
>>     $(hide) ./device/samsung/epicmtd/mkshbootimg.py $@
>> $(TARGET_PREBUILT_KERNEL) $(INSTALLED_RAMDISK_TARGET)
>> $(recovery_ramdisk)
>>
>> $(INSTALLED_RECOVERYIMAGE_TARGET): $(INSTALLED_BOOTIMAGE_TARGET)
>>     $(ACP) $(INSTALLED_BOOTIMAGE_TARGET) $@
>>
>> So you either make INSTALLED_BOOTIMAGE_TARGET_UBUNTU as a dependency
>> in there, or simply remove the need for it to be built, like
>> http://paste.ubuntu.com/5883021/ (under <root>/build).
>>
>> I'll try to get a better fix tomorrow.
>>
>> Cheers,
>> --
>> Ricardo Salveti de Araujo
>>
>> --
>> Mailing list: https://launchpad.net/~ubuntu-phone
>> Post to     : ubuntu-phone@xxxxxxxxxxxxxxxxxxx
>> Unsubscribe : https://launchpad.net/~ubuntu-phone
>> More help   : https://help.launchpad.net/ListHelp



--
Ricardo Salveti de Araujo