[Date Prev][Date Next][Thread Prev][Thread Next]
[Date Index]
[Thread Index]
- Subject: AW: Adding module+DLL to Lua for Windows (LfW)
- From: Richter, Jörg <Joerg.Richter@...>
- Date: Thu, 10 Dec 2009 19:00:39 +0100
> The build tool I maintain can use Lua (actually LuaPlus) as part of its
> build. It does so in a directory structure similar to this:
>
> -> jamplus/bin/macosxx64/
> -> jam executable
> -> lua/
> -> luaplus_1100.so
> -> modules/
> -> mymodule.dylib
> The executable dynamically loads the luaplus_1100.so, as it is
> optional. When a Lua script is run that loads mymodule.so, it can't
> open it. The install name path is @executable_path/modules/mymodule.dylib.
I think @loader_path can help you here. If you want to restrict yourself to >=10.4
Jörg
<<winmail.dat>>
- References:
- Adding module+DLL to Lua for Windows (LfW), Doug Rogers
- Re: Adding module+DLL to Lua for Windows (LfW), Doug Rogers
- Re: Adding module+DLL to Lua for Windows (LfW), Jerome Vuarand
- Re: Adding module+DLL to Lua for Windows (LfW), steve donovan
- Re: Adding module+DLL to Lua for Windows (LfW), Mike Pall
- Re: Adding module+DLL to Lua for Windows (LfW), steve donovan
- Re: Adding module+DLL to Lua for Windows (LfW), Joshua Jensen
- RE: Adding module+DLL to Lua for Windows (LfW), Richter, Jörg
- Re: Adding module+DLL to Lua for Windows (LfW), Joshua Jensen