Ruby FFI bindings for libclang 3.4+.
You cannot select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
 
 
 
Go to file
Samuel Williams f4720a99b9
Bump minor version.
1 day ago
.github Modernize code. 1 day ago
examples Modernize code. 1 day ago
ext Modernize code. 1 day ago
lib/ffi Bump minor version. 1 day ago
spec Modernize code. 1 day ago
.editorconfig Modernize gem. 2 years ago
.gitignore Modernize code. 1 day ago
.mailmap Modernize code. 1 day ago
.rspec Tidy up tests. 9 years ago
.rubocop.yml Modernize code. 1 day ago
bake.rb Add release notes & documentation tooling. 8 months ago
ffi-clang.gemspec Modernize code. 1 day ago
gems.rb Modernize code. 1 day ago
license.md Modernize code. 1 day ago
readme.md Bump minor version. 1 day ago
release.cert Modernize gem. (#58) 3 years ago
releases.md Bump minor version. 1 day ago

readme.md

FFI::Clang

A light-weight wrapper for Ruby exposing libclang. Works for libclang v3.4+.

Development Status

Installation

Add this line to your application's Gemfile:

gem 'ffi-clang'

And then execute:

$ bundle

Or install it yourself as:

$ gem install ffi-clang

Usage

Please see the project documentation for more details.

Library Version

Due to issues figuring out which library to use, we require you to manually specify it. For example, to run the tests, with MacPorts llvm/clang 3.4, use the following:

LLVM_CONFIG=llvm-config-mp-3.4 rake

Releases

Please see the project releases for all releases.

v0.14.0

  • Helper method that returns a curors's FFI::Clang::Cursor#qualified_display_name.

Contributing

We welcome contributions to this project.

  1. Fork it.
  2. Create your feature branch (git checkout -b my-new-feature).
  3. Commit your changes (git commit -am 'Add some feature').
  4. Push to the branch (git push origin my-new-feature).
  5. Create new Pull Request.

Developer Certificate of Origin

In order to protect users of this project, we require all contributors to comply with the Developer Certificate of Origin. This ensures that all contributions are properly licensed and attributed.

Community Guidelines

This project is best served by a collaborative and respectful environment. Treat each other professionally, respect differing viewpoints, and engage constructively. Harassment, discrimination, or harmful behavior is not tolerated. Communicate clearly, listen actively, and support one another. If any issues arise, please inform the project maintainers.