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
[]
= "kui-lua"
= true
= true
= true
= true
= "README.md"
= true
= true
= true
= "Lua extensions for kui via mlua: table trees in, events as tables out"
= ["crates-io", "drydock9"]
[]
= true
= true
# For `CExtension` alone: a script that places a native panel needs
# something to open the `.so`/`.dylib`/`.dll` with, and that loader is the
# C API's. `default-features = false` in the workspace manifest, so this is
# the library without its windowed runner — a Lua extension has no window
# of its own and would not use one (see the note in kui-ffi/Cargo.toml).
= true
[]
= true
= true
# The examples' devtools (docs/adr/0021), for the Rust host of the panel.
= true
# tests/conformance.rs drives the scene corpus, which kui-core keeps behind a
# feature; on here only, so the published extension does not carry it.
= { = true, = ["conformance"] }
# Reads `kui-core/tests/fixtures/size_spellings.json`, the size spellings
# every binding is run through (backlog RG94).
= "1"
# See the note in crates/kui-native/Cargo.toml: examples live under examples/ at the
# root, so cargo needs the path. A Lua extension has no window of its own, so
# both of these are Rust hosts and both live in examples/lua beside the script
# they run (the panel under features/slots, the bench under tools). lua_panel keeps the `lua_` prefix the file dropped: every example
# binary in the workspace lands in one flat target/debug/examples, so a
# `panel` here would collide with kui-ffi's.
[]
= ["lua_panel"]
[[]]
= "bench"
= "../../examples/lua/tools/bench.rs"
[[]]
= "lua_panel"
= "../../examples/lua/features/slots/panel.rs"
[[]]
= "sizes"
= false