Hello.
Will you be able to push the kernel source for Android Wear 9.0
catfish/catshark? Thank in advance.
--
--
You received this message because you are subscribed to the "Android Building"
mailing list.
To post to this group, send email to android-building@googlegroups.com
To unsubscribe
Got it.
Thanks for your quick response.
在 2019年3月18日星期一 UTC+8下午10:28:34，Po Hu写道：
>
> When I try to add a target binary called badblocks (defined
> https://android.googlesource.com/platform/external/e2fsprogs/+/refs/heads/master/misc/Android.bp#157)
>
> into image.
> "PRODUCT_PACKAGES +=
thanks, I've tried *compiledb-aosp.sh* in android-9.0.0_r34, but failed.
here is the out put
alex@alex-pc:~/code-reviww/aosp$ ./aosp-compdb.sh
# Loading build env
# Configuring x86_64 build
# Chosen module: bionic/libc
# Generating compilation database file
some module like frameworks/av is really hard to convert to Android.bp. In
android-9.0.0_r34 , SOONG_GEN_COMPDB can't use directly, I need add related
file to aosp soong module, then recompile soong, then I can
SOONG_GEN_COMPDB, but the generated compile_commands is really big, like
83M.
The basics on Android.bp files are documented at
https://android.googlesource.com/platform/build/soong/+/master/README.md,
and the documentation on the module types and their properties is at
https://ci.android.com/builds/latest/branches/aosp-build-tools/targets/linux/view/soong_build.html
.
On
I actually have everything in vendor and I'd prefer to keep it there. I'm
not sure how to include whats in vendor in framework.jar.
This is the structure of the stuff I have in vendor that I would like to
include.
vendor/xxx/lib -> the prebuilt jars are here
vendor/xxx/src/com/aaa/bbb/ccc => the
All of that is up to you. All Android.bp files found in the tree are
parsed, so you can create a directory anywhere (maybe under vendor/ so you
can minimize changes to AOSP files). Put the prebuilt jars in that
directory too.
static_libs takes a list of module names.
An alternative option would be compiledb tool (
https://github.com/nickdiego/compiledb), which is able to parse compile
commands from a build log. Some years ago I've been able to parse
compilation database from some AOSP modules using a similar approach.
On Mon, Mar 18, 2019, 13:18 'Dan
What directory should my prebuilt jars go into? Where are the pother
static_libs, like android.hardware.radio-V1.0-java, picked up from?
Where do I add this new Android.bp with the below content?
All I want to add to framework.jar are 2 prebuilt jars and 2 source files.
Do I need to create a
You need to use java_import modules to create a module for the jars.
Something like:
java_import {
name: "my_prebuilt_jars",
jars: [
"my_prebuilt_jar1.jar",
"my_prebuilt_jar2.jar",
],
}
Then you can add to static_libs:
"my_prebuilt_jars"
On Mon, Mar 18, 2019
The error message looks like a runtime denial (possibly due to a SELinux
denial), instead of a change to the package itself. But I can't tell if
it's a known issue based on that line alone. The logs prior to the
exception could be helpful, in particular something with "avc: denied" plus
the
Hi
I would like to add a couple of prebuilt jars and some source files to the
Android 9 aosp image that I"m building.
With lower versions of Android I've added these easily to frameworks.jar.
This was straight forward to do when framework.jar was built using a make
file. Its a lot less clear
The "android-q-preview-1" tag refers to the sources published as part of
this post:
GPL projects for Android Q Beta 1
https://groups.google.com/forum/#!topic/android-building/alh5sZHhEtU
Please note that it is not a complete release, and only includes GPL
projects.
On Monday, March 18,
Google pushed a tag to AOSP named "android-q-preview-1" a few days ago but
it is unclear what exactly makes it "Q" since the API level didn't change
and it appears to be missing new APIs like
Activity#onTopResumedActivityChanged()
Would be nice if someone could explain what exactly the
While re-playing with official emulator - and taking a look at Android 10
by the way ;) I noticed that the ramdisk.img of the emulator does't contain
/sepolicy file, and it looks like Emulator still succeeds to get it booting
: so the missing files that makes QEMU-KVM to fail is not really
The behavior up until a few weeks ago was to build everything in
PRODUCT_PACKAGES for both host and device. I'm in the process of splitting
them up, but right now that means that you need to add them to both
PRODUCT_PACKAGES and PRODUCT_HOST_PACKAGES. I hope to fully disconnect them
this week, so
The ninja compilation database support doesn't work very well for our ninja
files due to kati using a rule per command. This upstream ninja feature
request may help, but that's assuming that whatever is parsing the compdb
files can understand the raw rules (which is usually a bash script, not
just
Hi everybody,
I'm on this subject for some times now, and I'm stuck. I'll first really
simply describe what I did, and "how" it doesn't work.
*Building the most "generic" or "mainline" Android as possible
(android-9.0.0_r34 / aosp_x86_64-eng) :*
- PATH=~/bin:$PATH
- repo init -u
Check your build.config file in kernel. So it has what needed config
directories and files.
LZ4_PREBUILTS_BIN=prebuilts-master/misc/linux-x86/lz4
DTC_PREBUILTS_BIN=prebuilts-master/misc/linux-x86/dtc
LIBUFDT_PREBUILTS_BIN=prebuilts-master/misc/linux-x86/libufdt
Download this lz4(Compression
When I try to add a target binary called badblocks (defined
https://android.googlesource.com/platform/external/e2fsprogs/+/refs/heads/master/misc/Android.bp#157)
into image.
"PRODUCT_PACKAGES += badblocks" will show this error:
build/make/core/main.mk:1182: warning: Missing modules from
Hi,
That is not the right procedure to build Wahoo kernels: as the
documentation says, that is an example for HiKey development boards.
Please have a look at our recently updated Building Kernels documentation,
which shows a much simpler out-of-the-box procedure to build custom
kernels:
21 matches
Mail list logo
