search

arrayfire / arrayfire-lisp

Lisp bindings for ArrayFire
BSD 3-Clause "New" or "Revised" License
2 stars 3 forks source link

started down the path of the autowrap #2

Closed serialhex closed 7 years ago

serialhex commented 7 years ago

Again, this is just how I would start this, so it's not a commitment, just a suggestion.

Also, I havn't even tried to load the code yet, so it may explode. cl-autowrap needs a functioning version of Clang to make its *.spec files (though it only needs to do that once, users don't need Clang at all) and I don't have that set up on this system (the differences between a Linux & a Windows are striking, and annoying). I'll probably try it at home & start refining there, but idk how much time I'll have.

pavanky commented 7 years ago

@serialhex FYI your commits are not being linked to your github account, I am not sure if you mind that :)

Also is this PR a work in progress or is it OK to be merged?

serialhex commented 7 years ago

At first I was confused that my commit wasn't being linked to my GitHub... But now I see what happened! I don't have all my GitHub info on my work PC, so it's registering it as real me, and not internet me :stuck_out_tongue:

It is kind of a work in progress, it really depends on the direction you want to go in. There are a couple of different options, and this is probably the easiest & quickest, though again, I don't have much experience in building FFIs to libraries (I've only done it once, with SDL2-image, and started with nuklear but that's on hold).

If you haven't noticed I set up a Gitter so we can near-realtime chat about options. I have small snippits throughout the day, and it might be easier when you have time to talk that way.