summaryrefslogtreecommitdiff
path: root/vibrator/drv2624/apex/Android.bp
blob: 016a793572e6a22acd55b7f2dc59a212684817c8 (plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
package {
    default_applicable_licenses: ["Android-Apache-2.0"],
}

apex {
    name: "com.android.vibrator.drv2624",
    manifest: "apex_manifest.json",
    key: "com.android.vibrator.drv2624.key",
    certificate: ":com.android.vibrator.drv2624.certificate",
    file_contexts: "file_contexts",
    use_vndk_as_stable: true,
    updatable: false,

    // install the apex in /vendor/apex
    proprietary: true,

    // BEGIN of apex payloads
    // /bin
    binaries: [
        "android.hardware.vibrator-service.drv2624",
    ],
    // /etc
    prebuilts: [
        "com.android.vibrator.drv2624.rc",
    ],
    // END of apex payloads

    // BEGIN of companion files to be installed if this module is installed
    // init script, which is installed in /vendor/etc.
    // Note that init scripts in an apex can contain only "service" sections.
    // The following init script contains "on" section to enable the service.
    init_rc: [
        "com.android.vibrator.drv2624.enable.rc",
    ],

    // vintf manifest fragments, which is installed in /vendor/etc/vintf.
    // TODO(b/130058564): should we put vintf framgments within the apex?
    vintf_fragments: [
        "com.android.vibrator.drv2624.xml",
    ],
    // END of companion filse
}

apex_key {
    name: "com.android.vibrator.drv2624.key",
    public_key: "com.android.vibrator.drv2624.pubkey",
    private_key: "com.android.vibrator.drv2624.pem",
}

android_app_certificate {
    name: "com.android.vibrator.drv2624.certificate",
    certificate: "com.android.vibrator.drv2624",
}

prebuilt_etc {
    name: "com.android.vibrator.drv2624.rc",
    src: "com.android.vibrator.drv2624.rc",
    installable: false,
}