Tools and libraries to glue C/C++ APIs to high-level languages
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
 
 
 
 
 
Dimitar Dobrev cf58c70d23 Moved all ignored tests for the C# back-end to a temporary test project and enabled them. 12 years ago
build Revert "Remove VS2010 support." 12 years ago
deps Added missing unit testing dependencies. 12 years ago
docs Updated users manual. 12 years ago
examples Remove the SDL tests from the main build. 12 years ago
include Renamed the ICppInstance's 'NativePtr' property to 'Instance'. 12 years ago
patches This patch has been committed in Clang mainline. 13 years ago
src Generated the inlines only when using the C# back-end because the CLI one does not need them. 12 years ago
tests Moved all ignored tests for the C# back-end to a temporary test project and enabled them. 12 years ago
.gitignore Added an ignore rule for Make-based builds which we will have with the upcoming porting work. 12 years ago
LICENSE Update the license information. 12 years ago
README.md Updated the news with a message about the wrapping of inlines. 12 years ago

README.md

CppSharp is a library that 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.

News

  • September 11st 2013 - Added wrapping of inlined functions (thanks to @ddobrev)
  • September 11st 2013 - New binaries available for Windows (VS2012)

Binaries

VS2012 (32-bit): https://dl.dropboxusercontent.com/u/194502/CppSharp/CppSharp_VS2012_116_artifacts.zip

Getting started

The documentation is still a work-in-progress, please see the following resources for more information:

Getting Started

User's Manual

Developer's Manual

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?

  • No need to generate a C layer to interop with C++.
  • Based on an actual C++ parser (Clang) so very accurate.
  • Understands C++ at the ABI (application binary interface) level
  • Easily extensible semantics via user passes
  • Strongly-typed customization APIs
  • Can be used as a library

Can I use it yet?

It is being used to bind "real-world" complex codebases successfully, so give it a shot.

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.

Similiar Tools