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 .vendor` instead of `m `
If you don't need both copies of the module,
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
