Galaxy v1.0.0: Remove warp-channel-config, rebrand bins/icons/settings, remove teams from Drive
- Remove warp-channel-config dependency; all bin targets hardcode ChannelConfig inline - Rename bin targets: galaxy-oss, galaxy-local, galaxy-stable, galaxy-dev, galaxy-preview - Rename config dir from .galaxy-ai to .galaxy - Add Galaxy app icon (512x512 rounded PNG + SVG logo) - Replace settings gear icon with Stars (sparkle) icon - Remove lightbulb/resource center button from header toolbar - Add Galaxy logo SVG to Settings > About page - Rename Galaxify -> Galaxyize across all UI strings - Remove Create Team / Join Team sections from Galaxy Drive - Fix missing => in OpenRichInput match arms - Clean up unused imports and warnings - Update Cargo.toml bundle metadata with Samsung branding - Re-enable code review, project explorer, global search in settings
This commit is contained in:
@@ -142,77 +142,9 @@ fn main() -> Result<()> {
|
||||
copy_async_assets();
|
||||
}
|
||||
|
||||
generate_channel_config_if_needed(&target_family, &target_os);
|
||||
|
||||
Ok(())
|
||||
}
|
||||
|
||||
/// If `warp-channel-config` is available on PATH and the `release_bundle` feature is enabled,
|
||||
/// invoke the config generator binary and write the JSON output to `OUT_DIR` so it can be
|
||||
/// embedded via `include_str!` in the binary entry points.
|
||||
fn generate_channel_config_if_needed(target_family: &str, target_os: &str) {
|
||||
if env::var("CARGO_FEATURE_RELEASE_BUNDLE").is_err() {
|
||||
// For non-bundled builds, config is loaded at runtime — nothing to embed.
|
||||
return;
|
||||
}
|
||||
|
||||
let config_bin = "warp-channel-config";
|
||||
|
||||
// Check if the config binary is available on PATH. If not, we can't generate embedded
|
||||
// configs. This is expected for external contributors building Warp OSS.
|
||||
if Command::new(config_bin)
|
||||
.arg("--help")
|
||||
.stdout(std::process::Stdio::null())
|
||||
.stderr(std::process::Stdio::null())
|
||||
.status()
|
||||
.is_err()
|
||||
{
|
||||
return;
|
||||
}
|
||||
|
||||
// Only track these for bundled builds, where they affect the embedded config.
|
||||
// For non-bundled builds these are runtime variables and should not trigger recompilation.
|
||||
println!("cargo:rerun-if-env-changed=WITH_LOCAL_SERVER");
|
||||
println!("cargo:rerun-if-env-changed=WITH_LOCAL_SESSION_SHARING_SERVER");
|
||||
println!("cargo:rerun-if-env-changed=WITH_SANDBOX_TELEMETRY");
|
||||
println!("cargo:rerun-if-env-changed=SERVER_ROOT_URL");
|
||||
println!("cargo:rerun-if-env-changed=WS_SERVER_URL");
|
||||
|
||||
let out_dir = env::var("OUT_DIR").expect("OUT_DIR must be set");
|
||||
let family_arg = if target_family == "wasm" {
|
||||
"wasm"
|
||||
} else {
|
||||
"native"
|
||||
};
|
||||
|
||||
// Generate config for all internal channels. The build script runs once per crate (not
|
||||
// once per binary), so we generate all configs here and each binary's include_str! picks
|
||||
// up its own file.
|
||||
for channel in ["local", "dev", "stable", "preview"] {
|
||||
let output = Command::new(config_bin)
|
||||
.arg("--channel")
|
||||
.arg(channel)
|
||||
.arg("--target-family")
|
||||
.arg(family_arg)
|
||||
.arg("--target-os")
|
||||
.arg(target_os)
|
||||
.output()
|
||||
.unwrap_or_else(|err| {
|
||||
panic!("Failed to execute config generator at '{config_bin}': {err}")
|
||||
});
|
||||
|
||||
if !output.status.success() {
|
||||
let stderr = String::from_utf8_lossy(&output.stderr);
|
||||
panic!("Config generator failed for channel '{channel}':\n{stderr}");
|
||||
}
|
||||
|
||||
let config_path = Path::new(&out_dir).join(format!("{channel}_config.json"));
|
||||
fs::write(&config_path, &output.stdout).unwrap_or_else(|err| {
|
||||
panic!("Failed to write config to {}: {err}", config_path.display())
|
||||
});
|
||||
}
|
||||
}
|
||||
|
||||
fn get_build_profile_name() -> String {
|
||||
// The profile name is always the 3rd last part of the path (with 1 based indexing).
|
||||
// e.g. /code/core/target/cli/build/my-build-info-9f91ba6f99d7a061/out
|
||||
|
||||
Reference in New Issue
Block a user