nathan-mv / raylib-cruby-extension

Ruby C Extension for Raylib

Instalation

If possible, try the artifacts from the CI instead of compiling. Please give me a heads up if they don't work out of the box: CI Artifacts

Compilation

• Clone Repository

git clone https://github.com/Nathan-MV/raylib-cruby-extension

• Init Submodules

cd raylib-cruby-extension
git submodule update --init --recursive

• Windows
  • Install Ruby 3.3 with Devkit. Then, open PowerShell as Administrator and use the command bellow to set the execution policy, so that you can use ridk.

Set-ExecutionPolicy -ExecutionPolicy Unrestricted

• Ubuntu

sudo apt install cmake ninja-build ruby-devel libasound2-dev libx11-dev libxrandr-dev libxi-dev libgl1-mesa-dev libglu1-mesa-dev libxcursor-dev libxinerama-dev libwayland-dev libxkbcommon-dev

• Fedora

sudo dnf install cmake ninja-build ruby-devel alsa-lib-devel mesa-libGL-devel libX11-devel libXrandr-devel libXi-devel libXcursor-devel libXinerama-devel libatomic wayland-devel libxkbcommon-devel wayland-protocols-devel

• Arch Linux

sudo pacman -S cmake ninja ruby alsa-lib mesa libx11 libxrandr libxi libxcursor libxinerama

• Install Ruby Gems

bundle install --with compile

• Ruby Extension - Windows

ridk exec rake

• Ruby Extension - Linux

rake

• Binary
  • On Windows it require CMake, Ninja, Ruby 3.3 with Devkit, Visual Studio Build Tools with Desktop Development for C++ (And it segfault right after you launch xD)

cmake -B build -G Ninja -DCMAKE_BUILD_TYPE:STRING=Release
cmake --build build --config Release --target all

TODO

• Complete the API
• Investigate Windows Binary Segfault after launch
• Investigate Linux Binary Segfault after closing the window
• Make Windows Binary workflow use MSYS2 env from setup-ruby instead of using setup-msys2
• Ensure CMake Moves Linked Libraries to Build Folder

Contributing

Bug reports and pull requests are welcome on GitHub at https://github.com/Nathan-MV/raylib-cruby-extension. This project is intended to be a safe, welcoming space for collaboration, and contributors are expected to adhere to the code of conduct.

License

The gem is available as open source under the terms of the MIT License.

Code of Conduct

Everyone interacting in the HelloC project's codebases, issue trackers, chat rooms and mailing lists is expected to follow the code of conduct.