The more current library is the LJIT2Win32 library. I'll be merging that with the LJIT2CNG library. I'll place a MIT or equivalent license on it. you might also be interested in the LAPHLIBS library. It's got stuff in it that I have found to be useful, and has an extremely liberal license. -- William =============================== - Shaping clay is easier than digging it out of the ground. ---------------------------------------- > Date: Sat, 26 Jan 2013 00:36:39 +0900 > Subject: Re: How to create another lua_State in pthread? > From: hnakamur@xxxxxxxxx > To: luajit@xxxxxxxxxxxxx > > Hi, William. > > Thanks for your blog articles. > > I found your BanateCoreWin32 library > https://github.com/Wiladams/BanateCoreWin32 > in your article and wonder under what license it is released. > Could you add the license file? > I hope it will be BSD or MIT license. > > And I found two other Windows API bindings for LuaJIT in > http://wiki.luajit.org/FFI-Bindings > > I hope those three are merged to be a united binding. > Thanks > > 2013/1/25 William Adams <william_a_adams@xxxxxxx>: > > I wrote some on this subject a while back: > > > > http://williamaadams.wordpress.com/?s=lua+threads > > http://williamaadams.wordpress.com/?s=lua+state > > > > Maybe you'll find it useful. > > > > =============================== > > - Shaping clay is easier than digging it out of the ground. > > ---------------------------------------- > >> Date: Fri, 25 Jan 2013 14:39:39 +0100 > >> From: mike-1301@xxxxxxxxxx > >> To: luajit@xxxxxxxxxxxxx > >> Subject: Re: How to create another lua_State in pthread? > >> > >> Hiroaki Nakamura wrote: > >> > Now I am trying to get the callback function defined in another Lua state > >> > and call pthread_create with the callback address. > >> > >> You must cast the Lua function ('hello') to a C function pointer > >> and then to a number in the other state and then convert it back > >> to a function pointer in the main state. > >> > >> Patch attached. > >> > >> --Mike > > > > -- > 中村 弘輝 )Hiroaki Nakamura) hnakamur@xxxxxxxxx >