Why is "ext" folder needed?

[sheerun]

Hello! I'm wondering why this gem includes ext folder and requires compilation. I thought FFI bindings don't require compilation? Could you explain it to me, please? It's important to me.

[jvoorhis]

Hi Adam,

ext/ contains some glue code written in C that bridges to some of the
underlying C++ API. The Ruby library interfaces with this support code
using FFI. (FFI relies on C calling conventions and cannot invoke C++
methods directly.)

HTH,

On Sunday, November 16, 2014, Adam Stankiewicz notifications@github.com
wrote:

Hello! I'm wondering why this gem includes ext folder and requires
compilation. I thought FFI bindings don't require compilation? Could you
explain it to me, please? It's important to me.

—
Reply to this email directly or view it on GitHub
#24.

Jeremy Voorhis

[sheerun]

Thank you for the answer. Do you think it be circumvented in some way, without compilation?

[jvoorhis]

The functionality could be removed, or contributed upstream..

On Sunday, November 16, 2014, Adam Stankiewicz notifications@github.com
wrote:

Thank you for the answer. Do you think it be circumvented in some way,
without compilation?

—
Reply to this email directly or view it on GitHub
#24 (comment).

Jeremy Voorhis

[sheerun]

OK, one more question: how this repo relates to ruby-llvm/ruby-llvm?

This one seems not maintained anymore. I thought it's official one.

Could you please update the README and point to official repository?

[jvoorhis]

I can do that. I created the org when I realized there was more interest in
the project than I had bandwidth, and others stepped up to help.

On Monday, November 17, 2014, Adam Stankiewicz notifications@github.com
wrote:

OK, one more question: how this repo relates to ruby-llvm/ruby-llvm?

This one seems not maintained anymore. I thought it's official one.

Could you please update the README and point to official repository?

—
Reply to this email directly or view it on GitHub
#24 (comment).

Jeremy Voorhis