-
Notifications
You must be signed in to change notification settings - Fork 39
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
Create a chipmunk cli tool for developers #1966
Labels
new
newly created issue
Comments
This is a great idea! |
sergio-bobillier
added a commit
to sergio-bobillier/chipmunk
that referenced
this issue
Dec 6, 2023
sergio-bobillier
added a commit
to sergio-bobillier/chipmunk
that referenced
this issue
Dec 6, 2023
The BuildConfiguration struct will hold the build configuration loaded from the configuration file. For the moment it just loads the file contents into a string and handles failures.
sergio-bobillier
added a commit
to sergio-bobillier/chipmunk
that referenced
this issue
Dec 11, 2023
The BuildConfiguration struct will hold the build configuration loaded from the configuration file. For the moment it just loads the file contents into a string, parses them as TOML and handles failures.
sergio-bobillier
added a commit
to sergio-bobillier/chipmunk
that referenced
this issue
Jan 5, 2024
sergio-bobillier
added a commit
to sergio-bobillier/chipmunk
that referenced
this issue
Jan 12, 2024
I think this one is already done. Nice to see first issue I worked on again 😀 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
chipmunk has evolved to be more than a product, it's a platform + a specific use case.
we have long used rake for all developer related tasks.
especially building and re-building chipmunk is challenging.
we are a rust + typescript project and do not want to rely on ruby/rake on the developer side.
so we want to create a tool similar to the node-bindgen cli (https://github.com/infinyon/node-bindgen) that takes care of those tasks and replaces rake.
the tool should be implemented as a rust application
The text was updated successfully, but these errors were encountered: