-
-
Notifications
You must be signed in to change notification settings - Fork 10
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
Want to maintain this project? #27
Comments
i do all my dev on windows + vs2022 so the various build/nuget scripts are platform dependent. it shouldn't be hard to get publish/build things working on other platforms, but easiest on windows. |
Out of curiosity, what are you using instead if you don't use raylib-cslo anymore? |
I'm not using anything right now. The reason I'm giving up on raylib is more about driver support: my gpu doens't have proper drivers for OpenGL so suffers stuttering. Additionally, Raylib is great for 2d visualization but pretty mediocre for 3d support. I am interested in building an engine for my long-term tinkering, not really building a game. So these constraints give me pause, as it's a barrier to my hobby planning. I'm eying godot4, to build my engine hobby on top of it. |
Note that angle support has been added recently, so perhaps performance could be more stable through it |
how does one maintain this? |
Problems: I find it pretty annoying that Raylib doesn't build a .DLL with all extras, meaning you need to recreate the native raylib CPP build system just to have the extras. If you want to avoid that step, just don't build the extras (just ship the pre-built raylib libraries w/o them). The bindings can still ship with extras but it would be up to the user to build native if they needed them. |
it doesn't seem that hard indeed, might try to do it |
If you use/love
raylib-cslo
and are interested in helping to maintain the binding, let me know. Raylib-cslo is up to date and working 100%. I just don't really use it anymore so planning ahead, now (when no fires to put out) would be a good opportunity for a new maintainer to step in. It's super easy to update the bindings on new raylib releases. The biggest problems raylib-cslo faces is building native binaries on various platforms when a new version is deployed.. Check the issues for more detail.No rush to do this, just want to plan ahead.
The text was updated successfully, but these errors were encountered: