#x_pwork #rust #gamedev #macroquad #miniquad #comfy #ggez #gwg #bevy #wgpu
TASK: rust light game development 2d, 3d
sub-tasks
- offline installation
- rust working offline
- ability to adjust and edit all manually
- development on win (for now, goal Linux)
- lightweight on system and disk space
- portable environment
- development on low end pc
- convenient and easy to use modules
- deploy to low end hardware
- deploy os win XP>, web, linx, android 4>
- learn modules and rust
- share info
and a lot of mini tasks
...Continue from failed Comfy build
On online machine winX64dx12
installed rust by rustup toolchain stable x86_64-pc-windows-gnu
failed build gcc
installed msys64
- COMPLETED build but
- run app FAIL on offline and online machines
app window appears too wide and then exits
seems wgpu version requires opengl3
.
MACROQUAD
some research in Comfy lead to use of macroquad
After code edit
- COMPLETED !!! build and
- app run WORK on online machine and on offline.
Going for now with MACROQUAD and GGEZ,GWG,BEVY but still interested to build Comfy.
-- Bevy build COMPLETED but
- don't run FAILS on online machine,
- run WORK on offline, but barely example("alien cake obsession" not playable at all)
-- GGEZ build COMPLETED, but
- run FAILS on online machine (wgpu out of memory)
App show window with title and dies
(write buffer, device lost, winit errors)
- runs WORK on offline
(don't forget to copy resource folder to app executable and test --example 02_hello_world (shadow and super_simple failed sometimes)
-- GWG build COMPLETED !!!! (after some work)
- run WORK on online and offline machine
Back On offline machine winX64dx12 toolchain i686-pc-windows-gnu
Transfered vendored
----MACROQUAD project
- FAILED build
errors in miniquad
after some work
made copy of minuquad crate
edited errors by Cargos suggestions
add miniquad_ed as patch of miniquad
- COMPLETE build but
- App run FAILS on start on offline and online PC
---- GGEZ
- FAILED build gcc linker
after work
manually copied from online pc folder of msys64
and add e:/msys64/mingw64/bin to Enviroment Vars PATH
- FAILED to build
tool ld.exe fails
from toolchain i686-pc-windows-gnu
Thought it's might be problem with 32bit tool executable on x64 OS
Don't have rustup on machine so
Haven't found way to add new toolchain
(need to check configurations more)
just to copy toolchain x86_64-pc-windows-gnu
from online pc to toolchain folder of offline pc
don't work
haven't found where to initialize new toolchain
made backup of i686-pc-windows-gnu
and modified replaced in folder "self container" binaries with binaries from
msys64/mingw64 x86_64-pc-windows-gnu
copied from there all binaries
copied folder ldscript
then run Cargo with ggez example
cargo run --example 01_super_simple --target i686-pc-windows-gnu
- COMPLETED build but
- app run WORK offline pc
- app run FAILS on online pc
App starts window appeared and exited
---- GWG (good web games)
- COMPLETED build to win target BUT
at first app show blank window and died
- run WORK on offline PC
- run FAILS on online PC
gwg-bindgen example for wasm build for win target
- COMPLETED build,
- app run WORK-LIMITED
App starts screen filled with one color
terminal prints on keyboard input.
Code change of fill color works, but drawing anything else makes App Fail.
----- BEVY
- COMPLETED build
- app run WORK on offline PC
- app run FAIL on online PC
-so for THIS MOMENT
Online PC can
BUILD: macroquad, gwg, ggez, bevy(all run on offline pc).
RUN: macroquad executable, GWG,
Offline PC can
BUILD: macroquad(don't run on offline and onli pc), gwg, ggez(run only on offline pc), bevy(run on offline, fail on online)
RUN: macroquad executable, GWG, GGEZ, BEVY
NEED MORE RESEARCH and tests