No, there's nothing you need to do. vendor_available defines two
installations -- one into the vendor partition and one into the system
partition. To trigger the installation of the vendor version, you may need
to specify `m <modulename>.vendor` instead of `m <modulename>`

If you don't need both copies of the module, use `vendor: true` instead of
vendor_available. You may still need the .vendor on the command line, I
don't remember.

- Dan

On Fri, Aug 30, 2019 at 10:37 AM Donal Morrissey <donal.morris...@gmail.com>
wrote:

> Hi There,
> This is my setup:
>
>    - AOSP branch: android-9.0.0_r46
>    - Target: generic_x86_64
>
> I'm currently working on an Android example HIDL interface, with
> accompanying client and server processes. These are all created in a new
> vendor directory structure at the top level of the repo checkout.:
> vendor/
> └── horizonemb
>     ├── clients
>     │   └── example_client
>     │       ├── Android.bp
>     │       └── exampleClient.cpp
>     └── interfaces
>         ├── Android.bp
>         └── example
>             └── 1.0
>                 ├── Android.bp
>                 ├── default
>                 │   ├── Android.bp
>                 │   ├── Example.cpp
>                 │   ├── Example.h
>                 │   ├── service.cpp
>                 │   └── vendor.horizonemb.hardware.exam...@1.0-service.rc
>                 └── IExample.hal
>
>
> If I change the VNDK related properties (vendor_available, etc) in any of
> my Android.bp files, their installation destination (/vendor v's /system)
> does not change when I build with the '*m*' command. I have to first
> delete the out directory and then carry out a full build.
>
> After modifying an Android.bp file, is there some other command I need to
> run before I build with the '*m*' command?
>
> Thank you,
> Donal
>
> --
> --
> 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/ee745977-4c3e-428a-9825-2fd2ffafab77%40googlegroups.com
> <https://groups.google.com/d/msgid/android-building/ee745977-4c3e-428a-9825-2fd2ffafab77%40googlegroups.com?utm_medium=email&utm_source=footer>
> .
>

-- 
-- 
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/CALQgHdkEN_s0My8gektb6Y-ihExgDm9_Z36aBzAaYar1uQK3ew%40mail.gmail.com.

Reply via email to