[erlang-questions] Any tools available to generate code for Erlang Ports?

[Michael Truog]

On 01/18/2011 12:49 PM, Tim Watson wrote:
> On 18 January 2011 13:54, Dave Challis <dsc@REDACTED> wrote:
>   
>> I'm just curious - are there any tools or code generators out there for
>> creating Erlang Ports to interface with C code?
>>
>> There are a bunch of old C libraries I'd like to be able to use from within
>> Erlang, and it seems pretty time consuming to code interfaces to them from
>> scratch.
>>
>>     
> There's the Erlang Driver Toolkit
> (http://www.snookles.com/erlang/edtk/) which is pretty good but
> documentation is a bit sparse. It looks pretty solid. Another one is
> DryvErl but I've not looked closely at that one. I came across another
> tool on github recently - https://github.com/tonyrog/eapi. This is
> completely undocumented apart from some example code, but looks very
> interesting. Finally, there was a guy on the list some time ago
> mentioning that he'd written some generic C/C++ stuff for generating
> driver code, but I've been unable to fish out the link to his post.
> You might want to try searching github, as there are probably a few
> others out there too.
>   

You might be thinking of GEP[D]
(https://github.com/okeuday/generic-erlang-port--driver-).  GEP[D] does
everything EDTK does except the weird handling of file descriptors, but
the code was written before NIFs, so it does port driver code (with
async support).