Hi Colin,

Thanks for you help - I found that toplevel Android.bp in my repo includes 
vendor/*/*, so you were right - Android.bp in vendor/company/Android.bp was not 
parsed.

BR, K.
________________________________
From: [email protected] <[email protected]> on behalf of Colin Cross 
<[email protected]>
Sent: Thursday, October 12, 2017 6:53:48 PM
To: [email protected]
Subject: Re: [android-building] Sharing cc_defaults across multiple levels of 
Android.bp

cc_defaults are normal modules in the global namespace, so if it can't find it 
either you typo'd the name or the Android.bp you defined it in is not being 
parsed.

On Thu, Oct 12, 2017 at 6:42 AM, 
<[email protected]<mailto:[email protected]>> 
wrote:
Hello,

I am working on the project, which is build as part of whole AOSP.

I have noticed that many levels of our build files repeat same compiler flags, 
multilib config, they are all vendor etc.

So I tried to create sth like:

cc_defaults {
    name: "product_defaults",
    compile_multilib: "64",
    cflags: ["-fexceptions", "-Wall", "-Wextra"],
    vendor: true,
}

optional_subdirs = ["*"]

but I am not able to references it out of the top level projects:

error: vendor/product/submodule/Android.bp:14:1: "target_library" depends on 
undefined module "product_defaults"

Is it possible to share common configuration using cc_defaults module outside 
single Android.bp? And if not what would be the best equivalent?

Best Regards,
Krzysztof Wesolowski



--
--
You received this message because you are subscribed to the "Android Building" 
mailing list.
To post to this group, send email to 
[email protected]<mailto:[email protected]>
To unsubscribe from this group, send email to
[email protected]<mailto:android-building%[email protected]>
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 
[email protected]<mailto:[email protected]>.
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 [email protected]
To unsubscribe from this group, send email to
[email protected]
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 
[email protected]<mailto:[email protected]>.
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 [email protected]
To unsubscribe from this group, send email to
[email protected]
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 [email protected].
For more options, visit https://groups.google.com/d/optout.

Reply via email to