On Wed, Feb 26, 2014 at 05:18:10PM -0300, Hisham wrote: > On 26 February 2014 15:53, Peter Colberg <[email protected]> wrote: > > * The source rock uses gcc and the gcc-lua plugin to compile the headers > > of a library into pure C source code that the FFI module can digest. > > gcc-lua essentially does an API to ABI translation. The result of > > this translation is generally architecture-dependent. > > > > I can make “luarocks pack” include the architecture by installing the > > arch-dependent C.lua to $(LIBDIR) instead of $(LUADIR). Could this > > use case be supported by adding $(LIBDIR) to the LUA_PATH that is > > shown by “luarocks path”? > > I'm not sure I follow... What's the goal here, to have the .rock file > get an arch-dependent name?
The goal is to install arch-dependent files in an arch-dependent path. Currently $(LIBDIR) is intended for binary modules. Could this be extended to arch-dependent source modules? The only implication for luarocks is that "luarocks path --lr-path" includes both the */share/lua/… and the */lib/lua/… directories. Many distributions already include both types of paths in LUA_PATH: # cat /etc/redhat-release Red Hat Enterprise Linux Workstation release 6.5 (Santiago) # /usr/bin/lua -e 'print(package.path)' ./?.lua;/usr/share/lua/5.1/?.lua;/usr/share/lua/5.1/?/init.lua;/usr/lib64/lua/5.1/?.lua;/usr/lib64/lua/5.1/?/init.lua Thanks, Peter ------------------------------------------------------------------------------ Flow-based real-time traffic analytics software. Cisco certified tool. Monitor traffic, SLAs, QoS, Medianet, WAAS etc. with NetFlow Analyzer Customize your own dashboards, set traffic alerts and generate reports. Network behavioral analysis & security monitoring. All-in-one tool. http://pubads.g.doubleclick.net/gampad/clk?id=126839071&iu=/4140/ostg.clktrk _______________________________________________ Luarocks-developers mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/luarocks-developers
