Re: [android-building] shared library can't be copied into OTATOOLS

2020-05-15 Thread mohmod godo 
في الاثنين، ٤ مايو ٢٠٢٠ ٧:٢١ م 'Dan Willemsen' via Android Building <
android-building@googlegroups.com> كتب:

> What version of AOSP are you using? The current aosp/master builds of
> otatools.zip definitely have lib64/libbase.so:
> https://ci.android.com/builds/submitted/6459548/aosp_cf_x86_phone-userdebug/latest
>
> And printing out INTERNAL_OTATOOLS_MODULES_WITH_DEPS, it's getting libbase
> added from get-all-shared-libs-deps.
>
> - Dan
>
> On Mon, May 4, 2020 at 8:48 AM 임정민  wrote:
>
>> Hi I found there are no shared library in ota packages.
>>
>> I expect there are some modules and shared libraries.
>> but only existing were modules like lpunpack.
>> I hope there are shared libraries such as libbase.so.
>> but It's not working.
>>
>> I think get-all-shared-libs-deps is related with copying shared libraries
>> into ota_package. but It's not working
>> please check it for me
>>
>> thanks
>>
>> !!
>> /build/make/core/Makefile
>> !
>>
>> ---
>> INTERNAL_OTATOOLS_MODULES := \
>>   aapt2 \
>>   add_img_to_target_files \
>>   append2simg \
>>   avbtool \
>>   blk_alloc_to_base_fs \
>>   boot_signer \
>>   brillo_update_payload \
>>   brotli \
>>   bsdiff \
>>   build_image \
>>   build_super_image \
>>   build_verity_metadata \
>>   build_verity_tree \
>>   care_map_generator \
>>   check_ota_package_signature \
>>   check_target_files_signatures \
>>   check_target_files_vintf \
>>   checkvintf \
>>   delta_generator \
>>   e2fsck \
>>   e2fsdroid \
>>   fc_sort \
>>   fec \
>>   fs_config \
>>   generate_verity_key \
>>   img2simg \
>>   img_from_target_files \
>>   imgdiff \
>>   libconscrypt_openjdk_jni \
>>   lpmake \
>>   lpunpack \
>>   make_f2fs \
>>   merge_target_files \
>>   minigzip \
>>   mk_combined_img \
>>   mkbootfs \
>>   mkbootimg \
>>   mke2fs \
>>   mke2fs.conf \
>>   mkf2fsuserimg.sh \
>>   mksquashfs \
>>   mksquashfsimage.sh \
>>   mkuserimg_mke2fs \
>>   ota_from_target_files \
>>   sefcontext_compile \
>>   sgdisk \
>>   shflags \
>>   sign_apex \
>>   sign_target_files_apks \
>>   signapk \
>>   simg2img \
>>   sload_f2fs \
>>   tune2fs \
>>   unpack_bootimg \
>>   update_host_simulator \
>>   validate_target_files \
>>   verity_signer \
>>   verity_verifier \
>>   zipalign \
>>
>> # Additional tools to unpack and repack the apex file.
>> INTERNAL_OTATOOLS_MODULES += \
>>   apexer \
>>   deapexer \
>>   debugfs_static \
>>   merge_zips \
>>   resize2fs \
>>   soong_zip \
>>
>> ifeq (true,$(PRODUCT_SUPPORTS_VBOOT))
>> INTERNAL_OTATOOLS_MODULES += \
>>   futility \
>>   vboot_signer
>> endif
>>
>> INTERNAL_OTATOOLS_FILES := \
>>   $(filter $(HOST_OUT)/%,$(call
>> module-installed-files,$(INTERNAL_OTATOOLS_MODULES)))
>>
>> .PHONY: otatools
>> otatools: $(INTERNAL_OTATOOLS_FILES)
>>
>> # For each module, recursively resolve its host shared library
>> dependencies. Then we have a full
>> # list of modules whose installed files need to be packed.
>>
>> INTERNAL_OTATOOLS_MODULES_WITH_DEPS := \
>>   $(sort $(INTERNAL_OTATOOLS_MODULES) \
>>   $(foreach m,$(INTERNAL_OTATOOLS_MODULES),$(call
>> get-all-shared-libs-deps,$(m
>>
>> INTERNAL_OTATOOLS_PACKAGE_FILES := \
>>   $(filter $(HOST_OUT)/%,$(call
>> module-installed-files,$(INTERNAL_OTATOOLS_MODULES_WITH_DEPS)))
>>
>> INTERNAL_OTATOOLS_PACKAGE_FILES += \
>>   $(sort $(shell find build/make/target/product/security -type f -name
>> "*.x509.pem" -o \
>>   -name "*.pk8" -o -name verity_key))
>>
>> ifneq (,$(wildcard device))
>> INTERNAL_OTATOOLS_PACKAGE_FILES += \
>>   $(sort $(shell find device $(wildcard vendor) -type f -name "*.pk8" -o
>> -name "verifiedboot*" -o \
>>   -name "*.pem" -o -name "oem*.prop" -o -name "*.avbpubkey"))
>> endif
>> ifneq (,$(wildcard external/avb))
>> INTERNAL_OTATOOLS_PACKAGE_FILES += \
>>   $(sort $(shell find external/avb/test/data -type f -name
>> "testkey_*.pem" -o \
>>   -name "atx_metadata.bin"))
>> endif
>> ifeq (true,$(PRODUCT_SUPPORTS_VBOOT))
>> INTERNAL_OTATOOLS_PACKAGE_FILES += \
>>   $(sort $(shell find external/vboot_reference/tests/devkeys -type f))
>> endif
>>
>> INTERNAL_OTATOOLS_RELEASETOOLS := \
>>   $(sort $(shell find build/make/tools/releasetools -name "*.pyc" -prune
>> -o \
>>   \( -type f -o -type l \) -print))
>>
>> BUILT_OTATOOLS_PACKAGE := $(PRODUCT_OUT)/otatools.zip
>> $(BUILT_OTATOOLS_PACKAGE): PRIVATE_ZIP_ROOT := $(call
>> intermediates-dir-for,PACKAGING,otatools)/otatools
>> $(BUILT_OTATOOLS_PACKAGE): PRIVATE_OTATOOLS_PACKAGE_FILES :=
>> $(INTERNAL_OTATOOLS_PACKAGE_FILES)
>> $(BUILT_OTATOOLS_PACKAGE): PRIVATE_OTATOOLS_RELEASETOOLS :=
>> $(INTERNAL_OTATOOLS_RELEASETOOLS)
>> $(BUILT_OTATOOLS_PACKAGE): $(INTERNAL_OTATOOLS_PACKAGE_FILES)
>> $(INTERNAL_OTATOOLS_RELEASETOOLS)
>> $(BUILT_OTATOOLS_PACKAGE): $(SOONG_ZIP) $(ZIP2ZIP)
>> @echo "Package OTA tools: $@"
>> rm -rf $@ $(PRIVATE_ZIP_ROOT)
>> mkdir -p $(dir $@)
>> $(call
>>

Re: [android-building] Issue building AOSP with docker running on Mojave

2020-05-15 Thread 6020peaks /\/\/\ 
Thanks Dan! So I had a few issues which I enumerate below, so that this can
be useful for the next one hitting the wall like I did:
0. I created a case-sensitive volume on Mac that I shared with the docker
container.
1. I had to run the docker container with --privileged as suggested here:
https://issuetracker.google.com/issues/123210688 I was getting the
famous "nsjail error".
2. I added extra RAM to Docker Desktop on Mac to avoid the build process
being killed by the host.
3. For some reason the build would stop after 30 minutes. I did a `repo
sync` and then it started to build passing that time.

For the sake of comparing, the build is now at 44% after running longer
than 12 hours. The performance is quite poor in comparison to Docker
running on Linux. I read that this can be due to the I/O and the fact that
I shared a volume with the host OS. I didn't try this setup on Windows, but
I expect the same behavior. Definitely Linux is the way to go as
recommended everywhere.

On Thu, May 14, 2020 at 8:16 PM 'Dan Willemsen' via Android Building <
android-building@googlegroups.com> wrote:

> How much RAM have you given docker? `free -h` shows how much is available.
> IIRC, unlike on linux, because docker on Mac is a VM, it can't grow to use
> as much as necessary. Our docs list 16GB as the minimum available to the
> build.
>
> - Dan
>
> On Thu, May 14, 2020 at 9:30 AM 6020peaks /\/\/\ <6020pe...@gmail.com>
> wrote:
>
>> Hi,
>>
>> I wonder if anyone tried to build the master branch of AOSP using a
>> Docker container with Ubuntu 18.04 running on Mojave. If I compare the
>> process with a Docker container running on Linux, on Mac it is way slower.
>> And also the following issue appears when building. Any clue of what might
>> be happening?
>>
>> Thanks!
>>
>> 07:58:34 Build sandboxing disabled due to nsjail error.
>>
>> 
>>
>> PLATFORM_VERSION_CODENAME=S
>>
>> PLATFORM_VERSION=S
>>
>> TARGET_PRODUCT=aosp_x86_64
>>
>> TARGET_BUILD_VARIANT=eng
>>
>> TARGET_BUILD_TYPE=release
>>
>> TARGET_ARCH=x86_64
>>
>> TARGET_ARCH_VARIANT=x86_64
>>
>> TARGET_2ND_ARCH=x86
>>
>> TARGET_2ND_ARCH_VARIANT=x86_64
>>
>> HOST_ARCH=x86_64
>>
>> HOST_2ND_ARCH=x86
>>
>> HOST_OS=linux
>>
>> HOST_OS_EXTRA=Linux-4.19.76-linuxkit-x86_64-Ubuntu-18.04.4-LTS
>>
>> HOST_CROSS_OS=windows
>>
>> HOST_CROSS_ARCH=x86
>>
>> HOST_CROSS_2ND_ARCH=x86_64
>>
>> HOST_BUILD_TYPE=release
>>
>> BUILD_ID=AOSP.MASTER
>>
>> OUT_DIR=out
>>
>> 
>>
>> [100% 39/39] 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
>>
>> Killed
>>
>> 08:00:37 soong bootstrap failed with: exit status 1
>>
>> ninja: build stopped: subcommand failed.
>>
>>
>>  failed to build some targets (03:48 (mm:ss)) 
>>
>> --
>> --
>> 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.
>> To view this discussion on the web visit
>> https://groups.google.com/d/msgid/android-building/dc5e8f99-b0b8-46e2-9701-4f39f0f3dc13%40googlegroups.com
>> 
>> .
>>
> --
> --
> 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.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/android-building/CALQgHdmZyD2ej4puKrAJ3xGO%2B1cf5Od3z-4NoXrDXuS1srfEeA%40mail.gmail.com
> 
> .
>

-- 
-- 
You received this message because you are subscribed to the

[android-building] Building AOSP with libFuzzer including SanitizerCoverage

2020-05-15 Thread 'fa de' via Android Building 
I was able to build AOSP with libFuzzer and fuzz my target on an emulator. 
In order to get visual coverage feedback for libFuzzer I need to built it 
again, with the `Source-based Code Coverage`-modul (
https://clang.llvm.org/docs/SourceBasedCodeCoverage.html).

How can I add this module when building AOSP? Do I need to add the two 
flags `-fprofile-instr-generate -fcoverage-mapping` in the blueprints?


Thank you very much 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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/android-building/1228b85d-c2b6-4f9c-88d9-e8465898866c%40googlegroups.com.

[android-building] Re: No mkvendor.sh file in android source

2020-05-15 Thread ياسر الدوسري 
بتاريخ الاثنين، 5 مارس، 2018 2:14:59 ص UTC+3، كتب Amit Kumar:
> I am looking for a file "mkvendor.sh" but I am not able to find it in source 
> code. Kindly help me in this regard.
> 
> Thanking you

-- 
-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/android-building/a568a37b-e340-4366-94a7-cd0da0814d5f%40googlegroups.com.