**** BEGIN LOGGING AT Tue Nov 28 03:00:02 2017 Nov 28 06:43:25 Herrie: mainly you compare the libhardware/hardware headers with the ones from libhybris Nov 28 06:44:43 Morning! Nov 28 06:45:02 Tofe: I'm getting an error... Not sure what I'm doing wrong... Nov 28 06:45:17 build/core/product_config.mk:249: *** Can not locate config makefile for product "aosp_mido". Stop. Nov 28 06:45:25 I guess I need to add it somewhere Nov 28 06:45:59 For Halium 5.1 there's main.mk where you add vendor trees as you did for TP: https://github.com/Halium/android_build/commit/3ad7ffafeded18c81adb13d498a2fad04f0440bf Nov 28 06:46:07 Just this doesn't seem to exist for 7.1 ? Nov 28 06:46:58 for TP I added a lunch target in the cm.mk file (which I added too iirc) Nov 28 06:47:20 aosp and CM/Lineage differ slightly in how they add lunch targets Nov 28 06:47:39 but usually it's all in the root of the device tree Nov 28 06:47:47 Where's yours? Nov 28 06:48:11 Tofe: No clue :P Nov 28 06:48:23 I mean the repo Nov 28 06:48:28 for device tree Nov 28 06:48:44 https://github.com/piggz/android_device_xiaomi_mido/tree/pgz-14.1 Nov 28 06:49:01 (also you're right, if device/xiaomi isn't in main.mk, you'll need to add it yourself) Nov 28 06:53:12 I *think* you might be alright with lineage_mido-userdebug Nov 28 07:02:16 Tofe: Seems so Nov 28 07:02:18 Now get further Nov 28 07:02:40 device/xiaomi/mido/BoardConfig.mk:208: device/qcom/sepolicy/sepolicy.mk: No such file or directory Nov 28 07:37:29 Tofe: I guess I need to add something for that to the .xml will have a look Nov 28 07:38:27 We have a sepolicy but at different path it seems Nov 28 07:38:27 Could be a specific one for qcom is needed will try some things Nov 28 08:35:14 Tofe: Do we need selinux in general or I can just comment it out? Nov 28 08:35:26 Or would it be nice to have for future? Nov 28 08:44:11 Herrie|Laptop: we usually disable selinux, for simplicity's sake Nov 28 08:44:18 Tofe: OK Nov 28 08:44:34 I commented it out from my BoardConfig.mk for now Nov 28 08:44:47 for qcom, you can have a look at the prerequisites of the device tree, it says soemthing about qcom-common Nov 28 08:53:26 Tofe: It's my first time building Android bits from scratch so might need some more guidance :P Nov 28 08:53:29 Where I need to look? Nov 28 08:59:26 Tofe: With commented out selinux: https://bpaste.net/show/585f541d9d7a Nov 28 09:00:46 Ah that seems a result of me disabling sepolicy :P Nov 28 09:07:11 Herrie|Laptop: let me see Nov 28 09:08:08 Herrie|Laptop: just to be sure, which commands are you using to build ? mka systemimage ? Nov 28 09:08:21 Tofe: I just made a .sh with the code from our Jenkins job ;) Nov 28 09:08:25 ok, perfect Nov 28 09:09:07 For the prerequisites, I was looking at this: https://github.com/piggz/android_device_xiaomi_mido/blob/pgz-14.1/lineage.dependencies Nov 28 09:09:47 so you'll need to add android_device_qcom_common if it isn't there already Nov 28 09:11:02 and hopefully you'll be able to keep the BoardConfig.mk untouched Nov 28 09:11:23 disabling selinux is mainly done in the kernel anyway Nov 28 09:12:08 (let's just hope it isn't a hard dependency of Android 7...) Nov 28 09:12:23 Tofe: It's not there it seems Nov 28 09:12:32 It== ? Nov 28 09:12:37 There's Nov 28 09:12:38 ah, the qcom repo Nov 28 09:13:02 'We'd need to add https://github.com/LineageOS/android_device_qcom_sepolicy Nov 28 09:13:14 Herrie|Laptop: yep, help youself :) Nov 28 09:13:15 Would this work? Nov 28 09:13:30 We're using msm8953 on mido Nov 28 09:13:37 mmh let me see Nov 28 09:14:21 no, remove '/msm8953", the repo contains all of them Nov 28 09:14:45 Ah ok Nov 28 09:15:29 usually android_xxx_yyy_zzz corresponds simply to path xxx/yyy/zzz Nov 28 09:16:32 Tofe: OK Nov 28 11:21:56 Tofe: Getting further bit by bit... Got the selinux and signapk error sorted Nov 28 11:21:59 Now another one Nov 28 11:22:51 https://bpaste.net/show/4b803eb562b3 Nov 28 11:23:09 I guess this might be defconfig related, but not sure Nov 28 11:30:25 Tofe: Seems I might need 2 add another 2 qcom repos as per Moto Lux: http://codegists.com/code/halium%20build%20motorola/ Nov 28 11:39:29 Nope that doesn't sort it it seems Nov 28 11:50:02 Herrie|Laptop: you also have the vendor repo, right? Nov 28 11:50:14 like TheMuppets, or maybe a dedicated one Nov 28 11:51:33 But overall, you could ask the SFOS guy what manifest he used Nov 28 11:59:38 Tofe: Yeah TheMuppets as per https://github.com/webOS-ports/android/blob/herrie/wop-halium-7.1/wop_targets.xml#L20 Nov 28 12:04:47 Tofe: I don't see any manifest being used, but I do see he uses a custom https://github.com/piggz/android_system_core Nov 28 12:06:12 Herrie|Laptop: are things like https://github.com/piggz/android_system_core/commit/5d1c31eb79e9ac09ed8a4c6cecdeefa6f0c12a08 already in Halium 7.1 ? Nov 28 12:10:26 Tofe: Some is for sure: https://github.com/Halium/android_system_core/commit/98c007af50f93c797f4cdac04cd5b5eba59decfc Nov 28 12:10:34 Might need to ping bshah instead :P Nov 28 12:10:36 bshah: ^ Nov 28 13:46:10 Herrie|Laptop: he *might* be doing some serious sleep-catchup :) Nov 28 13:46:40 but it looks like the selinux stuff is also ripped off halium Nov 28 14:03:36 Tofe: Yes looks like it Nov 28 14:03:48 This one still seems to be related to selinux somehoiw Nov 28 14:03:59 I copied the apksign stuff as per example I found Nov 28 14:04:37 cp ${BUILD_DIR}/prebuilts/sdk/tools/lib/signapk.jar ${BUILD_DIR}/out/host/linux-x86/framework/ Nov 28 14:06:06 That helped me to progress a bit but got stuck at this error Nov 28 14:07:21 this build is pretty weird, I must say Nov 28 14:07:36 but maybe it's always the case :) Nov 28 14:13:42 Tofe: Not sure really Nov 28 14:21:03 My first time playing with Halium/Android build like this Nov 28 16:15:03 Tofe: https://github.com/sandymanu/device_hammerhead/issues/1 seems to suggest I'd might need to place my kernel already? Nov 28 16:44:22 Tofe: OK seems my error "disappeared" by simply doing a mkdir -p by the looks of it Nov 28 16:47:18 Next error LOL: ninja: error: 'external/ant-wireless/antradio-library/com.dsi.ant.antradio_library.xml', needed by '/home/herrie/halium-wop-12.1/out/target/product/mido/system/etc/permissions/com.dsi.ant.antradio_library.xml', missing and no known rule to make it Nov 28 16:48:28 Tofe: Seems for that one we might need: https://github.com/CyanogenMod/android_external_ant-wireless_antradio-library Nov 28 16:48:33 Or the lineageOS equiv Nov 28 16:52:36 Tofe: Seems that's related to FM radio Nov 28 16:53:45 Another try ;) Nov 28 16:53:47 Getting there slowly Nov 28 16:55:59 Tofe: OK this gets better: ninja: error: '/home/herrie/halium-wop-12.1/out/target/product/mido/kernel', needed by '/home/herrie/halium-wop-12.1/out/target/product/mido/boot.img', missing and no known rule to make it Nov 28 16:56:09 That's already close to where we'd want to be I gues Nov 28 16:56:12 +s Nov 28 18:00:52 Herrie: you're making progress I see :) Nov 28 18:02:49 ok, for the kernel it looks like it's a bit badly designed; maybe you should start the kernel build separately ? Nov 28 18:03:06 I'm surprised Halium people got it building Nov 28 18:03:24 Herrie: where is your kernel's repo ? Nov 28 18:08:43 something like "mka out/target/product/mido/kernel/arch/arm/boot/zImage-dtb" or similar Nov 28 18:21:45 Tofe: Well I need to check defconfig Nov 28 18:21:50 The port that exists is SFOS Nov 28 18:21:56 Not Halium specific Nov 28 18:22:04 So Need to run the script to check defconfig Nov 28 18:22:12 COuld be I need to change things still Nov 28 18:22:35 Tofe: https://github.com/piggz/android_kernel_xiaomi_msm8953 Nov 28 18:22:37 That's the repo Nov 28 18:26:13 Herrie: for the moment, just take the defconfig from piggz as-is Nov 28 18:26:26 Tofe: OK Nov 28 18:26:35 Well I guess it does that in the build for Halium? Nov 28 18:26:38 I would assume it does? Nov 28 18:26:43 (and it's probably very near what you'd want to have anyway) Nov 28 18:26:46 I have a building kernel in general from Yocto Nov 28 18:27:14 Not tested but building Nov 28 18:27:34 yes, it should take the "default" defconfig during Halium's build Nov 28 18:27:58 I'm just surprised it doesn't build the dependencies automatically for the kernel Nov 28 18:30:43 Tofe: Anything quick I can check? Nov 28 18:31:08 Tofe: Xiaomi is Chinese, I'm not surprised about badly designed :P Nov 28 18:31:45 I think you'll have to trigger the kernel build manually Nov 28 18:32:07 I'm reading https://source.android.com/setup/building-kernels, but I'm not sure how much it applies here Nov 28 19:03:41 Tofe: Am not sure either Nov 28 19:37:29 Herrie, do you have any builds that are waiting? Nov 28 19:39:46 ka6sox: Not atm Nov 28 19:42:31 Herrie, thanks Nov 28 21:06:34 Tofe: They suggested I do mka bootimage to get a boot.img Nov 28 21:07:01 However now I get errors about "ninja: error: 'device/generic/goldfish/fstab.goldfish', needed by '/home/herrie/halium-wop-12.1/out/target/product/generic/root/fstab.goldfish', missing and no known rule to make it" Nov 28 21:07:14 fstab.goldfish is reference stuff I think Nov 28 21:07:15 ? Nov 28 21:07:19 We shouldn't need that? Nov 28 21:07:25 https://github.com/lineageos/android_device_generic_goldfish Nov 28 21:07:37 I could add it to the .xml but not sure that should be needed really? thoughts? Nov 28 21:08:29 Seems it should be mka mkbootimg I guess as per https://github.com/Halium/docs/blob/0b6530095574c458b5ef8ec338b1bcd9e1ef1eaa/porting/build-sources.rst Nov 28 21:34:41 Nope that's also not it :S Nov 28 21:36:18 Ah I should do breakfast instead of lunch for 7.1 ;) Nov 28 21:37:20 RTFM LOL ;) Nov 28 21:49:33 Sorry was away Nov 28 21:49:46 Ok, seems you sorted it out :p Nov 28 21:49:52 Tofe: Not yet Nov 28 21:52:47 Tofe: My source build/envsetup.sh doesn't list the including the device/manufacturer entry as per docs Nov 28 21:52:55 The Halium docs list including device/lge/bullhead/vendorsetup.sh Nov 28 21:53:00 I only have the 4 basic ones :S Nov 28 21:53:33 Herrie: you may be missing a vendorsetup.sh yes Nov 28 21:53:47 Tofe: How do I get it there :P ? Nov 28 21:53:57 Or it's not a problem? Nov 28 21:54:00 don't panic, it's basically something like "add_lunch_item lineage-mido" Nov 28 21:54:11 let's have a closer look Nov 28 21:55:23 Tofe: Not panicing ;) Nov 28 21:56:08 https://github.com/Tofee/android_device_hp_tenderloin/commit/87bd658662b1b84a347de219f8b973971347e6d1 here's what I added for TP (which wasn't even a CM build, but AOSP) Nov 28 21:56:43 so what I would say is simply add a vendorsetup.sh in the mido device tree Nov 28 21:57:27 Tofe: Ehm I think I might have another idea Nov 28 21:57:54 with "add_lunch_combo lineage_mido-userdebug" Nov 28 21:58:53 you should be able to simply do "brunch lineage_mido-userdebug" directly I think Nov 28 21:59:22 (or breakfast) Nov 28 22:04:06 OK it does something :P https://bpaste.net/show/6fd870687359 Nov 28 22:04:25 I guess it doesn't pull in our wop_targets.xml properly somehow? Nov 28 22:04:30 Or doesn't parse it Nov 28 22:05:12 At least that's the feeling I get Nov 28 22:05:22 I could try adding them to the default.xml directly? Nov 28 22:06:46 no Nov 28 22:07:03 the manifests are only used by repo Nov 28 22:07:29 Tofe: OK :S Nov 28 22:07:37 Well i can see it pulls them in Nov 28 22:08:53 Does http://wiki.lineageos.org/w/Doc:_integrated_kernel_building give any info ? Nov 28 22:09:22 404 :P Nov 28 22:10:05 CM copy at: http://blog.csdn.net/qqbaby2005/article/details/7907137 Nov 28 22:11:18 ah, ok, that's just for downloading it, ok Nov 28 22:11:49 It seems that you need to add 2 values to BoardCOnfig.mk but those are there already Nov 28 22:11:49 what do you have at vendor/cm/build/tasks/kernel.mk:159 ? Nov 28 22:12:23 Ah wait Nov 28 22:12:44 because, well, you do have the source Nov 28 22:12:45 I have kernel/xiaomi/mido while it expects: https://github.com/piggz/android_device_xiaomi_mido/blob/pgz-14.1/BoardConfig.mk#L47 Nov 28 22:12:53 That might explain :P Nov 28 22:13:13 yup; and look at the kernel repo name, that fits Nov 28 22:13:48 So I should just update my wop_targets.xml with correct name? Nov 28 22:14:27 I would suggest to both update the xml file and do a rename of the folder yourself before doing repo sync Nov 28 22:14:39 otherwise it'll just redownload the whole thing Nov 28 22:17:33 OK Nov 28 22:17:39 Like this I could search forever LOL Nov 28 22:17:45 Should be better now I guess Nov 28 22:18:03 yup Nov 28 22:18:11 Learning along the way ;) Nov 28 22:18:48 yes... but I find that Android builds are often messy Nov 28 22:19:15 Yup LOL Nov 28 22:21:08 Ok takes longer now Nov 28 22:21:17 SO I guess it's actually cooking me some food :P Nov 28 22:21:42 Ah, did you also remove the wallpapers ? Nov 28 22:21:52 otherwise mka systemimage will probably fail Nov 28 22:22:07 Tofe: Not yet Nov 28 22:22:13 ok Nov 28 22:23:05 It's just building the Makefiles, right ? no building of code ? Nov 28 22:23:31 otherwise it should probably have been breakfast, not brunch Nov 28 22:23:56 Tofe: Just the Jenkins job basically Nov 28 22:26:47 ok Nov 28 22:27:10 going to bed now, I'll see the result tomorrow :) Nov 28 22:27:16 gn8 ! Nov 28 22:37:25 dn8 Nov 28 22:37:27 gn8 Nov 28 22:37:29 Same here **** ENDING LOGGING AT Wed Nov 29 03:00:02 2017