date:20170925

[android-building] Re: please push source for the 7.1.2_r33 revision of the flounder prebuilt kernel

2017-09-25 Thread 'Xin Li' via Android Building

Hi,

The android-7.1.2_r33 tag is for build NZH54D, which is meant for Pixel and 
Pixel XL devices only, therefore, no flounder images were published for 
that release.

As of today, the latest supported build for flounder is N4F27O 
(android-7.1.1_r51), and the corresponding kernel is available at 
https://android.googlesource.com/kernel/tegra/+/android-7.1.1_r0.74 

 .

Cheers,

-- 
-- 
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] Re: Problems building android-8.0.0_r4 branch

2017-09-25 Thread Colin Cross

It is somewhat ironic that unicode support sources fail to build because of
unicode issues.

On my AOSP master build:
$ echo $LANG
en_US.UTF-8
$ file
out/target/common/obj/JAVA_LIBRARIES/android_system_stubs_current_intermediates/src/android/icu/lang/UCharacterCategory.java
out/target/common/obj/JAVA_LIBRARIES/android_system_stubs_current_intermediates/src/android/icu/lang/UCharacterCategory.java:
UTF-8 Unicode text
$ file
out/target/common/obj/JAVA_LIBRARIES/android_system_stubs_current_intermediates/src/android/nfc/FormatException.java
out/target/common/obj/JAVA_LIBRARIES/android_system_stubs_current_intermediates/src/android/nfc/FormatException.java:
ASCII text

Have you tried regenerating those files after setting LANG?
$ export LANG=en_US.UTF-8
$ rm
-rf 
out/target/common/obj/JAVA_LIBRARIES/android_system_stubs_current_intermediates
$ m

On Mon, Sep 25, 2017 at 8:26 AM,  wrote:

> bump. I have encountered exactly the same issue. The files in question are
> located in " out/target/common/obj/JAVA_LIBRARIES/android_system_
> stubs_current_intermediates/src/android/icu/" (all files in 4 folders
> called: "lang", "math", "text" and "util"). They all seem to be stub
> classes generated by the build. Running file -i {path_to_filename} reveals
> that their character encoding is "iso-8859-1" which has problem with the
> unicode copywrite symbol. I have changed the locale of my linux system to
> en_US.utf8 which unfortunately has not helped. I am building on a Linux
> Virtual Machine if that's of any help.
>
>
> On Wednesday, September 6, 2017 at 5:58:50 PM UTC+1, Sean Hicks wrote:
>>
>> I'm trying to build the AOSP (Oreo) for the Nexus 5x. I am building on
>> Ubuntu 14.04.
>>
>>
>> I went to https://source.android.com/source/requirements and installed
>> all of the requirements. I even uninstalled my version of OpenJDK8 (161) in
>> favor of the 45 version on the site. By using sudo update-alternatives
>> --all, I made sure all of my java related commands point to this version of
>> java 8.
>>
>>
>> I got the binary preview blobs from https://developers.google
>> .com/android/blobs-preview and untar'd/ran after getting the AOSP.
>>
>>
>> From the build numbers page https://source.android.co
>> m/source/build-numbers I found the build for the nexus 5X is
>> OPR6.170623.013, corresponding to branch android-8.0.0_r4.
>>
>>
>> So, I repo init -b android-8.0.0_r4, followed by a repo sync, followed by
>> extracting my binary images (which placed them in vendor, as expected).
>> Then I did a lunch, selecting aosp-bullhead-userdebug (option 25), and then
>> make -j8.
>>
>>
>> After over an hour of building, the build fails (81 errors) on many of
>> the java files with the following error.
>>
>>
>> "error: unmappable character encoding for UTF-8 // ? 2016 and later:
>> Unicode, Inc. and others."
>>
>>
>> Does anyone know how I can resolve this build error?
>>
> --
> --
> 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: Problems building android-8.0.0_r4 branch

