alacritty/Cargo.toml

[workspace]
members = [
    "alacritty",
    "alacritty_terminal",
    "alacritty_config",
    "alacritty_config_derive",
]
resolver = "2"

[profile.release]
lto = "thin"
debug = 1
incremental = false
Add cargo workspace, add winpty tests to CI 2018-10-19 01:08:45 -04:00			`[workspace]`
			`members = [`
Split alacritty into a separate crates The crate containing the entry point is called alacritty, and the crate containing everything else is called alacritty_terminal. 2019-04-28 09:24:58 -04:00			`"alacritty",`
			`"alacritty_terminal",`
Add IPC config subcommand This patch adds a new mechanism for changing configuration options without editing the configuration file, by sending options to running instances through `alacritty msg`. Each window will load Alacritty's configuration file by default and then accept IPC messages for config updates using the `alacritty msg config` subcommand. By default all windows will be updated, individual windows can be addressed using `alacritty msg config --window-id "$ALACRITTY_WINDOW_ID"`. Each option will replace the config's current value and cannot be reset until Alacritty is restarted or the option is overwritten with a new value. Configuration options are passed in the format `field.subfield=value`, where `value` is interpreted as yaml. Closes #472. 2022-08-31 18:48:38 -04:00			`"alacritty_config",`
Replace serde's derive with custom proc macro This replaces the existing `Deserialize` derive from serde with a `ConfigDeserialize` derive. The goal of this new proc macro is to allow a more error-friendly deserialization for the Alacritty configuration file without having to manage a lot of boilerplate code inside the configuration modules. The first part of the derive macro is for struct deserialization. This takes structs which have `Default` implemented and will only replace fields which can be successfully deserialized. Otherwise the `log` crate is used for printing errors. Since this deserialization takes the default value from the struct instead of the value, it removes the necessity for creating new types just to implement `Default` on them for deserialization. Additionally, the struct deserialization also checks for `Option` values and makes sure that explicitly specifying `none` as text literal is allowed for all options. The other part of the derive macro is responsible for deserializing enums. While only enums with Unit variants are supported, it will automatically implement a deserializer for these enums which accepts any form of capitalization. Since this custom derive prevents us from using serde's attributes on fields, some of the attributes have been reimplemented for `ConfigDeserialize`. These include `#[config(flatten)]`, `#[config(skip)]` and `#[config(alias = "alias)]`. The flatten attribute is currently limited to at most one per struct. Additionally the `#[config(deprecated = "optional message")]` attribute allows easily defining uniform deprecation messages for fields on structs. 2020-12-20 21:44:38 -05:00			`"alacritty_config_derive",`
Add cargo workspace, add winpty tests to CI 2018-10-19 01:08:45 -04:00			`]`
Add resolver to workspace manifest This explicitly specifies resolver "2" in the root manifest, to fix a warning introduced in a recent nightly release. 2023-06-11 14:58:30 -04:00			`resolver = "2"`
Add cargo workspace, add winpty tests to CI 2018-10-19 01:08:45 -04:00
Fix some compiler warnings Also enables debug symbols in release profile by default. Until Alacritty ships, there's going to be lots of perf analysis which needs debug symbols. The PriorityMutex low priority method was never used. Now it's just a fair mutex. 2016-09-23 13:12:11 -04:00			`[profile.release]`
Use `thin` instead of `fat` LTO The performance between `thin` and `fat` is in the margin of error, however `thin` LTO is way faster to build. 2023-03-11 15:16:49 -05:00			`lto = "thin"`
Reduce debug level for release Backtraces are useful, but line-level debuginfo bloats the binary, and has impact on compile times notably. This reduces it to function-level debuginfo which is a good compromise point. 2018-05-30 05:08:35 -04:00			`debug = 1`
Disable incremental for release builds This fixes #1115. 2019-02-05 18:00:14 -05:00			`incremental = false`