This tool allows you to generate .NET bindings that wrap C/C++ code allowing interoperability with managed languages. This can be useful if you have an existing native codebase and want to add scripting support, or want to consume an existing native library in your managed code.
This tool allows you to generate .NET bindings that wrap C/C++ code allowing interoperability with managed languages. This can be useful if you have an existing native codebase and want to add scripting support, or want to consume an existing native library in your managed code.
## Getting started
Since binary releases have not been provided yet, you will have to compile the project and dependencies manually (LLVM and Clang).
The documentation is still a work-in-progress, please see the following resources for more information:
[Getting Started](docs/GettingStarted.md)
[User's Manual](docs/UsersManual.md)
[Developer's Manual](docs/DevManual.md)
## Why reinvent the wheel?
## Why reinvent the wheel?
There are not many automated binding tools around, the only real alternative is SWIG. So how is it different from SWIG?
There are not many automated binding tools around, the only real alternative is SWIG. So how is it different from SWIG?
@ -21,18 +33,6 @@ It is being used to bind "real-world" complex codebases successfully, so give it
Since C and C++ provide such a wide array of features I'm sure there's still tonnes of bugs and unsupported edge cases, but give and try and report any bugs you find and I'll try to fix them ASAP.
Since C and C++ provide such a wide array of features I'm sure there's still tonnes of bugs and unsupported edge cases, but give and try and report any bugs you find and I'll try to fix them ASAP.
## Getting started
Since binary releases have not been provided yet, you will have to compile the project and dependencies manually (LLVM and Clang).
The documentation is still a work-in-progress, please see the following resources for more information: