v0.2.0.0
Overview
Since the introduction of pkg-config files in the installed directory of Lua, LuaInstaller became able to integrate nicely in the build process of some important libraries like LGI. However, it brought to light some hidden bugs in that fresh introduced feature. With this release, issues regarding the path of directories stored on such files were addressed.
In the current state, the library is continuously tested by different configurations of two famous libraries (LuaFileSystem and LGI), and also LuaRocks.
Technical discussion of the main changes
- Fixed INSTALL_LMOD and INSTALL_CMOD on installed pkg-config files (.pc) for Lua 5.2.4 and older. On Lua modules that depend on these variables, they should work without LuaRocks being installed from now on;
- INSTALL_LMOD and INSTALL_CMOD on installed pkg-config files (.pc) now holds the full path to the destination directory. When installing Lua through the graphical program (
LuaInstaller.exe) and a relative destination path was given, the pkg-config file stored the path as relative; - On
LuaInstaller.Core, warnings related to WebClient-derived features were solved by coding a new download feature using the recommended HttpClient class. Other minor warnings were also cleaned; - For the users of the library
LuaInstaller.Core, the methodGetLatestVersionwas marked as obsolete. Now,TryGetLatestVersionis the recommended approach; - CI was improved by adding LGI as a build requirement. At the moment of writing, since LGI on Windows depends on INSTALL_LMOD and INSTALL_CMOD of the pkg-config files, it verifies the good behavior of the installed pkg-config files;
- CI was split to span different reusable workflows.