Re: [android-building] Integration of new lib in license files

2018-12-06 Thread Sascha Effert
Hi Dan, thanks. Unfortunately I was out of office for a week, but now I coud create the ticket: https://issuetracker.google.com/issues/120561634 bests Sascha Am Donnerstag, 29. November 2018 21:42:43 UTC+1 schrieb Dan Willemsen: > > The hidl module types create new modules behind the scenes,

Re: [android-building] Integration of new lib in license files

2018-11-29 Thread 'Dan Willemsen' via Android Building
The hidl module types create new modules behind the scenes, and likely aren't forwarding the notice property. Can you file a bug at https://issuetracker.google.com/issues/new?component=381517 ? I can route it appropriately. Thanks, Dan On Thu, Nov 29, 2018 at 9:40 AM Sascha Effert wrote: > Hi

Re: [android-building] Integration of new lib in license files

2018-11-29 Thread Sascha Effert
Hi Dan, thanks, I found my problem. The Android.bp files containing the cc_library and cc_binary entries I am adding are in subdirectories under the directory that contains my NOTICE file. Therefore they have not been detected correctly. I added now a notice: "../../NOTICE", and

[android-building] Integration of new lib in license files

2018-11-28 Thread Sascha Effert
Hello, I added a new lib into our vendor HAL using soong. This is already running, it is part of our vendor Image and we can use it. The only problem left: added files or notmentioned in vendor.xml.gz in vendor/etc/, so the license information is missing. What is the way to get it in? I had a