-
-
Notifications
You must be signed in to change notification settings - Fork 2.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Support custom memory allocators #1074
Comments
Reviewed some raylib allocations in commit bec4677. |
|
|
|
|
|
This issue is related to #966. Supposedly, new raylib module |
NOTE: Two libraries still use custom allocators: glfw and stb_vorbis
I can not do much on my side about it at the moment... so, closing this issue. |
raylib implements
RL_MALLOC
,RL_CALLOC
,RL_REALLOC
andRL_FREE
but some of the external libraries implement their own memory allocators definitions, others none at all.Below table shows allocators used by external libraries used by raylib, all of them should be custom allocators to have full control over raylib programs memory allocation if it was required, for example on embedded devices.
NOTE:
stb_vorbis
andglfw
implement custom allocators mechanism based on functions pointers... but it will be nice to be able to also re-define default allocators.Below table shows allocators used by raylib modules.
Note that all libraries custom allocators should ultimatelly fallback to raylib allocators:
RL_MALLOC
,RL_CALLOC
,RL_REALLOC
,RL_FREE
.The text was updated successfully, but these errors were encountered: