Leo`s Raylib-Quickstart fork

A simple template for setting up a project with raylib code using C++ , VisualStudio2022 and Windows.

This fork

This fork simplifies Raylib-Quickstart by removing features and making it strict to:

• Visual Studio 2022
• C++
• Windows (Dev environment)

Using this template you can start a new C++ project in just two clicks.

• Run build-VisualStudio2022.bat
• Run the .sln file that was generated
• you are good to go ! 😎😎😎😎😎😎😎😎😎😎

Using this template

Rename this folder before generating the .sln file, as the project will be named after it.
Change the icon ./resources/icon.png and the player ./resources/wabbit_alpha.png.
Duplicate, rename, and change the class ./src/MyClass .h .cpp
Edit the Main function at ./src/main.cpp with your game./

Ship your game

After opening Visual Studio and running the code as release, you will find the EXE at /bin.
To share your game, copy that EXE and the ./resources folder to the same place, and ship it!.\

It should look like this:

FolderWithYourGame
├── resources/ # Assets folder (contains images, sounds, etc.)
│ └── icon.png
└── YourGame.exe

Dangerous files from the internet

I would never open an EXE that a stranger sent me from the internet, so why would you?! This project is created using premake5.exe.
It came from https://github.com/raylib-extras/raylib-quickstart , but you can also download it here: https://premake.github.io/download/

License

Copyright (c) 2020-2024 Jeffery Myers

This software is provided "as-is", without any express or implied warranty. In no event will the authors be held liable for any damages arising from the use of this software.

Permission is granted to anyone to use this software for any purpose, including commercial applications, and to alter it and redistribute it freely, subject to the following restrictions:

1. The origin of this software must not be misrepresented; you must not claim that you wrote the original software. If you use this software in a product, an acknowledgment in the product documentation would be appreciated but is not required.

2. Altered source versions must be plainly marked as such, and must not be misrepresented as being the original software.

3. This notice may not be removed or altered from any source distribution.