watchexec/Cargo.toml

[workspace]
resolver = "2"
members = [
	"crates/lib",
	"crates/cli",
	"crates/events",
	"crates/signals",
	"crates/supervisor",
	"crates/filterer/globset",
	"crates/filterer/ignore",
	"crates/filterer/tagged",
	"crates/bosion",
	"crates/ignore-files",
	"crates/project-origins",
]

[workspace.dependencies]
miette = "5.10.0"
tempfile = "3.8.0"
tracing-test = "0.2.4"
rand = "0.8"
uuid = "1.5.0"

[profile.release]
lto = true
debug = 1 # for stack traces
codegen-units = 1
strip = "symbols"

[profile.dev.build-override]
opt-level = 0
codegen-units = 1024
debug = false
debug-assertions = false
overflow-checks = false
incremental = false

[profile.release.build-override]
opt-level = 0
codegen-units = 1024
debug = false
debug-assertions = false
overflow-checks = false
incremental = false
Split into two crates: lib and cli That has a number of advantages: - #193 the build.rs is only run for the CLI, so the Windows manifest is not embedded in the library anymore, opening it up for downstreams. - it sets the stage for decoupling the version numbers of the CLI and library, to have the library increase its major more often, while the CLI retains compatibility further… that is, to have both follow semver - it removes the CLI-only dependencies from the library - it makes compilation a bit faster as compiling the library and the CLI's other dependencies can happen in parallel One major disadvantage: - installing via cargo changes from watchexec to watchexec-cli. Most installs are from prebuilt and from packages, but that's still a potential stumble. And of course, the CLI APIs in the library are gone (they were already deprecated, though). We also take this opportunity to get rid of the clear_screen code and use our new clearscreen library. #99 #171 #185 2021-04-30 17:27:17 +02:00			`[workspace]`
Opt into resolver=2 2021-10-19 13:47:41 +02:00			`resolver = "2"`
Split into two crates: lib and cli That has a number of advantages: - #193 the build.rs is only run for the CLI, so the Windows manifest is not embedded in the library anymore, opening it up for downstreams. - it sets the stage for decoupling the version numbers of the CLI and library, to have the library increase its major more often, while the CLI retains compatibility further… that is, to have both follow semver - it removes the CLI-only dependencies from the library - it makes compilation a bit faster as compiling the library and the CLI's other dependencies can happen in parallel One major disadvantage: - installing via cargo changes from watchexec to watchexec-cli. Most installs are from prebuilt and from packages, but that's still a potential stumble. And of course, the CLI APIs in the library are gone (they were already deprecated, though). We also take this opportunity to get rid of the clear_screen code and use our new clearscreen library. #99 #171 #185 2021-04-30 17:27:17 +02:00			`members = [`
Split into more crates (#307) 2022-06-15 05:25:05 +02:00			`"crates/lib",`
			`"crates/cli",`
--emit-events-to (#515) 2023-03-18 09:32:24 +01:00			`"crates/events",`
			`"crates/signals",`
Watchexec lib v3 (#601) Co-authored-by: emilHof <95590295+emilHof@users.noreply.github.com> 2023-11-25 21:33:44 +01:00			`"crates/supervisor",`
Split into more crates (#307) 2022-06-15 05:25:05 +02:00			`"crates/filterer/globset",`
			`"crates/filterer/ignore",`
			`"crates/filterer/tagged",`
Add bosion crate: build-time info (#516) 2023-03-05 04:26:23 +01:00			`"crates/bosion",`
Split into more crates (#307) 2022-06-15 05:25:05 +02:00			`"crates/ignore-files",`
			`"crates/project-origins",`
Split into two crates: lib and cli That has a number of advantages: - #193 the build.rs is only run for the CLI, so the Windows manifest is not embedded in the library anymore, opening it up for downstreams. - it sets the stage for decoupling the version numbers of the CLI and library, to have the library increase its major more often, while the CLI retains compatibility further… that is, to have both follow semver - it removes the CLI-only dependencies from the library - it makes compilation a bit faster as compiling the library and the CLI's other dependencies can happen in parallel One major disadvantage: - installing via cargo changes from watchexec to watchexec-cli. Most installs are from prebuilt and from packages, but that's still a potential stumble. And of course, the CLI APIs in the library are gone (they were already deprecated, though). We also take this opportunity to get rid of the clear_screen code and use our new clearscreen library. #99 #171 #185 2021-04-30 17:27:17 +02:00			`]`
Switch to gh actions and clean up metadata and build stuff 2021-04-10 13:53:12 +02:00
Optimise ignore file gathering (#663) Co-authored-by: Félix Saparelli <felix@passcod.name> 2024-01-01 06:01:14 +01:00			`[workspace.dependencies]`
			`miette = "5.10.0"`
			`tempfile = "3.8.0"`
			`tracing-test = "0.2.4"`
			`rand = "0.8"`
			`uuid = "1.5.0"`

Switch to gh actions and clean up metadata and build stuff 2021-04-10 13:53:12 +02:00			`[profile.release]`
Learn some build optimisations from binstall (#416) 2022-09-07 08:00:08 +02:00			`lto = true`
Move profile to where it's effective 2022-01-15 02:34:37 +01:00			`debug = 1 # for stack traces`
Switch to gh actions and clean up metadata and build stuff 2021-04-10 13:53:12 +02:00			`codegen-units = 1`
Learn some build optimisations from binstall (#416) 2022-09-07 08:00:08 +02:00			`strip = "symbols"`

			`[profile.dev.build-override]`
			`opt-level = 0`
			`codegen-units = 1024`
			`debug = false`
			`debug-assertions = false`
			`overflow-checks = false`
			`incremental = false`

			`[profile.release.build-override]`
			`opt-level = 0`
			`codegen-units = 1024`
			`debug = false`
			`debug-assertions = false`
			`overflow-checks = false`
			`incremental = false`