fancypants' experiments
214 subscribers
124 photos
4 videos
37 links
stuff
Download Telegram
dexpreopt_bootjars has now moved to the soong build system
All modules to be added as bootjars need to migrate to Android.bp rules
They also need to be marked as installable
installable: true,

Else they aren't picked up for bootjar dexpreopt at all
Also, much like last time, snooping around base, SystemUI and Settings, doesn't look like Google pushed any major visual changes on the preview tag.
Kshitij Gupta
Photo
You can add
BUILD_BROKEN_DUP_RULES := true
to work around this for the time being.
But yeah, if you have this, I guess it's time to fix your build rules.
Similarly,
BUILD_BROKEN_PHONY_TARGETS := true
Particularly useful if you're trying to use the current kernel.mk rules. Again, this should be fixed up properly and this is a mere workaround.
Google was nice enough to "warn" us this way, I guess ๐Ÿ˜†
Oh I should probably add in a few older findings here too
Channel photo updated
Most are probably aware, but yeah. Might as well add it here.
add_lunch_combo is deprecated and lunch relies on a build var:
Set COMMON_LUNCH_CHOICES in your AndroidProducts.mk, instead.
Also, AOSP now has fuchsia targets ๐Ÿ˜†
Thank you Google, very cool.
Checking the PATH variable from make, there seems to be only
/home/agentfabulous/q-preview/prebuilts/build-tools/path/linux-x86:/home/agentfabulous/q-preview/out/.path by default.
/home/agentfabulous/q-preview/out/.path has symlinks to ../.path_interposer
I don't know what I was expecting, but yes the only differnce now is that the system PATH variable is no more considered at all. We need to add paths to prebuilt binaries in our kernel.mk or we can look into path_interposer's inclusions.
So, path_interposer will back up the current PATH data to a file in outdir. This is restored when soong is exiting. If you manage to kill soong during the build (or even hit Ctrl+c a bunch of times when it starts exiting from the initial interrupt), you'll be left with the PATH set for the build.
inline kernel compilation now works :)
Though I guess we could do something nicer, this should do the job for now.
You may also be wondering as to why I'm using the prebuilt make while I'm running instructions against the original path. This is because path.go will throw an error if I try to build specifying any path tools such as make.
Oh also, I should mention, the soong kernel header generator also calls make. Fixed it up now, just need to clean-up and add my path override.