pub struct KeyboardTomlConfig { /* private fields */ }Expand description
Configurations for RMK keyboard.
Implementations§
Source§impl KeyboardTomlConfig
impl KeyboardTomlConfig
Sourcepub fn build_constants(
&self,
active_features: &[&str],
) -> Result<BuildConstants, String>
pub fn build_constants( &self, active_features: &[&str], ) -> Result<BuildConstants, String>
Build compile-time constants from the configuration.
active_features contains feature names enabled on the
downstream crate (e.g. ["split", "_ble"]). These are matched
against subscriber_default.toml to auto-bump event subscriber counts.
Source§impl KeyboardTomlConfig
impl KeyboardTomlConfig
Sourcepub fn new_from_toml_path_with_event_defaults<P: AsRef<Path>>(
config_toml_path: P,
) -> Self
pub fn new_from_toml_path_with_event_defaults<P: AsRef<Path>>( config_toml_path: P, ) -> Self
Load keyboard.toml with event defaults only.
This is used in build.rs where we only need [rmk] and [event] constants,
and should not require [keyboard.board]/[keyboard.chip].
pub fn new_from_toml_path<P: AsRef<Path>>(config_toml_path: P) -> Self
Sourcepub fn dfu_storage_conflict(&self) -> Option<DfuStorageConflict>
pub fn dfu_storage_conflict(&self) -> Option<DfuStorageConflict>
Detect a [storage]/[dfu] conflict in the user’s keyboard.toml.
While DFU is enabled, the storage region is a partition fixed by the
bootloader’s linker script (rmk-memory.x, generated by rmk-boot’s
build.rs): start_addr is overridden to the partition start and
num_sectors must match the partition size. Explicit [storage]
values have no effect there, so return which keys the user set.
Trait Implementations§
Source§impl Clone for KeyboardTomlConfig
impl Clone for KeyboardTomlConfig
Source§fn clone(&self) -> KeyboardTomlConfig
fn clone(&self) -> KeyboardTomlConfig
1.0.0 (const: unstable) · Source§fn clone_from(&mut self, source: &Self)
fn clone_from(&mut self, source: &Self)
source. Read more