nandi/frqpublic Fork 0
bffe879efd6e16d866307e451e9a3568976fcdb2
Commits
Clone
git clone https://git.rickub.com/nandi/frq.git
git clone ssh://git@rickub.com/nandi/frq.git

Host key fingerprint (ed25519): SHA256:iycHnxEyq0Q7uyVpB7JlznP0G7JrTPXLYRcAU5CSLhc — verify it before your first connect.

Build the APK with buck2, from pins rather than from a second checkout a71ef8f · on bffe879efd6e16d866307e451e9a3568976fcdb2 · nandi · 18d ago
BUCK · 33 lines · 1.4 KBPython Blame HistoryRaw
 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
load("@prelude//platforms:defs.bzl", "host_configuration")
load(":defs.bzl", "execution_platform")

# Where every action runs: locally, against the BuildBuddy cache. The same
# arrangement jolt-native uses, and registered the same two ways — `[build]
# execution_platforms` in .buckconfig and `[parser] target_platform_detector_spec`
# there too, since setting only the first leaves toolchain-owned actions on the
# prelude's uncached default.
execution_platform(
    name = "cache",
    cpu_configuration = host_configuration.cpu,
    os_configuration = host_configuration.os,
    use_windows_path_separators = host_info().os.is_windows,
    visibility = ["PUBLIC"],
)

# The same platform, allowed to dispatch. Most of this graph cannot use it: the
# packaging steps name an Android SDK, a Chez cross build and an OpenSSL by
# absolute path, and a worker has none of them. The boot image compile is the
# one that could, which is why jolt reaches it through a manifest rather than a
# path — see android/BUCK.
execution_platform(
    name = "remote",
    cpu_configuration = host_configuration.cpu,
    os_configuration = host_configuration.os,
    remote_enabled = True,
    remote_execution_properties = {
        "OSFamily": "Linux",
        "container-image": "docker://gcr.io/flame-public/rbe-ubuntu24-04:latest",
    },
    use_windows_path_separators = host_info().os.is_windows,
    visibility = ["PUBLIC"],
)