search

Tieske / luawinmulti

Lua build and installation script for Windows, building multiple Lua versions in parallel, including LuaRocks.
Other
57 stars 5 forks source link

switch to LuaRocks 3 #27

Open Tieske opened 3 months ago

Tieske commented 3 months ago

fixes #15

Tieske commented 3 months ago

@hishamhm mind having a look?

It uses the same approach; 1 luarocks, in an enviornment with 4 lua versions (5.1 - 5.4). The enviornment is set up based on a specific compiler configuration.

To make it work, I had to copy out "hardcoded.lua", and make it versioned. In the new Luarocks wrapper batch file, the Lua version is set, the matching version of hardcoded.lua is set, and the tree is forced to "system" to keep it self contained.

hishamhm commented 3 months ago

To make it work, I had to copy out "hardcoded.lua", and make it versioned. In the new Luarocks wrapper batch file, the Lua version is set, the matching version of hardcoded.lua is set, and the tree is forced to "system" to keep it self contained.

If you are making wrapper batch files, it should be possible to set --lua-dir and --lua-version in them, and simply delete hardcoded.lua. If you need to set anything more specific such as LUA_BINDIR, you can set LUAROCKS_CONFIG in the wrapper batch file, and then set any other LuaRocks variables in the config file this variable points to.

The hardcoded.lua file exists only to simplify installations where the installer wants to set some settings in stone. If it is causing you trouble and forcing you to turn it into "soft-coding", then you should just delete it (LuaRocks requires with pcall, so it runs fine without it).