Skip to content

Update README.md: Mention ninja-build is required #172

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

Closed
wants to merge 1 commit into from
Closed

Update README.md: Mention ninja-build is required #172

wants to merge 1 commit into from

Conversation

jestarray
Copy link
Contributor

closes #165

@jestarray
Copy link
Contributor Author

as said in #165 , I think its better if we remove ninja as a build generator in general? Advanced users will have custom bindings anyways but for people who just want to dip their toes into raylib-rs, it is annoying. If so, reject this PR

@IoIxD
Copy link
Contributor

IoIxD commented Jan 31, 2024

Hi, if you're still interested in working on this, some users of the library are moving over to a fork of it which aims to be actively maintained. It would be nice if you reopened the PR there!

@jestarray jestarray closed this May 26, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Mention the requirement of ninja-build as a dependency
2 participants