Updated the VSCode Makefile to allow compilation of multiple .c files instead of just one (main.c).
- Replaced `SRC` and `OBJS` definitions to dynamically include all .c and .h files in the project.
- This change enables automatic handling of any number of source files specifically in the VSCode setup.

Changed the raylib version from 4.2.0 to 5.1-dev, just like the raylib.h file

Change vscode config and makefile to add a missing IOKit framework reference and use whichever MacOSX sdk symlink is available

* Remove PLATFORM_RPI

* remove build artifacts

---------

Co-authored-by: MichaelFiber <michael@cubeofb.org>
Co-authored-by: Ray <raysan5@gmail.com>

* Modify remove trailing whitespace

* Fix invalid SetCameraMode call and missing argument to UpdateCamera for VSCode project

Specify root as the starting point for the linux compiler path

NOTE: New raylib release installer uses `w64devkit`, smaller and more updated than regular `mingw64-w64` default project. Paths are updated properly.

* Executable is called game, not main

* Use make not mingw32-make on macOS

* Update year of copyright notices

* Fix mistake in comment

* Fix typo ("algorythms")

* Replace tabs with spaces

* Remove trailing whitespace and fix mistake in comment

* Fix ExportImageAsCode missing comment rectangle corner

* Replace tab with spaces

* Replace tabs with spaces

Now it works on Windows for me but there are lots of hardcoded paths around... I don't like it.

raylib resource data file for Windows platform (containing raylib icon and metadata for executable file) has been renamed to a more consistent name: raylib.rc.data

Also required to work with tcc compiler.

Users will have to specify their personal installation of raylib.

This was causing linker errors on OSX

This requires the user to explicitly specify the path to their raylib folder. We need a better way around this (something like what we do for windows would help).