- Don't issue a warning for "mismatched version" since the new bindings
make this irrelevant
- Minor build script refactoring and code cleanup
- Output a `release` version (-X) for libctru env vars
- Revert version to 0.5.0, which is higher than we were using before the
major 22.x version but should be ok since we never released to crates.io
Luckily, Cargo doesn't mind circular dev-dependencies and we can patch
to ensure it's using the same version. We can also leave this as a
`git = "..."` dependency if we want, since it's a dev dependency.
- Added the `bindgen-ctru-sys` to be able to use `ParseCallbacks` when generating the bindings.
- Updated `doxygen-rs` to 0.4, which has a faster engine and more extensible internal (even though there are some regressions).
- Removes the `docstring-to-rustdoc` package because it is no longer needed.
Also simplify version checking logic a bit. It's just a warning, so we
can check for exact version just to be safe and skip the major/minor
comparisons for semver.
Also update the README a bit to explain the versioning scheme.
- Add a helper for local testing with https://github.com/nektos/act
- Don't deny clippy warnings, they can change too easily and break CI
- Add minimum rust version just for completeness' sake
This commit adds support for translating:
- ``retval``
- ``return``
- ``sa``
- ``see``
- ``code``
- ``endcode``
- ``warning``
- ``ref``
- ``note``
- ``name``
There are no remaining tags in `ctru-sys` to translate
This adds a "_bin-dependency_" on ``ctru-sys`` to doxygen-rs, a project I've been roking on to improve Doxygen to Rustdoc conversion: https://github.com/Techie-Pi/doxygen-rs
Right now, only basic things are changed (remove ``@`` annotations, trim spaces, etc.).
In the future, changes will be made (mostly to _truly_ transform ``@param``to rustdoc conventions.
Right now, the documentation is mostly decent, and definitely understandable
All of our 3DS changes have been upstreamed. If in the future we need
to use the fork again, we can edit the top-level Cargo.toml and adjust
the patches (replace upstream with fork).
We don't want duplicate ctru-sys crates in the dependency graph. Same
for libc. We can patch them here to avoid any issues.
Now that we don't have duplicate ctru-sys crates, we can add back the
links field. This field is important because it warns us when there are
two crates linking to the same library (ex. duplicate ctru-sys crates).
Ian Chamberlain