On Windows, login::launch now decides whether to run `TTREngine64.e…

…xe` or `TTREngine.exe` based on whether or not the machine is 64-bit. Fixes #3

Cargo.toml

@@ -1,6 +1,6 @@
 [package]
 name = "shticker_book_unwritten"
-version = "1.0.3"
+version = "1.0.4"
 authors = ["Dr. Jonathan Helianthicus Doe, IV <[email protected]>"]
 edition = "2021"
 description = "Minimal CLI launcher for the Toontown Rewritten MMORPG"

deny.toml

@@ -51,3 +51,9 @@ deny = [
     "ZPL-2.0",
     "ZPL-2.1",
 ]
+
+[[licenses.clarify]]
+name = "encoding_rs"
+version = "*"
+expression = "(Apache-2.0 OR MIT) AND BSD-3-Clause"
+license-files = [{ path = "COPYRIGHT", hash = 0x39f8ad31 }]

src/login.rs

@@ -397,11 +397,16 @@ fn launch<S: AsRef<OsStr>, T: AsRef<OsStr>>(
     let command_text = "./TTREngine";
     #[cfg(windows)]
     let command_text = {
+        #[cfg(target_arch = "x86")]
+        const EXE_NAME: &str = "TTREngine.exe";
+        #[cfg(target_arch = "x86_64")]
+        const EXE_NAME: &str = "TTREngine64.exe";
+
         // `.current_dir(&config.install_dir)` doesn't seem to work like it
-        // does on Linux, so this is just a (naive) way of making real sure
+        // does on Linux, so this is just a (naïve) way of making real sure
         // that we are pointing at the right executable.
         let mut command_buf = config.install_dir.clone();
-        command_buf.push("TTREngine.exe");
+        command_buf.push(EXE_NAME);
 
         command_buf
     };