[android-building] Re: Android Wear 9.0 released
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 from this group, send email to android-building+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-building?hl=en --- You received this message because you are subscribed to the Google Groups "Android Building" group. To unsubscribe from this group and stop receiving emails from it, send an email to android-building+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[android-building] Re: Question about PRODUCT_HOST_PACKAGES and PRODUCT_PACKAGES
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 += badblocks" will show this error: > build/make/core/main.mk:1182: warning: Missing modules from > PRODUCT_HOST_PACKAGES > build/make/core/main.mk:1183: warning: See > https://android.googlesource.com/platform/build/+/master/Changes.md#PRODUCT_HOST_PACKAGES > > for more information > build/make/core/main.mk:1184: warning: _ badblocks > build/make/core/main.mk:1185: error: stop. > > Because badblocks happens to be a "host_supported" binary too. > How to make only the target one installed ? > I don't want to use "PRODUCT_HOST_PACKAGES += badblocks" to generate extra > host binary. > > -- -- 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 from this group, send email to android-building+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-building?hl=en --- You received this message because you are subscribed to the Google Groups "Android Building" group. To unsubscribe from this group and stop receiving emails from it, send an email to android-building+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [android-building] how to get compile_commands.json by mma or mm from android.mk in aosp project of android 9
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 /home/alex/code-reviww/aosp/bionic/libc/compile_commands.json alex@alex-pc:~/code-reviww/aosp$ ls /home/alex/code-reviww/aosp/bionic/libc/compile_commands.json ls: cannot access '/home/alex/code-reviww/aosp/bionic/libc/compile_commands.json': No such file or directory Nick Diego Yamane 于2019年3月19日周二 上午4:34写道： > 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 Willemsen' via Android Building < > android-building@googlegroups.com> wrote: > >> 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 a call to the compiler): >> https://github.com/ninja-build/ninja/issues/1377 >> >> I'd recommend converting to Android.bp so that you can use >> SOONG_GEN_COMPDB. >> >> - Dan >> >> On Mon, Mar 18, 2019 at 9:54 AM wrote: >> >>> I can get CMakeLists.txt from Android.bp by soong, then get >>> compile_commands, but cann't get CMakeLists.json from android.mk. I've >>> tried pass ' -t compdb cxx' but just get empty "[ \n ]" , any one can help >>> me? >>> >>> -- >>> -- >>> 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 from this group, send email to >>> android-building+unsubscr...@googlegroups.com >>> For more options, visit this group at >>> http://groups.google.com/group/android-building?hl=en >>> >>> --- >>> You received this message because you are subscribed to the Google >>> Groups "Android Building" group. >>> To unsubscribe from this group and stop receiving emails from it, send >>> an email to android-building+unsubscr...@googlegroups.com. >>> For more options, visit https://groups.google.com/d/optout. >>> >> -- >> -- >> 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 from this group, send email to >> android-building+unsubscr...@googlegroups.com >> For more options, visit this group at >> http://groups.google.com/group/android-building?hl=en >> >> --- >> You received this message because you are subscribed to the Google Groups >> "Android Building" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to android-building+unsubscr...@googlegroups.com. >> For more options, visit https://groups.google.com/d/optout. >> > -- > -- > 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 from this group, send email to > android-building+unsubscr...@googlegroups.com > For more options, visit this group at > http://groups.google.com/group/android-building?hl=en > > --- > You received this message because you are subscribed to the Google Groups > "Android Building" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to android-building+unsubscr...@googlegroups.com. > For more options, visit https://groups.google.com/d/optout. > -- -- 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 from this group, send email to android-building+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-building?hl=en --- You received this message because you are subscribed to the Google Groups "Android Building" group. To unsubscribe from this group and stop receiving emails from it, send an email to android-building+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [android-building] how to get compile_commands.json by mma or mm from android.mk in aosp project of android 9
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. generated by CMakeLists.txt is much smaller. :) 'Dan Willemsen' via Android Building 于2019年3月19日周二 上午1:18写道： > 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 a call to the compiler): > https://github.com/ninja-build/ninja/issues/1377 > > I'd recommend converting to Android.bp so that you can use > SOONG_GEN_COMPDB. > > - Dan > > On Mon, Mar 18, 2019 at 9:54 AM wrote: > >> I can get CMakeLists.txt from Android.bp by soong, then get >> compile_commands, but cann't get CMakeLists.json from android.mk. I've >> tried pass ' -t compdb cxx' but just get empty "[ \n ]" , any one can help >> me? >> >> -- >> -- >> 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 from this group, send email to >> android-building+unsubscr...@googlegroups.com >> For more options, visit this group at >> http://groups.google.com/group/android-building?hl=en >> >> --- >> You received this message because you are subscribed to the Google Groups >> "Android Building" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to android-building+unsubscr...@googlegroups.com. >> For more options, visit https://groups.google.com/d/optout. >> > -- > -- > 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 from this group, send email to > android-building+unsubscr...@googlegroups.com > For more options, visit this group at > http://groups.google.com/group/android-building?hl=en > > --- > You received this message because you are subscribed to the Google Groups > "Android Building" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to android-building+unsubscr...@googlegroups.com. > For more options, visit https://groups.google.com/d/optout. > -- -- 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 from this group, send email to android-building+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-building?hl=en --- You received this message because you are subscribed to the Google Groups "Android Building" group. To unsubscribe from this group and stop receiving emails from it, send an email to android-building+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [android-building] Add prebuilt jar to system image - android 9.0
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 Mon, Mar 18, 2019 at 2:52 PM KarenL wrote:
> 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 source files are here
>
> Question: Should I add an Android.bp to vendor/xxx/
> It sounds like that should contain the java_import section you already
> mentioned.
> How do I include the source files in the new Android.bp?
>
> Question: How do I reference this not module from Android.bk in
> frameworks/base/Android.bp?
>
> Is there any documentation on how to set up Android.bp files. I've been
> looking around and I cant find anything.
>
> I need the extra classes because I'm adding a new system service to the
> build that I'm making.
>
> Thank you again for your help.
>
>
>
> On Monday, March 18, 2019 at 2:33:13 PM UTC-7, Colin Cross wrote:
>>
>> 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.
>> android.hardware.radio-V1.0-java is a module created
>> by hardware/interfaces/radio/1.0/Android.bp. The modules can be defined
>> anywhere in the tree.
>>
>> Taking a step back, what are you trying to accomplish? Why do you need
>> extra classes in framework.jar? Maybe it would be better to keep them
>> outside framework.jar but add them to the default classpath using
>> PRODUCT_BOOT_JARS? Or ship them as a separate shared library that apps can
>> opt into loading?
>>
>> On Mon, Mar 18, 2019 at 1:34 PM KarenL wrote:
>>
>>> 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 new folder structure under frameworks/base for
>>> these? If so - what does that structure look like.
>>>
>>> Thank you for your help.
>>>
>>>
>>>
>>> On Monday, March 18, 2019 at 1:06:45 PM UTC-7, Colin Cross wrote:
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 at 12:35 PM KarenL wrote:
> 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 how to do this using
> blueprint files and soong.
>
> This is what I've tried and its not enough.
>
> Add a new folder to frameworks/base for my source files:
> frameworks/base/myfolder/java/com/xxx
>
> Edit the Android.bp file in frameworks/base and add source files to
> the "srcs" list
> "myfolder/java/com/xxx/source1.java"
> "myfolder/java/com/xxx/source2.java"
>
> Edit the "static_libs" list and add my prebuilt jars
> "prebuilt_jar1",
> "prebuilt_jar2",
>
> I'm not sure where to put these prebuilt jars.
> Do they go somewhere inside myfolder? Where are the other static libs
> in this list picked up from?
> Do I need to create .bp files inside myfolder to build this new part?
>
> Do you have any suggestions as to how to add prebuilt jars to Android
> 9.
>
> Thanks for your help.
> Karen
>
> --
> --
> You received this message because you are subscribed to the "Android
> Building" mailing list.
> To post to this group, send email to android-...@googlegroups.com
> To unsubscribe from this group, send email to
> android-buildi...@googlegroups.com
> For more options, visit this group at
> http://groups.google.com/group/android-building?hl=en
>
> ---
> You received this message because you are subscribed to the Google
> Groups "Android Building" group.
> To unsubscribe from this group and stop receiving emails from it, send
> an email to android-buildi...@googlegroups.com.
> For more options, visit
Re: [android-building] Add prebuilt jar to system image - android 9.0
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 source files are here
Question: Should I add an Android.bp to vendor/xxx/
It sounds like that should contain the java_import section you already
mentioned.
How do I include the source files in the new Android.bp?
Question: How do I reference this not module from Android.bk in
frameworks/base/Android.bp?
Is there any documentation on how to set up Android.bp files. I've been
looking around and I cant find anything.
I need the extra classes because I'm adding a new system service to the
build that I'm making.
Thank you again for your help.
On Monday, March 18, 2019 at 2:33:13 PM UTC-7, Colin Cross wrote:
>
> 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.
> android.hardware.radio-V1.0-java is a module created
> by hardware/interfaces/radio/1.0/Android.bp. The modules can be defined
> anywhere in the tree.
>
> Taking a step back, what are you trying to accomplish? Why do you need
> extra classes in framework.jar? Maybe it would be better to keep them
> outside framework.jar but add them to the default classpath using
> PRODUCT_BOOT_JARS? Or ship them as a separate shared library that apps can
> opt into loading?
>
> On Mon, Mar 18, 2019 at 1:34 PM KarenL >
> wrote:
>
>> 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 new folder structure under frameworks/base for
>> these? If so - what does that structure look like.
>>
>> Thank you for your help.
>>
>>
>>
>> On Monday, March 18, 2019 at 1:06:45 PM UTC-7, Colin Cross wrote:
>>>
>>> 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 at 12:35 PM KarenL wrote:
>>>
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 how to do this using
blueprint files and soong.
This is what I've tried and its not enough.
Add a new folder to frameworks/base for my source files:
frameworks/base/myfolder/java/com/xxx
Edit the Android.bp file in frameworks/base and add source files to the
"srcs" list
"myfolder/java/com/xxx/source1.java"
"myfolder/java/com/xxx/source2.java"
Edit the "static_libs" list and add my prebuilt jars
"prebuilt_jar1",
"prebuilt_jar2",
I'm not sure where to put these prebuilt jars.
Do they go somewhere inside myfolder? Where are the other static libs
in this list picked up from?
Do I need to create .bp files inside myfolder to build this new part?
Do you have any suggestions as to how to add prebuilt jars to Android 9.
Thanks for your help.
Karen
--
--
You received this message because you are subscribed to the "Android
Building" mailing list.
To post to this group, send email to android-...@googlegroups.com
To unsubscribe from this group, send email to
android-buildi...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/android-building?hl=en
---
You received this message because you are subscribed to the Google
Groups "Android Building" group.
To unsubscribe from this group and stop receiving emails from it, send
an email to android-buildi...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
>>> --
>> --
>> You received this message because you are subscribed to the "Android
>> Building" mailing list.
>> To post to this group, send email to android-...@googlegroups.com
>>
>> To unsubscribe from this group, send email to
>> android-buildi...@googlegroups.com
>> For more options, visit this group at
>> http://groups.google.com/group/android-building?hl=en
>>
>> ---
>> You received this
Re: [android-building] Add prebuilt jar to system image - android 9.0
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. android.hardware.radio-V1.0-java
is a module created by hardware/interfaces/radio/1.0/Android.bp. The
modules can be defined anywhere in the tree.
Taking a step back, what are you trying to accomplish? Why do you need
extra classes in framework.jar? Maybe it would be better to keep them
outside framework.jar but add them to the default classpath using
PRODUCT_BOOT_JARS? Or ship them as a separate shared library that apps can
opt into loading?
On Mon, Mar 18, 2019 at 1:34 PM KarenL wrote:
> 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 new folder structure under frameworks/base for these?
> If so - what does that structure look like.
>
> Thank you for your help.
>
>
>
> On Monday, March 18, 2019 at 1:06:45 PM UTC-7, Colin Cross wrote:
>>
>> 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 at 12:35 PM KarenL wrote:
>>
>>> 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 how to do this using
>>> blueprint files and soong.
>>>
>>> This is what I've tried and its not enough.
>>>
>>> Add a new folder to frameworks/base for my source files:
>>> frameworks/base/myfolder/java/com/xxx
>>>
>>> Edit the Android.bp file in frameworks/base and add source files to the
>>> "srcs" list
>>> "myfolder/java/com/xxx/source1.java"
>>> "myfolder/java/com/xxx/source2.java"
>>>
>>> Edit the "static_libs" list and add my prebuilt jars
>>> "prebuilt_jar1",
>>> "prebuilt_jar2",
>>>
>>> I'm not sure where to put these prebuilt jars.
>>> Do they go somewhere inside myfolder? Where are the other static libs in
>>> this list picked up from?
>>> Do I need to create .bp files inside myfolder to build this new part?
>>>
>>> Do you have any suggestions as to how to add prebuilt jars to Android 9.
>>>
>>> Thanks for your help.
>>> Karen
>>>
>>> --
>>> --
>>> You received this message because you are subscribed to the "Android
>>> Building" mailing list.
>>> To post to this group, send email to android-...@googlegroups.com
>>> To unsubscribe from this group, send email to
>>> android-buildi...@googlegroups.com
>>> For more options, visit this group at
>>> http://groups.google.com/group/android-building?hl=en
>>>
>>> ---
>>> You received this message because you are subscribed to the Google
>>> Groups "Android Building" group.
>>> To unsubscribe from this group and stop receiving emails from it, send
>>> an email to android-buildi...@googlegroups.com.
>>> For more options, visit https://groups.google.com/d/optout.
>>>
>> --
> --
> 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 from this group, send email to
> android-building+unsubscr...@googlegroups.com
> For more options, visit this group at
> http://groups.google.com/group/android-building?hl=en
>
> ---
> You received this message because you are subscribed to the Google Groups
> "Android Building" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to android-building+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>
--
--
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 from this group, send email to
android-building+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/android-building?hl=en
---
You received this message because you are subscribed to the Google Groups
"Android Building" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to android-building+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Re: [android-building] how to get compile_commands.json by mma or mm from android.mk in aosp project of android 9
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 Willemsen' via Android Building < android-building@googlegroups.com> wrote: > 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 a call to the compiler): > https://github.com/ninja-build/ninja/issues/1377 > > I'd recommend converting to Android.bp so that you can use > SOONG_GEN_COMPDB. > > - Dan > > On Mon, Mar 18, 2019 at 9:54 AM wrote: > >> I can get CMakeLists.txt from Android.bp by soong, then get >> compile_commands, but cann't get CMakeLists.json from android.mk. I've >> tried pass ' -t compdb cxx' but just get empty "[ \n ]" , any one can help >> me? >> >> -- >> -- >> 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 from this group, send email to >> android-building+unsubscr...@googlegroups.com >> For more options, visit this group at >> http://groups.google.com/group/android-building?hl=en >> >> --- >> You received this message because you are subscribed to the Google Groups >> "Android Building" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to android-building+unsubscr...@googlegroups.com. >> For more options, visit https://groups.google.com/d/optout. >> > -- > -- > 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 from this group, send email to > android-building+unsubscr...@googlegroups.com > For more options, visit this group at > http://groups.google.com/group/android-building?hl=en > > --- > You received this message because you are subscribed to the Google Groups > "Android Building" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to android-building+unsubscr...@googlegroups.com. > For more options, visit https://groups.google.com/d/optout. > -- -- 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 from this group, send email to android-building+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-building?hl=en --- You received this message because you are subscribed to the Google Groups "Android Building" group. To unsubscribe from this group and stop receiving emails from it, send an email to android-building+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [android-building] Add prebuilt jar to system image - android 9.0
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 new folder structure under frameworks/base for these?
If so - what does that structure look like.
Thank you for your help.
On Monday, March 18, 2019 at 1:06:45 PM UTC-7, Colin Cross wrote:
>
> 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 at 12:35 PM KarenL >
> wrote:
>
>> 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 how to do this using blueprint files and soong.
>>
>> This is what I've tried and its not enough.
>>
>> Add a new folder to frameworks/base for my source files:
>> frameworks/base/myfolder/java/com/xxx
>>
>> Edit the Android.bp file in frameworks/base and add source files to the
>> "srcs" list
>> "myfolder/java/com/xxx/source1.java"
>> "myfolder/java/com/xxx/source2.java"
>>
>> Edit the "static_libs" list and add my prebuilt jars
>> "prebuilt_jar1",
>> "prebuilt_jar2",
>>
>> I'm not sure where to put these prebuilt jars.
>> Do they go somewhere inside myfolder? Where are the other static libs in
>> this list picked up from?
>> Do I need to create .bp files inside myfolder to build this new part?
>>
>> Do you have any suggestions as to how to add prebuilt jars to Android 9.
>>
>> Thanks for your help.
>> Karen
>>
>> --
>> --
>> You received this message because you are subscribed to the "Android
>> Building" mailing list.
>> To post to this group, send email to android-...@googlegroups.com
>>
>> To unsubscribe from this group, send email to
>> android-buildi...@googlegroups.com
>> For more options, visit this group at
>> http://groups.google.com/group/android-building?hl=en
>>
>> ---
>> You received this message because you are subscribed to the Google Groups
>> "Android Building" group.
>> To unsubscribe from this group and stop receiving emails from it, send an
>> email to android-buildi...@googlegroups.com .
>> For more options, visit https://groups.google.com/d/optout.
>>
>
--
--
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 from this group, send email to
android-building+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/android-building?hl=en
---
You received this message because you are subscribed to the Google Groups
"Android Building" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to android-building+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Re: [android-building] Add prebuilt jar to system image - android 9.0
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 at 12:35 PM KarenL wrote:
> 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 how to do this using blueprint files and soong.
>
> This is what I've tried and its not enough.
>
> Add a new folder to frameworks/base for my source files:
> frameworks/base/myfolder/java/com/xxx
>
> Edit the Android.bp file in frameworks/base and add source files to the
> "srcs" list
> "myfolder/java/com/xxx/source1.java"
> "myfolder/java/com/xxx/source2.java"
>
> Edit the "static_libs" list and add my prebuilt jars
> "prebuilt_jar1",
> "prebuilt_jar2",
>
> I'm not sure where to put these prebuilt jars.
> Do they go somewhere inside myfolder? Where are the other static libs in
> this list picked up from?
> Do I need to create .bp files inside myfolder to build this new part?
>
> Do you have any suggestions as to how to add prebuilt jars to Android 9.
>
> Thanks for your help.
> Karen
>
> --
> --
> 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 from this group, send email to
> android-building+unsubscr...@googlegroups.com
> For more options, visit this group at
> http://groups.google.com/group/android-building?hl=en
>
> ---
> You received this message because you are subscribed to the Google Groups
> "Android Building" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to android-building+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>
--
--
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 from this group, send email to
android-building+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/android-building?hl=en
---
You received this message because you are subscribed to the Google Groups
"Android Building" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to android-building+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[android-building] Re: Creating and applying OTA on Android 9 AOSP
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 name of the FOTA tool. Do you mind filing a bug (public or partner issue tracker) with more info? On Wednesday, March 13, 2019 at 11:44:04 AM UTC-7, Fernando Medina wrote: > > We build our own internal distro of AOSP software and have always created > OTA files in the following manner for previous AOSP versions: > > ./build/tools/releasetools/ota_from_target_files > dist_output/tardis-target_files.zip ota_update.zip as per documentation. > > We have never had issues applying those OTA files, either manually in > recovery or using our internal FOTA tool. > > In Android 9, we build the OTA files and they work when doing it manually > in recovery, but it fails with our custom FOTA tool that has worked all the > way through AOSP 8. > > We get the following error when our FOTA client tries to apply OTA package. > > W/System.err: java.io.FileNotFoundException: /cache/recovery/uncrypt_file > (Permission denied) > > We are not sure if the building of the OTA file has changed or if we are > missing some new permission we need on FOTA client? Any ideas? > > Thanks, > > > -- -- 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 from this group, send email to android-building+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-building?hl=en --- You received this message because you are subscribed to the Google Groups "Android Building" group. To unsubscribe from this group and stop receiving emails from it, send an email to android-building+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[android-building] Add prebuilt jar to system image - android 9.0
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 how to do this using blueprint files and soong. This is what I've tried and its not enough. Add a new folder to frameworks/base for my source files: frameworks/base/myfolder/java/com/xxx Edit the Android.bp file in frameworks/base and add source files to the "srcs" list "myfolder/java/com/xxx/source1.java" "myfolder/java/com/xxx/source2.java" Edit the "static_libs" list and add my prebuilt jars "prebuilt_jar1", "prebuilt_jar2", I'm not sure where to put these prebuilt jars. Do they go somewhere inside myfolder? Where are the other static libs in this list picked up from? Do I need to create .bp files inside myfolder to build this new part? Do you have any suggestions as to how to add prebuilt jars to Android 9. Thanks for your help. Karen -- -- 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 from this group, send email to android-building+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-building?hl=en --- You received this message because you are subscribed to the Google Groups "Android Building" group. To unsubscribe from this group and stop receiving emails from it, send an email to android-building+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [android-building] AOSP libselinux build error for android-q-preview-1
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, 2019 at 12:18:59 PM UTC-7, Jacob Abrams wrote: > > 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 > "android-q-preview-1" tag is. > > I guess Google won't actually be releasing the source code for Q until > after they go through several preview releases? It appears that is what > they did last time with Pie. > > Jacob > > On Thursday, March 14, 2019 at 8:29:47 AM UTC-7, shahul hameed wrote: >> >> Hi Jacob, >> >> Is Android Q source available? can you share me link to download source. >> >> Regards, >> SkShahul. >> >> On Thu, Mar 14, 2019, 11:31 AM Jacob Abrams wrote: >> >>> Getting the following error when trying to build Q preview aosp generic >>> aosp_arm: >>> >>> >>> PLATFORM_VERSION_CODENAME=Q >>> PLATFORM_VERSION=Q >>> TARGET_PRODUCT=aosp_arm >>> TARGET_BUILD_VARIANT=eng >>> TARGET_BUILD_TYPE=release >>> TARGET_ARCH=arm >>> TARGET_ARCH_VARIANT=armv7-a-neon >>> TARGET_CPU_VARIANT=generic >>> HOST_ARCH=x86_64 >>> HOST_2ND_ARCH=x86 >>> HOST_OS=linux >>> HOST_OS_EXTRA=Linux-4.15.0-45-generic-x86_64-Ubuntu-16.04.6-LTS >>> HOST_CROSS_OS=windows >>> HOST_CROSS_ARCH=x86 >>> HOST_CROSS_2ND_ARCH=x86_64 >>> HOST_BUILD_TYPE=release >>> BUILD_ID=PI >>> OUT_DIR=out >>> >>> [100% 134/134] out/soong/.bootstrap/bin/soong_build out/soong/build.ninja >>> FAILED: out/soong/build.ninja >>> out/soong/.bootstrap/bin/soong_build -t -l >>> out/.module_paths/Android.bp.list -b out/soong -n out -d >>> out/soong/build.ninja.d -globFile out/soong/.bootstrap/build-globs.ninja -o >>> out/soong/build.ninja Android.bp >>> error: frameworks/native/libs/gui/Android.bp:20:1: module "libgui" >>> variant "android_arm_armv7-a-neon_core_shared_asan": links a library >>> "libselinux" which is not LL-NDK, VNDK-SP, or explicitly marked as >>> 'double_loadable:true'. (dependency: libgui -> libbufferhubqueue -> >>> libpdx_default_transport -> libselinux) >>> >>> I went to external/selinux/libselinux/Android.bp and added >>> "double_loadable: true" to that particular module and the build is >>> continuing now. Not sure what effect that has, but likely needs a fix? >>> >>> Best, >>> Jacob >>> >>> -- >>> -- >>> You received this message because you are subscribed to the "Android >>> Building" mailing list. >>> To post to this group, send email to android-...@googlegroups.com >>> To unsubscribe from this group, send email to >>> android-buildi...@googlegroups.com >>> For more options, visit this group at >>> http://groups.google.com/group/android-building?hl=en >>> >>> --- >>> You received this message because you are subscribed to the Google >>> Groups "Android Building" group. >>> To unsubscribe from this group and stop receiving emails from it, send >>> an email to android-buildi...@googlegroups.com. >>> For more options, visit https://groups.google.com/d/optout. >>> >> -- -- 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 from this group, send email to android-building+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-building?hl=en --- You received this message because you are subscribed to the Google Groups "Android Building" group. To unsubscribe from this group and stop receiving emails from it, send an email to android-building+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [android-building] AOSP libselinux build error for android-q-preview-1
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 "android-q-preview-1" tag is. I guess Google won't actually be releasing the source code for Q until after they go through several preview releases? It appears that is what they did last time with Pie. Jacob On Thursday, March 14, 2019 at 8:29:47 AM UTC-7, shahul hameed wrote: > > Hi Jacob, > > Is Android Q source available? can you share me link to download source. > > Regards, > SkShahul. > > On Thu, Mar 14, 2019, 11:31 AM Jacob Abrams > wrote: > >> Getting the following error when trying to build Q preview aosp generic >> aosp_arm: >> >> >> PLATFORM_VERSION_CODENAME=Q >> PLATFORM_VERSION=Q >> TARGET_PRODUCT=aosp_arm >> TARGET_BUILD_VARIANT=eng >> TARGET_BUILD_TYPE=release >> TARGET_ARCH=arm >> TARGET_ARCH_VARIANT=armv7-a-neon >> TARGET_CPU_VARIANT=generic >> HOST_ARCH=x86_64 >> HOST_2ND_ARCH=x86 >> HOST_OS=linux >> HOST_OS_EXTRA=Linux-4.15.0-45-generic-x86_64-Ubuntu-16.04.6-LTS >> HOST_CROSS_OS=windows >> HOST_CROSS_ARCH=x86 >> HOST_CROSS_2ND_ARCH=x86_64 >> HOST_BUILD_TYPE=release >> BUILD_ID=PI >> OUT_DIR=out >> >> [100% 134/134] out/soong/.bootstrap/bin/soong_build out/soong/build.ninja >> FAILED: out/soong/build.ninja >> out/soong/.bootstrap/bin/soong_build -t -l >> out/.module_paths/Android.bp.list -b out/soong -n out -d >> out/soong/build.ninja.d -globFile out/soong/.bootstrap/build-globs.ninja -o >> out/soong/build.ninja Android.bp >> error: frameworks/native/libs/gui/Android.bp:20:1: module "libgui" >> variant "android_arm_armv7-a-neon_core_shared_asan": links a library >> "libselinux" which is not LL-NDK, VNDK-SP, or explicitly marked as >> 'double_loadable:true'. (dependency: libgui -> libbufferhubqueue -> >> libpdx_default_transport -> libselinux) >> >> I went to external/selinux/libselinux/Android.bp and added >> "double_loadable: true" to that particular module and the build is >> continuing now. Not sure what effect that has, but likely needs a fix? >> >> Best, >> Jacob >> >> -- >> -- >> You received this message because you are subscribed to the "Android >> Building" mailing list. >> To post to this group, send email to android-...@googlegroups.com >> >> To unsubscribe from this group, send email to >> android-buildi...@googlegroups.com >> For more options, visit this group at >> http://groups.google.com/group/android-building?hl=en >> >> --- >> You received this message because you are subscribed to the Google Groups >> "Android Building" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to android-buildi...@googlegroups.com . >> For more options, visit https://groups.google.com/d/optout. >> > -- -- 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 from this group, send email to android-building+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-building?hl=en --- You received this message because you are subscribed to the Google Groups "Android Building" group. To unsubscribe from this group and stop receiving emails from it, send an email to android-building+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[android-building] Re: android-9.0.0_r34 / aosp_x86_64-eng builds missing files, like /sepolicy - can't boot
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 missing, it can be avoided and work fine ? It tends to indicates that the standard generic build android-9.0.0_r34 / aosp_x86_64-eng is probably fine and can be booted in some way. But how... By running the emulator by command line, and adding a magic parameter, I got information about the way the Kernel and the others things are loaded by the emulator *./emulator -avd Eve_API_Q -show-kernel* For example : [0.00] Kernel command line: nopti qemu=1 no_timer_check androidboot. hardware=ranchu androidboot.serialno=EMULATOR28X0X23X0 clocksource=pit no-kvmclock console=ttyS0,38400 android.qemud=1 android.checkjni=1 qemu.gles=1 qemu. encrypt=1 qemu.opengles.version=131072 cma=288M@0-4G qemu.wifi=1 mac80211_hwsim.channels=2 androidboot.android_dt_dir=/proc/device-tree/ firmware/android/ skip_initramfs rootwait ro init=/init loop.max_part=7 dm="1 vroot none ro 1,0 5156696 verity 1 PARTUUID=1F043BE6-7A8C-43B6-8531-70B6C93CBBDC PARTUUID=1F043BE6-7A8C-43B6-8531-70B6C93CBBDC 4096 4096 644587 644587 sha1 926f02610018cd908ac13bfe96c403b304344292 02da5c0c5c30a948ae740375556f4bf37fc8a052 1 ignore_zero_blocks" androidboot.veritymode=enforcing androidboot.verifiedbootstate=orange root=/ dev/dm-0 ramoops.mem_address=0xff018000 ramoops.mem_size=0x1 memmap= 0x1$0xff018000 qemu.dalvik.vm.heapsize=384m mac80211_hwsim.mac_prefix= 5554 But it's really tough. I'll continue to check all that I can, but if some of you know how to do, or already done a "standard generic Android build" that works fine on standard supported hardware, and know what is mandatory to get it starting fine, you're welcome ! Le lundi 18 mars 2019 15:28:34 UTC+1, julien@gmail.com a écrit : > > 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 https://android.googlesource.com/platform/manifest -b >android-9.0.0_r34 >- repo sync >- source build/envsetup.sh >- lunch aosp_x86_64-eng >- make -j 8 > > *Running it on QEMU-KVM* > > I'm using the Kernel delivered inside the "out" folder, which is 4.4. I > successfully booted Debian with it on KVM (even if I just had command line > instead of graphic display, probably because of Xorg drivers of Debian). > It's able to see /dev/vdX disks but cannot see /dev/sdX disks. It has some > importance for the KVM parameters about disk mounting (drives parameters > are little bit longer) > > > > > *kvm -m 2048 -smp 4 * > > *-vga std * > > > > > > > > *-kernel kernel-ranchu -append "console=ttyS0 debug drm.debug=0x0 > androidboot.selinux=permissive androidboot.hardware=ranchu" -serial > mon:stdio -initrd ramdisk.img -drive > format=raw,index=0,if=none,id=system,file=system.img -device > virtio-blk-pci,drive=system -drive > format=raw,index=1,if=none,id=userdata,file=userdata.img -device > virtio-blk-pci,drive=userdata -drive > format=raw,index=2,if=none,id=cache,file=cache.img -device > virtio-blk-pci,drive=cache -drive > format=raw,index=3,if=none,id=vendor,file=vendor.img -device > virtio-blk-pci,drive=vendor* > > (in reality it's a bg command line so it's easier to see when I split > it). > > It makes volumes available this way : > >1. system beeing /dev/vda >2. userdata beeing /dev/vdb >3. cache beeing /dev/vdc >4. vendor beeing /dev/vdd > > *It cannot boot fine :* > It stops at failing to load the "/sepolicy" file that we are usually able > to find at the root of the ramdisk.img : this file is missing and it stops. > With or without the 4 drives it makes no difference, since the file is > missing from ramdisk.img, so I guess "mounting" would happen later. > > [1.163969] init: init first stage started! > [1.164537] init: Using Android DT directory > /proc/device-tree/firmware/android/ > [1.165485] init: First stage mount skipped (missing/incompatible fstab > in device tree) > [1.166509] init: Skipped setting INIT_AVB_VERSION (not in recovery > mode) > *[1.167318] init: Loading SELinux policy* > [1.167824] selinux: SELinux: Could not open /sepolicy: No such file > or directory > [1.167824] > [1.168978] init: Failed to load monolithic SELinux policy: No such > file or directory > [1.169934] init: Unable to load SELinux policy > [1.170490] init: Reboot start, reason: reboot, rebootTarget: bootloader > [1.171292] init[1]: segfault at 14 ip 00565e30 sp > 7ffcfd4651e0 error 4 in
Re: [android-building] Question about PRODUCT_HOST_PACKAGES and PRODUCT_PACKAGES
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 that you can add it to PRODUCT_PACKAGES, but not PRODUCT_HOST_PACKAGES, and get it installed only for the device. Sorry for the complication, Dan On Mon, Mar 18, 2019 at 7:28 AM Po Hu wrote: > 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 > PRODUCT_HOST_PACKAGES > build/make/core/main.mk:1183: warning: See > https://android.googlesource.com/platform/build/+/master/Changes.md#PRODUCT_HOST_PACKAGES > for more information > build/make/core/main.mk:1184: warning: _ badblocks > build/make/core/main.mk:1185: error: stop. > > Because badblocks happens to be a "host_supported" binary too. > How to make only the target one installed ? > I don't want to use "PRODUCT_HOST_PACKAGES += badblocks" to generate extra > host binary. > > -- > -- > 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 from this group, send email to > android-building+unsubscr...@googlegroups.com > For more options, visit this group at > http://groups.google.com/group/android-building?hl=en > > --- > You received this message because you are subscribed to the Google Groups > "Android Building" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to android-building+unsubscr...@googlegroups.com. > For more options, visit https://groups.google.com/d/optout. > -- -- 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 from this group, send email to android-building+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-building?hl=en --- You received this message because you are subscribed to the Google Groups "Android Building" group. To unsubscribe from this group and stop receiving emails from it, send an email to android-building+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [android-building] how to get compile_commands.json by mma or mm from android.mk in aosp project of android 9
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 a call to the compiler): https://github.com/ninja-build/ninja/issues/1377 I'd recommend converting to Android.bp so that you can use SOONG_GEN_COMPDB. - Dan On Mon, Mar 18, 2019 at 9:54 AM wrote: > I can get CMakeLists.txt from Android.bp by soong, then get > compile_commands, but cann't get CMakeLists.json from android.mk. I've > tried pass ' -t compdb cxx' but just get empty "[ \n ]" , any one can help > me? > > -- > -- > 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 from this group, send email to > android-building+unsubscr...@googlegroups.com > For more options, visit this group at > http://groups.google.com/group/android-building?hl=en > > --- > You received this message because you are subscribed to the Google Groups > "Android Building" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to android-building+unsubscr...@googlegroups.com. > For more options, visit https://groups.google.com/d/optout. > -- -- 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 from this group, send email to android-building+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-building?hl=en --- You received this message because you are subscribed to the Google Groups "Android Building" group. To unsubscribe from this group and stop receiving emails from it, send an email to android-building+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[android-building] android-9.0.0_r34 / aosp_x86_64-eng builds missing files, like /sepolicy - can't boot
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 https://android.googlesource.com/platform/manifest -b android-9.0.0_r34 - repo sync - source build/envsetup.sh - lunch aosp_x86_64-eng - make -j 8 *Running it on QEMU-KVM* I'm using the Kernel delivered inside the "out" folder, which is 4.4. I successfully booted Debian with it on KVM (even if I just had command line instead of graphic display, probably because of Xorg drivers of Debian). It's able to see /dev/vdX disks but cannot see /dev/sdX disks. It has some importance for the KVM parameters about disk mounting (drives parameters are little bit longer) *kvm -m 2048 -smp 4 * *-vga std * *-kernel kernel-ranchu -append "console=ttyS0 debug drm.debug=0x0 androidboot.selinux=permissive androidboot.hardware=ranchu" -serial mon:stdio -initrd ramdisk.img -drive format=raw,index=0,if=none,id=system,file=system.img -device virtio-blk-pci,drive=system -drive format=raw,index=1,if=none,id=userdata,file=userdata.img -device virtio-blk-pci,drive=userdata -drive format=raw,index=2,if=none,id=cache,file=cache.img -device virtio-blk-pci,drive=cache -drive format=raw,index=3,if=none,id=vendor,file=vendor.img -device virtio-blk-pci,drive=vendor* (in reality it's a bg command line so it's easier to see when I split it). It makes volumes available this way : 1. system beeing /dev/vda 2. userdata beeing /dev/vdb 3. cache beeing /dev/vdc 4. vendor beeing /dev/vdd *It cannot boot fine :* It stops at failing to load the "/sepolicy" file that we are usually able to find at the root of the ramdisk.img : this file is missing and it stops. With or without the 4 drives it makes no difference, since the file is missing from ramdisk.img, so I guess "mounting" would happen later. [1.163969] init: init first stage started! [1.164537] init: Using Android DT directory /proc/device-tree/firmware/android/ [1.165485] init: First stage mount skipped (missing/incompatible fstab in device tree) [1.166509] init: Skipped setting INIT_AVB_VERSION (not in recovery mode) *[1.167318] init: Loading SELinux policy* [1.167824] selinux: SELinux: Could not open /sepolicy: No such file or directory [1.167824] [1.168978] init: Failed to load monolithic SELinux policy: No such file or directory [1.169934] init: Unable to load SELinux policy [1.170490] init: Reboot start, reason: reboot, rebootTarget: bootloader [1.171292] init[1]: segfault at 14 ip 00565e30 sp 7ffcfd4651e0 error 4 in init[40+22a000] [1.172452] init: Reboot ending, jumping to kernel [1.173023] Unregister pv shared memory for cpu 0 [1.173024] Unregister pv shared memory for cpu 2 [1.173043] Unregister pv shared memory for cpu 3 [1.174913] Unregister pv shared memory for cpu 1 [1.176075] reboot: Restarting system with command 'bootloader' [1.176804] reboot: machine restart *What I already tried :* - aosp_cf_x86_64_tablet-userdebug - img files and Kernel, same problem - aosp_cf_x86_64_tv-userdebug - img files and Kernel,same problem - android-4.19 kernel (x86_64_defconfig with support of /dev/sdX but not /dev/vdX) - works fine with Debian but no change when booting Android - android-4.19 kernel (x86_64_defconfig edited for adding support of /dev/vdX too) - works fine with Debian but no change when booting Android *Do you know what I'm missing ?* >From https://source.android.com/setup/build/building we can read the following : *AOSP cannot be used from pure source code only and requires additional hardware-related proprietary libraries to run, such as for hardware graphics acceleration. See the sections below for download links and Device binaries for additional resources.* My understanding is that of course, for a real world device, specific drivers should probably be added. But for KVM / QEMU too ? At "lunch" command, hikey and google devices builds are complete and including the missing files, without adding any command. Also, for Sony devices, some commands are added between repo init and repo sync : - cd .repo - git clone https://github.com/sonyxperiadev/local_manifests - cd local_manifests - git checkout android-9.0.0_r34 - cd ../.. Is something like that mandatory for running on a standard KVM ? Or laptop/device on which every driver is included into the mainline kernel ? If so, is this a Google/Android thing, or Linaro ? Or something completely custom and unofficial ? (and where to find it) Thank you in advance ! For now, I'm completely stuck ;) Julien ROBIN -- -- You received this message because you are subscribed to the "Android Building"
Re: [android-building] make kernel of wahoo
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 algorithm),dtc(Device Tree compiler),libufdt(Used for optimization of dtos) and give proper path and config and use CC=clang. Coz pixel 2 user level programms are compiled using clang. So some of the files will be compile using Clang. export ARCH=arm64 export CROSS_COMPILE_ARM32=~/PATH_TO_directory(arm eabi 4.7 or 4.8)/arm-eabi- export CROSS_COMPILE=~/PATH_TO_DIR(aarch64)/ LZ4_PREBUILTS_BIN=prebuilts-master/misc/linux-x86/lz4 DTC_PREBUILTS_BIN=~/pATH TO/linux-x86/dtc LIBUFDT_PREBUILTS_BIN=`/pATH_TO_DIR/linux-x86/libufdt Saurabh Sakhare 8007157873 On Sat, Mar 16, 2019 at 9:07 PM <927002...@qq.com> wrote: > *i put below:* > export ARCH=arm64 > export CROSS_COMPILE_ARM32=aarch64-linux-android- > PATH=/home/shallin/android9_r22/prebuilts/gcc/linux-x86/aarch64/aarch64-linux-android-4.9/bin:$PATH > make wahoo_defconfig *and then i put "make" ,show like this* > > [image: error.jpg] > > how can i do > > -- > -- > 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 from this group, send email to > android-building+unsubscr...@googlegroups.com > For more options, visit this group at > http://groups.google.com/group/android-building?hl=en > > --- > You received this message because you are subscribed to the Google Groups > "Android Building" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to android-building+unsubscr...@googlegroups.com. > For more options, visit https://groups.google.com/d/optout. > -- -- 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 from this group, send email to android-building+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-building?hl=en --- You received this message because you are subscribed to the Google Groups "Android Building" group. To unsubscribe from this group and stop receiving emails from it, send an email to android-building+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[android-building] Question about PRODUCT_HOST_PACKAGES and PRODUCT_PACKAGES
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 PRODUCT_HOST_PACKAGES build/make/core/main.mk:1183: warning: See https://android.googlesource.com/platform/build/+/master/Changes.md#PRODUCT_HOST_PACKAGES for more information build/make/core/main.mk:1184: warning: _ badblocks build/make/core/main.mk:1185: error: stop. Because badblocks happens to be a "host_supported" binary too. How to make only the target one installed ? I don't want to use "PRODUCT_HOST_PACKAGES += badblocks" to generate extra host binary. -- -- 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 from this group, send email to android-building+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-building?hl=en --- You received this message because you are subscribed to the Google Groups "Android Building" group. To unsubscribe from this group and stop receiving emails from it, send an email to android-building+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [android-building] make kernel of wahoo
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: https://source.android.com/setup/build/building-kernels. Regards, Alessio On Sat, Mar 16, 2019 at 3:37 PM <927002...@qq.com> wrote: > *i put below:* > export ARCH=arm64 > export CROSS_COMPILE_ARM32=aarch64-linux-android- > PATH=/home/shallin/android9_r22/prebuilts/gcc/linux-x86/aarch64/aarch64-linux-android-4.9/bin:$PATH > make wahoo_defconfig *and then i put "make" ,show like this* > > [image: error.jpg] > > how can i do > > -- > -- > 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 from this group, send email to > android-building+unsubscr...@googlegroups.com > For more options, visit this group at > http://groups.google.com/group/android-building?hl=en > > --- > You received this message because you are subscribed to the Google Groups > "Android Building" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to android-building+unsubscr...@googlegroups.com. > For more options, visit https://groups.google.com/d/optout. > -- -- 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 from this group, send email to android-building+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-building?hl=en --- You received this message because you are subscribed to the Google Groups "Android Building" group. To unsubscribe from this group and stop receiving emails from it, send an email to android-building+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