2017-09-25 Thread mobiledevelopers

bump. I have encountered exactly the same issue. The files in question are 
located in " 
out/target/common/obj/JAVA_LIBRARIES/android_system_stubs_current_intermediates/src/android/icu/"
 
(all files in 4 folders called: "lang", "math", "text" and "util"). They 
all seem to be stub classes generated by the build. Running file -i 
{path_to_filename} reveals that their character encoding is "iso-8859-1" 
which has problem with the unicode copywrite symbol. I have changed the 
locale of my linux system to en_US.utf8 which unfortunately has not helped. 
I am building on a Linux Virtual Machine if that's of any help.

On Wednesday, September 6, 2017 at 5:58:50 PM UTC+1, Sean Hicks wrote:
>
> I'm trying to build the AOSP (Oreo) for the Nexus 5x. I am building on 
> Ubuntu 14.04.
>
>
> I went to https://source.android.com/source/requirements and installed 
> all of the requirements. I even uninstalled my version of OpenJDK8 (161) in 
> favor of the 45 version on the site. By using sudo update-alternatives 
> --all, I made sure all of my java related commands point to this version of 
> java 8.
>
>
> I got the binary preview blobs from 
> https://developers.google.com/android/blobs-preview and untar'd/ran after 
> getting the AOSP.
>
>
> From the build numbers page 
> https://source.android.com/source/build-numbers I found the build for the 
> nexus 5X is OPR6.170623.013, corresponding to branch android-8.0.0_r4.
>
>
> So, I repo init -b android-8.0.0_r4, followed by a repo sync, followed by 
> extracting my binary images (which placed them in vendor, as expected). 
> Then I did a lunch, selecting aosp-bullhead-userdebug (option 25), and then 
> make -j8.
>
>
> After over an hour of building, the build fails (81 errors) on many of the 
> java files with the following error.
>
>
> "error: unmappable character encoding for UTF-8 // ? 2016 and later: 
> Unicode, Inc. and others."
>
>
> Does anyone know how I can resolve this build error?
>

-- 
-- 
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: Black emulator on Building Android OREO on Linux 14.04 LTS

2017-09-25 Thread Chih-Wei Huang

You are not alone.
The emulator image built from 8.0.0 release
is totally broken. The issue is tracked in

https://issuetracker.google.com/issues/66066209

You can follow the instructions to build a bootable
emulator image for 8.0. But it's far from stable
than SDK image download from Google.

There must be more patches to fix that.

J Lee於 2017年9月20日星期三 UTC+8下午11時34分39秒寫道：
>
> I need help too.
> I have the exact same problem. I built android-8.0.0_r1 and 
> android-8.0.0_r11 x86-eng on Ubuntu 14.04 and the both of them have same 
> black emulator problem though the builds are sucessful.
> If emulator source is still not stable, is there any way to run the built 
> image on the emulator from standard Android SDK?
>
>
> On Wednesday, September 20, 2017 at 8:53:58 AM UTC-5, pranker wrote:
>>
>> Hi All,
>>
>> I have downloaded Android OREO code. (Branch - android-8.0.0_r4).
>>
>> The code builds successfully but on opening the emulator the emulator 
>> shows with a black screen and never opens.
>>
>> I get below messages while building.
>>
>> cts/apps/CtsVerifier/Android.mk:72: warning: FindEmulator: find: 
>> `cts/apps/CtsVerifier/src/com/android/cts/verifier/backup': No such file or 
>> directory
>> build/core/java_common.mk:88: warning: FindEmulator: cd: 
>> cts/hostsidetests/appsecurity/test-apps/WriteExternalStorageApp/cts/hostsidetests/appsecurity/test-apps/WriteExternalStorageApp/res:
>>  
>> No such file or directory
>> build/core/java_common.mk:88: warning: FindEmulator: cd: 
>> cts/hostsidetests/backup/assets: No such file or directory
>> cts/hostsidetests/os/test-apps/StaticSharedNativeLibProvider/Android.mk:23: 
>> warning: FindEmulator: find: 
>> `cts/hostsidetests/os/test-apps/StaticSharedNativeLibProvider/src': No such 
>> file or directory
>> cts/hostsidetests/os/test-apps/StaticSharedNativeLibProvider1/Android.mk:23: 
>> warning: FindEmulator: find: 
>> `cts/hostsidetests/os/test-apps/StaticSharedNativeLibProvider1/src': No 
>> such file or directory
>> cts/tests/tests/contactsproviderwipe/Android.mk:33: warning: 
>> FindEmulator: find: `cts/tests/tests/contactsproviderwipe/common/src': No 
>> such file or directory
>>
>>
>> And the below on running command emulator
>>
>> Your emulator is out of date, please update by launching Android Studio:
>>  - Start Android Studio
>>  - Select menu "Tools > Android > SDK Manager"
>>  - Click "SDK Tools" tab
>>  - Check "Android SDK Tools" checkbox
>>  - Click "OK"
>>
>> My Lunch option is aosp_arm64-eng
>>
>> Thanks for the help.
>>
>>

-- 
-- 
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: ERROR: --- target build has specified no recovery ---

2017-09-25 Thread James Muir

If you just want an ota package, then you can use "make -jN otapackage".

If you want to resign the ota package, then try calling "make -jN dist" 
before using the release-tools scripts.

-James M

On Wednesday, September 13, 2017 at 10:41:05 AM UTC-4, Binit kumar wrote:
>
>
> * Intent*: To test OTA package in Emulator 
>
>  Steps:-
>  
>  source ./build/envsetup.sh
>  lunch aosp_arm-eng
>  make -j24
>  make target-files-package
>  
>  ./build/tools/releasetools/ota_from_target_files 
> out/target/product/generic/obj/PACKAGING/target_files_intermediates/aosp_arm-target_files-eng.root.zip
>  
> ota_update_generic.zip
> unzipping target target-files...
>
>ERROR: --- target build has specified no recovery ---
>
>
>   I have noticed that recovery.img file is not getting created for target 
> "aosp_arm-eng". Why? It is throwing error while creating OTA package.
>
> For other target like "bullhead_arm-userdebug", I have noticed that 
> recovery.img is getting created and I am able to create ota packages using 
> ota_from_target_files releasetools. But I am unable to run Emulator with 
> blank screen. Why ? 
>

-- 
-- 
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] Soong convert Android.mk file for shared lib that uses LOCAL_AIDL_INCLUDES

2017-09-25 Thread Rugnath Ram

Thanks michael,
build/soong$ androidmk Android.mk > Android.bp
androidmk: command not found
 
Please help me how to built androidmk? thanks in advance. 

On Tuesday, September 19, 2017 at 2:15:51 AM UTC+5:30, Michael Lekman wrote:
>
> $ androidmk  Android.mk > Android.bp
>
> androidmk must be built first. build/soong/androidmk/Android.bp
>
>
> On Monday, 18 September 2017 16:25:12 UTC+2, filzap...@gmail.com wrote:
>>
>> How you convert android.mk to android.bp file. I am looking for 
>> documentation but haven't find any thing? Can you please write the 
>> procedure here?
>>
>> Regards,
>>
>> On Saturday, September 16, 2017 at 9:54:44 PM UTC+2, Michael Lekman wrote:
>>>
>>> I found it. aidl export flag was missing:
>>>
>>> aidl: {
>>> local_include_dirs: ["api"],
>>> export_aidl_headers: true,
>>> }
>>>
>>>
>>> On Friday, 15 September 2017 16:15:31 UTC+2, Michael Lekman wrote:

 follow up question about aidl code generation: I have added this to my 
 Android.bp file

 cc_library_shared {
 name: "libtest",
 srcs: [
 "api/corp/proj/IGreatService.aidl",
 ],
 cppflags: [
 "-std=gnu++11",
 "-Wall",
 ],
 include_dirs: ["external/rapidjson/include"],
 local_include_dirs: ["."],
 export_include_dirs: ["."],
 compile_multilib: "both",
 shared_libs: [
 "liblog",
 "libbinder",
 "libutils",
 ],

 static_libs: ["libcutils"],
 aidl: {
 local_include_dirs: ["api"],
 }
 }


 Unfortunately it doesn't generated the header file from aidl.

 vendor/proj/proprietary/system/test/MyState.h:4:10: fatal error: 
 'corp/proj/IGreatService.h' file not found

 BR
 /Michael
  
 On Tuesday, 12 September 2017 23:38:16 UTC+2, Colin Cross wrote:
