Automatic C-Go Bindings Generator for Go Programming Language
Go
Switch branches/tags
Nothing to show
Clone or download
xlab Merge pull request #52 from mdlayher/master
Comply with expected header for generated Go code
Latest commit 3a95514 Jun 2, 2018

README.md

c-for-go Go Report Card

Automatic C-Go Bindings Generator for Go Programming Language

This project allows to reuse existing C/C++ libraries in your Go applications, by automatically creating c-go bindings for a given set of C headers and the manifest file. We believe in component-based software engineering and think that reusing C/C++ code in Go applications could bring a huge boost to developer's productivity and system's performance. Read more about the motivation: top reasons to use bindings.

Process overview

c-for-go process overview

The only component required to produce a Go package that will wrap the source C/C++ code is the YAML manifest file that defines parsing, translation and generation rules. The manifest can have just a few lines, however in order to match Go's naming conventions and provide enough tips for type conversions it usually contains about 100 lines, which is still better than producing tens of thousands lines of Go code by hand.

The resulting bindings are as low-level as C code, i.e. it would require knowledge of memory management to carefully use the resulting code, however no more C code is needed to make things done. Eventually some functions can be replaced manually with pure-Go analogs. Also usually a high-level wrapper is created by hand, to introduce Object Oriented Design into API, manage inner state and memory, thus making things safe and lifting the mental overhead.

A simple demo case can be seen on the project homepage http://sphere.software/c-for-go.

Full documentation is available at https://github.com/xlab/c-for-go/wiki

Installation

$ go get github.com/xlab/c-for-go

A simple Makefile template.

In action

Sponsors

sphere software sponsor

Credits

License

MIT