2022-10-01 16:58:22 +00:00
|
|
|
[package]
|
|
|
|
|
name = "gupax"
|
|
|
|
|
version = "0.1.0"
|
|
|
|
|
edition = "2021"
|
|
|
|
|
|
|
|
|
|
[dependencies]
|
2022-10-25 02:58:42 +00:00
|
|
|
anyhow = "1.0.65"
|
|
|
|
|
arti-client = "0.7.0"
|
|
|
|
|
arti-hyper = "0.7.0"
|
|
|
|
|
bytes = "1.2.1"
|
2022-10-13 12:57:50 +00:00
|
|
|
chrono = "0.4.22"
|
2022-10-25 02:58:42 +00:00
|
|
|
dirs = "4.0.0"
|
update: save [Version] to state, use runtime [og: State]
[og: State] is now completely wrapped in an [Arc<Mutex>] so that
when the update is done, it can [.lock()] the CURRENT runtime
settings of the user and save to [gupax.toml] instead of using an
old copy that was given to it at the beginning of the thread.
In practice, this means users can change settings around during
an update and the update finishing and saving to disk won't be
using their old settings, but the current ones. Wrapping all of
[og: State] within in [Arc<Mutex>] might be overkill compared to
message channels but [State] really is just a few [bool]'s, [u*],
and small [String]'s, so it's not much data.
To bypass a deadlock when comparing [og == state] every frame,
[og]'s struct fields get cloned every frame into separate
variables, then it gets compared. This is also pretty stupid, but
again, the data being cloned is so tiny that it doesn't seem to
slow anything down.
2022-11-02 17:58:44 +00:00
|
|
|
#eframe = "0.19.0"
|
|
|
|
|
#egui = "0.19.0"
|
|
|
|
|
#egui_extras = { version = "0.19.0", features = ["image"] }
|
2022-10-29 13:13:00 +00:00
|
|
|
## [external/egui/crates/eframe/src/native/run.rs] line 41: [.with_srgb(true)]
|
|
|
|
|
## This line causes a [panic!] inside a Windows VM, from a Linux host.
|
|
|
|
|
## There are many issue threads and PRs to fix it but for now,
|
|
|
|
|
## this is here for convenience sake when I'm testing.
|
|
|
|
|
## The only change is [.with_srgb()] is set to [false].
|
update: save [Version] to state, use runtime [og: State]
[og: State] is now completely wrapped in an [Arc<Mutex>] so that
when the update is done, it can [.lock()] the CURRENT runtime
settings of the user and save to [gupax.toml] instead of using an
old copy that was given to it at the beginning of the thread.
In practice, this means users can change settings around during
an update and the update finishing and saving to disk won't be
using their old settings, but the current ones. Wrapping all of
[og: State] within in [Arc<Mutex>] might be overkill compared to
message channels but [State] really is just a few [bool]'s, [u*],
and small [String]'s, so it's not much data.
To bypass a deadlock when comparing [og == state] every frame,
[og]'s struct fields get cloned every frame into separate
variables, then it gets compared. This is also pretty stupid, but
again, the data being cloned is so tiny that it doesn't seem to
slow anything down.
2022-11-02 17:58:44 +00:00
|
|
|
eframe = { path = "external/egui/crates/eframe" }
|
|
|
|
|
egui = { path = "external/egui/crates/egui" }
|
|
|
|
|
egui_extras = { path = "external/egui/crates/egui_extras", features = ["image"] }
|
2022-10-13 12:57:50 +00:00
|
|
|
env_logger = "0.9.1"
|
2022-10-18 19:26:21 +00:00
|
|
|
figment = { version = "0.10.8", features = ["toml"] }
|
2022-10-25 02:58:42 +00:00
|
|
|
flate2 = "1.0"
|
2022-10-13 12:57:50 +00:00
|
|
|
hex-literal = "0.3.4"
|
2022-10-25 02:58:42 +00:00
|
|
|
hyper = "0.14.20"
|
|
|
|
|
hyper-tls = "0.5.0"
|
2022-10-01 16:58:22 +00:00
|
|
|
image = { version = "0.24.4", features = ["png"] }
|
2022-10-13 12:57:50 +00:00
|
|
|
log = "0.4.17"
|
2022-10-01 16:58:22 +00:00
|
|
|
monero = "0.18.0"
|
2022-10-13 12:57:50 +00:00
|
|
|
num_cpus = "1.13.1"
|
2022-10-14 21:13:38 +00:00
|
|
|
num-format = "0.4.0"
|
2022-10-29 13:13:00 +00:00
|
|
|
#openssl = { version = "*", features = ["vendored"] }
|
2022-10-15 15:24:02 +00:00
|
|
|
rand = "0.8.5"
|
2022-10-01 16:58:22 +00:00
|
|
|
regex = "1.6.0"
|
2022-10-14 21:13:38 +00:00
|
|
|
reqwest = { version = "0.11.12", features = ["blocking", "json"] }
|
2022-10-29 13:13:00 +00:00
|
|
|
rusqlite = { version = "0.28.0", features = ["bundled"] }
|
update: save [Version] to state, use runtime [og: State]
[og: State] is now completely wrapped in an [Arc<Mutex>] so that
when the update is done, it can [.lock()] the CURRENT runtime
settings of the user and save to [gupax.toml] instead of using an
old copy that was given to it at the beginning of the thread.
In practice, this means users can change settings around during
an update and the update finishing and saving to disk won't be
using their old settings, but the current ones. Wrapping all of
[og: State] within in [Arc<Mutex>] might be overkill compared to
message channels but [State] really is just a few [bool]'s, [u*],
and small [String]'s, so it's not much data.
To bypass a deadlock when comparing [og == state] every frame,
[og]'s struct fields get cloned every frame into separate
variables, then it gets compared. This is also pretty stupid, but
again, the data being cloned is so tiny that it doesn't seem to
slow anything down.
2022-11-02 17:58:44 +00:00
|
|
|
serde = { version = "1.0.145", features = ["rc", "derive"] }
|
2022-10-25 02:58:42 +00:00
|
|
|
serde_json = "1.0"
|
2022-10-13 12:57:50 +00:00
|
|
|
sha2 = "0.10.6"
|
2022-10-25 02:58:42 +00:00
|
|
|
tls-api = "0.9.0"
|
|
|
|
|
tls-api-native-tls = "0.9.0"
|
|
|
|
|
tokio = { version = "1.21.2", features = ["full"] }
|
2022-10-13 12:57:50 +00:00
|
|
|
toml = "0.5.9"
|
2022-10-25 02:58:42 +00:00
|
|
|
tor-rtcompat = "0.7.0"
|
|
|
|
|
walkdir = "2.3.2"
|
update: save [Version] to state, use runtime [og: State]
[og: State] is now completely wrapped in an [Arc<Mutex>] so that
when the update is done, it can [.lock()] the CURRENT runtime
settings of the user and save to [gupax.toml] instead of using an
old copy that was given to it at the beginning of the thread.
In practice, this means users can change settings around during
an update and the update finishing and saving to disk won't be
using their old settings, but the current ones. Wrapping all of
[og: State] within in [Arc<Mutex>] might be overkill compared to
message channels but [State] really is just a few [bool]'s, [u*],
and small [String]'s, so it's not much data.
To bypass a deadlock when comparing [og == state] every frame,
[og]'s struct fields get cloned every frame into separate
variables, then it gets compared. This is also pretty stupid, but
again, the data being cloned is so tiny that it doesn't seem to
slow anything down.
2022-11-02 17:58:44 +00:00
|
|
|
|
|
|
|
|
# Unix dependencies
|
|
|
|
|
[target.'cfg(unix)'.dependencies]
|
|
|
|
|
tar = "0.4.38"
|
|
|
|
|
|
|
|
|
|
# Windows dependencies
|
|
|
|
|
[target.'cfg(windows)'.dependencies]
|
2022-10-31 20:08:25 +00:00
|
|
|
zip = "0.6.3"
|
2022-10-01 16:58:22 +00:00
|
|
|
|
update: save [Version] to state, use runtime [og: State]
[og: State] is now completely wrapped in an [Arc<Mutex>] so that
when the update is done, it can [.lock()] the CURRENT runtime
settings of the user and save to [gupax.toml] instead of using an
old copy that was given to it at the beginning of the thread.
In practice, this means users can change settings around during
an update and the update finishing and saving to disk won't be
using their old settings, but the current ones. Wrapping all of
[og: State] within in [Arc<Mutex>] might be overkill compared to
message channels but [State] really is just a few [bool]'s, [u*],
and small [String]'s, so it's not much data.
To bypass a deadlock when comparing [og == state] every frame,
[og]'s struct fields get cloned every frame into separate
variables, then it gets compared. This is also pretty stupid, but
again, the data being cloned is so tiny that it doesn't seem to
slow anything down.
2022-11-02 17:58:44 +00:00
|
|
|
# For Windows build (icon)
|
2022-10-31 20:08:25 +00:00
|
|
|
[target.'cfg(windows)'.build-dependencies]
|
|
|
|
|
winres = "0.1.12"
|
2022-10-01 16:58:22 +00:00
|
|
|
|
update: save [Version] to state, use runtime [og: State]
[og: State] is now completely wrapped in an [Arc<Mutex>] so that
when the update is done, it can [.lock()] the CURRENT runtime
settings of the user and save to [gupax.toml] instead of using an
old copy that was given to it at the beginning of the thread.
In practice, this means users can change settings around during
an update and the update finishing and saving to disk won't be
using their old settings, but the current ones. Wrapping all of
[og: State] within in [Arc<Mutex>] might be overkill compared to
message channels but [State] really is just a few [bool]'s, [u*],
and small [String]'s, so it's not much data.
To bypass a deadlock when comparing [og == state] every frame,
[og]'s struct fields get cloned every frame into separate
variables, then it gets compared. This is also pretty stupid, but
again, the data being cloned is so tiny that it doesn't seem to
slow anything down.
2022-11-02 17:58:44 +00:00
|
|
|
# For macOS build (cargo-bundle)
|
2022-10-31 20:08:25 +00:00
|
|
|
[package.metadata.bundle]
|
|
|
|
|
identifier = "io.github.hinto-janaiyo.gupax"
|
|
|
|
|
icon = ["images/png/icon@2x.png"]
|
|
|
|
|
short_description = "GUI for P2Pool+XMRig"
|
