configure sm

game/game_logic/Cargo.toml

@@ -5,7 +5,6 @@ version = "0.1.0"
 edition = "2021"
 
 # See more keys and their definitions at https://doc.rust-lang.org/cargo/reference/manifest.html
-
 [dependencies]
-raylib = {version="3.5", path="../../third_party/raylib-rs/raylib"}
-# raylib = { version = "3.5", git = "https://github.com/ewpratten/raylib-rs", branch = "ludum-dare-50" }
+raylib = { version = "3.7", path = "../../third_party/raylib-rs/raylib" }
+sad_machine = { version = "1.0", path = "../../third_party/sm" }

third_party/README.md

@@ -0,0 +1,11 @@
+# Third Party Dependencies
+
+Since we evolve so fast during game jams, it is sometimes impractical to deal with the pull-request/review process of our dependencies.
+
+We also have a habit of breaking well-known Rust crates during these weekends, so it has just become more practical to build our game in a bit of a monorepo using custom forks of dependencies.
+
+## Should I add my dependency as a submodule
+
+Probably not.
+
+But, if you have found a critical bug in something (like raylib), and cannot get it merged upstream, just fork the repo, add it here with `git submodule add <repo>` and use it.

third_party/raylib-rs

@@ -1 +1 @@
-Subproject commit 9320e27aae0abc95a39d74d0221821f8164e5c21
+Subproject commit 67775a41ab64aae22951455fdd45147b9cbb749a

third_party/sm

@@ -1 +1 @@
-Subproject commit 749d4df59f095327bad5836ca5594e98b3686481
+Subproject commit 2620c833d4ac0f5f2af57d9ff2a9c20d38606e8a