+12
−0
+1
−0
Loading
Donate to e Foundation | Murena handsets with /e/OS | Own a part of Murena! Learn more
protobuf compilation defaults to dropping the generated objects and headers onto a path derived from the origin source path. This poses a problem with some of our repositories since they're not placed in their original paths, and may include hard references to pb headers assuming the original directory. Typical use of this will be to place a LOCAL_PROTOC_OUTPUT := <original repo path> line in the relevant module block (for example, "hardware/ril" for our "hardware/ril-caf") Change-Id: Ib9b0cadd47e29a0d2e693b331cfc18e71b048ee5 binary: Don't run protobuf header relocations if origin/target are the same Change-Id: I3746746bdf1526674f345d884e2eccef85e946ef build: Fix LOCAL_PROTOC_OUTPUT * This code was refactored in 7.1 adjust accordingly. * This is used by projects like ril-caf where the proto-c generated sources dir might not match the project path. Change-Id: I7a7d0bb7a397b02deb5406a591059a877ac2c6da