raylib
No description set
- Developed at devel:libraries:c_c++
- Sources inherited from project openSUSE:Factory
-
1
derived packages
- Download package
-
Checkout Package
osc -A https://api.opensuse.org checkout home:seife:Factory/raylib && cd $_
- Create Badge
Refresh
Refresh
Source Files
Filename | Size | Changed |
---|---|---|
raylib-3.0.0-noexamples.patch | 0000000400 400 Bytes | |
raylib-noexamples-3.0.0.tar.gz | 0004390778 4.19 MB | |
raylib.changes | 0000010688 10.4 KB | |
raylib.spec | 0000002574 2.51 KB |
Revision 6 (latest revision is 12)
Dominique Leuenberger (dimstar_suse)
accepted
request 799028
from
Michael Vetter (jubalh)
(revision 6)
- Switch to noexamples tarball as requested in: https://github.com/raysan5/raylib/issues/1180 So we don't ship examples with various licenses that we don't install anyways. - Add raylib-3.0.0-noexamples.patch: dont try to install examples Raysan seems to have forgotten that. - Added missing development header files. - Update to 3.0.0: * All global variables from the multiple raylib modules have been moved to a global context state, it has several benefits, first, better code readability with more comprehensive variables naming and categorization (organized by types, i.e. CORE.Window.display.width, CORE.Input.Keyboard.currentKeyState or RLGL.State.modelview). Second, it allows better memory management to load global context state dynamically when required (not at the moment), making it easy to implement a hot-reloading mechanism if desired. * All memory allocations on raylib and its dependencies now use RL_MALLOC, RL_FREE and similar macros. Now users can easely hook their own memory allocations mechanism if desired, having more control over memory allocated internally by the library. Additionally, it makes it easier to port the library to embedded devices where memory control is critical. For more info check raylib issue #1074. * All I/O file accesses from raylib are being moved to memory data access, now all I/O file access is centralized into just four functions: LoadFileData(), SaveFileData(), LoadFileText(), SaveFileText(). Users can just update those functions to any I/O file system. This change makes it easier to integrate raylib with Virtual File Systems or custom I/O file implementations.
Comments 0