I use it for playing around with some game ideas, really liked the ease of it. Clean, compact API.
Only nuisance is that SUPPORT_BUSY_WAIT_LOOP is defined in the defaults, so I can't use the package from my distribution but have to compile it myself – as I don't want 100% CPU usage when prototyping (where I can happily live with inaccuracies of the timers). I considered opening an issue and forgot about it. But you, Ray, seem to be reading this thread anyway. :-) Thanks, by the way!
Hey, yeah, actually there have been a couple of issues about it... Using a busy wait loop is the only way to keep a quite stable timming measure, depending on OS, clock granularity could be up to 10 ms (despite raylib tries to enable a hi-res clock with granularity of 1ms), it means, some undesired timming issues...
In any case, you can just comment that line in src/config.h (or even uncomment SUPPORT_EVENTS_WAITING) and recompile the lib. raylib has been designed with customization in mind.
raylib is not an engine. It's a quite low level library intended to enjoy coding, probably better small games. You can use for a big project but it lacks lots of required elements that engines have, to name some: Screen Manager, Content Manager, Objects Manager. In any case, you can test it and evaluate if it could fit your needs.
Sorry, no iOS support, it can be ported but I don't have an iOS or a MAC. raylib is plain C and uses OpenGL, lately Apple ecosystem doesn't like those techs.
Please check out codefund.app. We help sustain open source projects through ethical advertising. We have recently been helping more game-related projects such as yours. Disclaimer: I am the founder of CodeFund.
We don’t use cookies. Our code is open source. our ads are relevant to developers. 50-65% of the revenue goes to the publishers (devs). Examples at codesandbox.io, JSBin.com, phaser.io
30 comments
[ 2.8 ms ] story [ 59.3 ms ] threadhttps://github.com/raysan5/raylib/blob/master/games/Makefile
Full API:
https://www.raylib.com/cheatsheet/cheatsheet.html
Is there a list of other bindings somewhere? I didn't see one in my admittedly cursory look.
Only nuisance is that SUPPORT_BUSY_WAIT_LOOP is defined in the defaults, so I can't use the package from my distribution but have to compile it myself – as I don't want 100% CPU usage when prototyping (where I can happily live with inaccuracies of the timers). I considered opening an issue and forgot about it. But you, Ray, seem to be reading this thread anyway. :-) Thanks, by the way!
In any case, you can just comment that line in src/config.h (or even uncomment SUPPORT_EVENTS_WAITING) and recompile the lib. raylib has been designed with customization in mind.
Does this work with Swift and iOS - namely, is embedding this library as a dependency likely to pass Apple's App Store review process?
It does sound far less shady than other places.
I wouldn't call that good enough to make for "ethical" advertising, but I understand you need a handle to hang your brand on.