Want to maintain this project?

[jasonswearingen]

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.

[jasonswearingen]

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.

[enriko-riba]

Out of curiosity, what are you using instead if you don't use raylib-cslo anymore?
BTW I really love the work you have done so far, great job - would hate to see it die!

[jasonswearingen]

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.

[Peter0x44]

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.

Note that angle support has been added recently, so perhaps performance could be more stable through it

[FormalSnake]

how does one maintain this?

[jasonswearingen]

how does one maintain this?

0. Easiest if you are on Windows and use Visual Studio (can be the free community version)
1. Explore/understand the folders in this repository. I include detailed Readme.MD's everywhere I could think of.
2. Learn the build workflow, described here in detail: https://github.com/NotNotTech/Raylib-CsLo/tree/main/binding-gen

• How to generate the C# bindings,
• build the native raylib DLL,
• publish the nuget package

3. After you can build/publish for the existing raylib version, upgrade to the new version

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.

[FormalSnake]

it doesn't seem that hard indeed, might try to do it