>
> Java support for soong is still a work in progress and not ready for 
> wide use yet.
>
> On Tue, Sep 12, 2017 at 10:37 AM, Michael Lekman  > wrote:
>
>> Thanks.
>>
>> It didn't translate LOCAL_RESOURCE_DIR and LOCAL_MANIFEST_FILE. Are 
>> they not supported anymore?
>>
>>
>> On Tuesday, 12 September 2017 19:12:16 UTC+2, Colin Cross wrote:
>>>
>>> That's a mistake in the androidmk tool, it should have produced:
>>> aidl: {
>>> local_include_dirs: ["api"],
>>> }
>>>
>>> On Tue, Sep 12, 2017 at 6:10 AM, Michael Lekman <
>>> michael...@gmail.com> wrote:
>>>
 Hello,

 I am trying to convert my Android.mk file to Android.bp.
 But it fails when I use aidl_includes. ANdroid.mk was converted 
 using androidmk.


 include $(CLEAR_VARS)
 LOCAL_MODULE := libmysharedlib
 LOCAL_SRC_FILES := \
 file.cpp \
 $(call all-Iaidl-files-under, api)
 LOCAL_CPPFLAGS := -std=gnu++11 -Wall
 LOCAL_C_INCLUDES += \
  $(LOCAL_PATH) \
  external/rapidjson/include
 LOCAL_LDFLAGS := -llog
 LOCAL_EXPORT_C_INCLUDE_DIRS := $(LOCAL_PATH)
 LOCAL_MULTILIB := both
 LOCAL_SHARED_LIBRARIES := \
 liblog \
 libbinder \
 libutils \
 libpowermanager \

 LOCAL_STATIC_LIBRARIES := libcutils
 LOCAL_AIDL_INCLUDES := $(LOCAL_PATH)/api

 include $(BUILD_SHARED_LIBRARY)

 FAILED: out/soong/build.ninja
 out/soong/.bootstrap/bin/soong_build -t -b out/soong -d 
 out/soong/build.ninja.d -o out/soong/build.ninja Android.bp
 Clang SA is not enabled
 error: vendor/my-shared-lib/Android.bp:38:18: unrecognized property 
 "aidl_includes"
 error: vendor/my-shared-lib/Android.bp:74:18: unrecognized property 
 "aidl_includes"
 ninja: build stopped: subcommand failed.
 13:59:19 soong bootstrap failed with: exit status 1
 make: *** [run_soong_ui] Error 1

 BR
 /Michael

 -- 
 -- 
 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.

>>>
>>> -- 
>> -- 
>>

[android-building] Re: please push source for the 7.1.2_r33 revision of the flounder prebuilt kernel

Re: [android-building] Re: Problems building android-8.0.0_r4 branch

[android-building] Re: Problems building android-8.0.0_r4 branch

[android-building] Re: Black emulator on Building Android OREO on Linux 14.04 LTS

[android-building] Re: ERROR: --- target build has specified no recovery ---

Re: [android-building] Soong convert Android.mk file for shared lib that uses LOCAL_AIDL_INCLUDES

6 matches

Site Navigation

Mail list logo

Footer information