-
Notifications
You must be signed in to change notification settings - Fork 124
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
4.5.0 #139
4.5.0 #139
Conversation
Fix enum member redefinition error
… might not be safe
4.5.0 is now released |
@deltaphc could you take a look at the PR, please? I think it's worth merging as soon as possible. |
cc @Dacode45 |
@litten2up Thanks for the hard working on porting to 4.5.0! Do you think is ready do go? do you need some help testing out the modules? |
I've given a try to shaders, blend modes et other stuff (like ffi::rlSetBlendFactorsSeparate) on Windows. So far so good. Right now I'm using bitten2up's branch. |
im aware things like the examples/tests are broken and some most renamed functions have the same name for compatibility reasons |
This seems to also be done already in 4.6.0 bindings but we should do it for this branch also. This fixes issues with people not having `ninja` in their PATH on windows and linux, which has been cropping up causing unnecessary friction and may deter people from trying raylib-rs when things don't just work out of box. ``` CMake Error: CMake was unable to find a build program corresponding to "Ninja". CMAKE_MAKE_PROGRAM is not set. You probably need to select a different build tool. ``` https://discord.com/channels/426912293134270465/540620507708522517/1138805729541763082 I tested removing it and it builds fine.
Update build.rs: Remove ninja build
5.0 is released now, anyone working on this? How can I help? :) |
i have been mostly inactive in raylib due to some issues i was having on linux, but I am more than happy to take help, iirc my 4.6.0 branch was broken, so i would recommend you to base yours on my 4.5.0 branch |
a port of raylib-rs to 4.5 (I'm doing this now so then when new functions are added in raylib It doesn't have to be added at once, also the branch is stale)
edit: put this in the discord but thought it could also go here, to test it you can put this in your cargo.toml file