[android-building] Re: GPL projects for DaydreamOS

2018-12-18 Thread 'Bill Yi' via Android Building
We pushed the kernel source for the following devices:
  Tag,   Branch,
 Project,Device
- android-daydreamos-8.0.0_r0.7, android-msm-vega-4.4-oreo-daydream, 
kernel/msm, Vega

Thanks

bill

-- 
-- 
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: Android 8.1 build error in ubuntu 14.04

2018-12-18 Thread soham1
Facing the same issue. Any idea how to solve it?

On Monday, May 21, 2018 at 11:02:47 AM UTC-4, Fish Zheng wrote:
>
> Hello, Colin, and Dan
>You are right, it really related to the fs type.
>With your comments, I did 2 new testings, one is on ext3, and 
> another is on ext4, both are successful.
>
>Back to my issue, I just noticed the hardware difference instead of 
> file system.
>Actually my VMware Ubuntu uses ext4, however my bare metal Ubuntu 
> uses xfs.
>
>So until now I can have a result:
>* I can build my code on ext3, ext4 partitions.
>* My failed case ralated to xfs -- though I still don't know the 
> root cause, why the out/host/linux-x86/bin/hidl-gen will touch the file 
> system's flag.
>
> I'll continue to observe this.
>
> THANKS for your professional hints.
>
> On Thursday, May 17, 2018 at 10:56:58 PM UTC+8, Dan Willemsen wrote:
>>
>> > This means that in my current opinion, the software environment is the 
>> same except for hardware (VMware vs. Bare metal).
>>
>> I don't recognize the above error, but this difference is strange. Is the 
>> source on the same type of filesystem in both cases? I know there have been 
>> issues with a few filesystems (iirc, ones that don't return extra file 
>> metadata during readdir, but require extra stat calls)
>>
>> - Dan
>>
>> On Thu, May 17, 2018, 7:31 AM Fish Zheng  wrote:
>>
>>> Hello,
>>>Did you fix this issue? or any update?
>>>I just got the same compiling error as yours.
>>>
>>>However I got two very strange comparison result, I can build it on a 
>>> Ubuntu-14.04.5 VMware but failed to do it on one bare metal Ubuntu-14.04.5 
>>> workstation.
>>>I can promise I do install these 2 Ubuntu ENV using the same 
>>> installation iso. I also install the same dependencies or tools for example:
>>> ```
>>>$ sudo apt-get install git ccache automake lzop bison gperf 
>>> build-essential zip curl zlib1g-dev zlib1g-dev:i386 g++-multilib 
>>> python-networkx libxml2-utils bzip2 libbz2-dev libbz2-1.0 libghc-bzlib-dev 
>>> squashfs-tools pngcrush schedtool dpkg-dev liblz4-tool make optipng
>>>$ sudo apt-get install python-wand python-crypto liblz4-tool
>>> ```
>>>This means that in my current opinion, the software environment is 
>>> the same except for hardware (VMware vs. Bare metal).
>>>I am very confused of this now. 
>>>
>>>
>>> On Thursday, March 15, 2018 at 10:52:45 PM UTC+8, zeo...@naver.com 
>>> wrote:

 Hi
 When i try to build AOSP O(8.1.0), i got this error. 
 Can anyone help me on this?

 [  0% 9/47545] target Generated: android.hardware.usb-V1.1-java <= 
 hardware/interfaces/usb/1.1/types.hal
 FAILED: 
 out/target/common/gen/JAVA_LIBRARIES/android.hardware.usb-V1.1-java_intermediates/android/hardware/usb/V1_1/PortStatus_1_1.java
 /bin/bash -c "out/host/linux-x86/bin/hidl-gen -o 
 out/target/common/gen/JAVA_LIBRARIES/android.hardware.usb-V1.1-java_intermediates
  
 -Ljava -randroid.hardware:hardware/interfaces 
 -randroid.hidl:system/libhidl/transport 
 android.hardware.usb@1.1::types.PortStatus_1_1"
 ERROR: Failed to lookup type 'PortMode' at 
 hardware/interfaces/usb/1.1/types.hal:22.21-28
 ERROR: Failed to lookup type 'PortStatus' at 
 hardware/interfaces/usb/1.1/types.hal:45.5-14
 ERROR: Failed to lookup type 'PortMode_1_1' at 
 hardware/interfaces/usb/1.1/types.hal:51.14-25
 ERROR: Failed to lookup type 'PortMode_1_1' at 
 hardware/interfaces/usb/1.1/types.hal:56.5-16
 ERROR: Could not parse android.hardware.usb@1.1::types.PortStatus_1_1. 
 Aborting.
 [  0% 10/47545] target Generated: android.hardware.usb-V1.1-java <= 
 hardware/interfaces/usb/1.1/types.hal
 FAILED: 
 out/target/common/gen/JAVA_LIBRARIES/android.hardware.usb-V1.1-java_intermediates/android/hardware/usb/V1_1/PortMode_1_1.java
 /bin/bash -c "out/host/linux-x86/bin/hidl-gen -o 
 out/target/common/gen/JAVA_LIBRARIES/android.hardware.usb-V1.1-java_intermediates
  
 -Ljava -randroid.hardware:hardware/interfaces 
 -randroid.hidl:system/libhidl/transport 
 android.hardware.usb@1.1::types.PortMode_1_1"
 ERROR: Failed to lookup type 'PortMode' at 
 hardware/interfaces/usb/1.1/types.hal:22.21-28
 ERROR: Failed to lookup type 'PortStatus' at 
 hardware/interfaces/usb/1.1/types.hal:45.5-14
 ERROR: Failed to lookup type 'PortMode_1_1' at 
 hardware/interfaces/usb/1.1/types.hal:51.14-25
 ERROR: Failed to lookup type 'PortMode_1_1' at 
 hardware/interfaces/usb/1.1/types.hal:56.5-16
 ERROR: Could not parse android.hardware.usb@1.1::types.PortMode_1_1. 
 Aborting.
 [  0% 11/47545] target Generated: android.hardware.usb-V1.1-java <= 
 hardware/interfaces/usb/1.1/IUsb.hal
 FAILED: 
 out/target/common/gen/JAVA_LIBRARIES/android.hardware.usb-V1.1-java_intermediates/android/hardware/usb/V1_1/IUsb.java
 /bi

[android-building] Failing to build sdk and sdk_addon in master P

2018-12-18 Thread konstantin . karasik
Hey there,

I am rather new to AOSP development and i am trying to build a sdk version 
and a sdk_addon but it fails.
This is after i managed to build regularly successfully.

I am using the *master branch* from google source.
*lunch option*: aosp-arm64  userdebug

*commands tried*: 
make sdk -j6   
make PRODUCT-sample_addon-sdk_addon -j6 

I was trying to understand how and where i get the *mkstubs* development 
tool to compile in P, as it is not being 
built in the the normal build option. 
After scouring the internet for answers but couldn't find any i thought 
maybe using these options
will build them for me and i can get some more understanding on how to 
control which tool is built.

Can you please explain why those builds fail for me and how i can add such 
development tools to the build?

Thank you,
Konstantin

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