What is luapower?
Luapower is a free and open source module distribution for LuaJIT, Terra and OpenResty and a system for deploying and sharing Lua modules.
Luapower’s goal is to turn LuaJIT into a powerful cross-platform development environment, brick by brick.
What is different about it?
Luapower works on all major desktop systems out-of-the-box. Binaries are included for all platforms, including Linux.
C sources are always included. There’s no such thing as an external dependency and the build toolchain is specified for each platform, so building binaries is no longer a hit-or-miss experience.
The build toolchain contains only easy-to-get open source components (no need to install Visual Studio) and you don’t have to learn a new build system because luapower uses only simple bash scripts to build everything.
Luapower tracks dependencies between modules automatically so you don’t have to write manifest files to describe packages, you don’t have to declare dependencies (except in a few rare cases) or perform any packaging steps, or even move code out of version control, ever.
Modules don’t need to be “installed” out of version control in order to create a proper runtime. You can make changes directly on deployments, and you can push/pull changes between deployments and even create pull requests to upstream without moving files around. There’s no runtime overhead either, as there’s no need for a custom module loader.
How does it do that?
Luapower is a simple idea: it puts luajit and a bunch of modules in separate repositories on github, and it allows you to clone them back together over the same directory (git can do that with the
--git-dir option, which was wrapped in a script for typing comfort). The files in the repos are laid out such that when cloned overlaid like that, the result is a self-contained, runnable luajit installation. Binaries for all platforms are included directly into the repo’s master branch, and
luajit is a shell script which selects the right luajit executable for your platform at runtime, and sets up the environment so that modules and other dependencies are looked for in the luapower directory first, effectively isolating the installation from other libraries that might be present in the host system. C sources and build scripts are in there too in separate directories.
This results in a self-contained, version-controled, run-everywhere, build-anytime LuaJIT installation in which packages can be added, removed, upgraded and downgraded at will.
Check out the philosophy page more insight into these choices.
OK, how do I put one together?
The best way is with multigit, which keeps everything under version control at all times, making it easy to add and remove packages, stay up-to-date, make pull requests, and even make deployments.
But git sucks, can I skip it?
Git does indeed suck (to some). If you want to avoid git or you don’t care about downloading all that history, you can download the packages from the website directly. Getting luajit and the modules that you need and unzipping them over a common directory is enough to create a runnable LuaJIT installation that is self-contained and portable, meaning it will run the included luajit command from any directory and on any platform. The downside is that updating and removing modules must be done manually too.
I got luapower, how do I make an app with it?
Luapower is supposed to be self-contained, so you have to add your scripts to the luapower directory, among all the other Lua files in there. To run a script type
./luajit myscript.lua (that is
luajit myscript.lua on Windows) from inside the luapower directory (you can also bundle your app into a self-contained executable and run that). If you downloaded luapower with multigit, it’s a good idea to keep your files under version control too:
./mgit init myrepo
./mgit add -f myscript.lua
./mgit commit -m "my first commit"
./mgit myrepo remote add origin https://github.com/myuser/myrepo
./mgit push -u origin/master
On Windows, the command is
mgit instead of
You mean I have to mix my code with yours? That’s gross!
This idea of mixing your code with someone else’s can be appalling at first (especially since it’s pretty crowded in there already), but if you keep your app files with git they will be tracked separately of everything else so you’re not really mixing anything git-wise. The upside is that you get to put any file anywhere (you can add a font to media/fonts or a binary dependency to bin/mingw64/somelib.dll), basically extending luapower just as you would extend an OOP class: in git, your “overrides” stay separate, but at runtime they mix together with the base class. A Linux installation works the same way with packages spreading their files to their appropriate locations in the root filesystem. Of course, you can always just add the luapower directory to your LUA_PATH and keep it separated from your own stuff (but please use LuaJIT 2.1 if you use your own runtime).
What are the oldest platforms that it is guaranteed to run on?
- Windows 7 x64 SP2
- Ubuntu 18 64bit (i.e. EGLIBC 2.27)
That being said, OSX binaries are built with OSX 10.9 compatiblity, and many Linux binaries do support older GLIBC versions, however this is neither tested nor supported.
Why is Mac not supported anymore?
Because it was a drag building and testing for Mac since I’m not on a Mac myself (I’m on Windows) and because Macs have a very slim market share on the desktop and no market share in the data center, so the only users left are Google employees and they don’t dig Lua.
How do I compile the binaries?
Luapower uses shell scripts to build everything. There’s no build system, no makefiles, and no need to specify where to look for dependencies in the host system, because all dependencies are available as luapower packages as well. The build scripts are in the
csrc directory for each package. The C sources are also included, so you can start right away. Just make sure you have a compatible build toolchain installed, and that you build the dependencies first, as listed on the website.
Can I make single-exe apps with it?
Yes. Static libraries are included for all C packages, and can be bundled together with Lua modules and other static resources to create self-contained single-exe apps on any platform.
Can I use it in commercial apps?
Yes. Almost all packages have a non-viral, open-source license, and many are in public domain. If in doubt, check the package table on the homepage (click on the license column to sort by license). Luapower itself, which includes multigit, the build scripts, and the luapower module are in Public Domain.
Can I use it with plain Lua?
Although the module collection on the whole is focused on LuaJIT, pure Lua modules should work with Lua 5.1 just fine, and some of them might even work with Lua 5.2 out-of-the-box. Lua/C modules should work with Lua 5.1 too, since LuaJIT is ABI-compatible with it.
You can also compile stock Lua, bundle it as a luapower package and use that as your runtime instead of luajit.
What about luaffi?
Increasing the portability of luapower beyond LuaJIT is beyond my priorities at the moment. That being said, some Lua+ffi modules might work with luaffi already, but you would have to check that out yourself.
How do I see which files belong to which package?
mgit <package> ls-files
But can I browse them too?
You can browse the whole tree online. Alternatively, you can create hard links with
mgit --all make-hardlinks (not for Windows) and you will get hard links in the
.mgit directory for every package. Now they’re separate and you can list them and check their size, and even edit them and commit the changes. Remember to run that command again if you add or delete files though.
How do I fix a package?
Fork it, clone it from your place (i.e. instead of
mgit clone foo, do
mgit clone https://github.com/you/foo), fix it, then send a pull request. If you want to become a maintainer, email me so I can add you to the luapower account on github.
How do I make a new package?
Refer to get-involved for what it should contain.
Refer to luapower-git for the actual procedure.
How is it different from LuaRocks?
FIXME: What follows is only the luapower author’s biased opinion of LuaRocks. Someone else should write this, ideally an user of both systems. Feedback welcome.
LuaRocks is probably the most popular package manager for Lua. It is quite different than luapower in scope (Lua-focus vs. LuaJIT-focus), philosophy (manifest-based vs. convention-based, install vs. portable-tree) and implementation (full-fledged package manager vs simple git wrapper + reflection library), and with a large module collection. LuaRocks requires declaring all package dependencies, while luapower requires declaring only binary-only/build-only dependencies. Because LuaRocks does not specify a standard directory layout on packages, having installed packages under version control is not possible. Luapower includes and compiles all external libraries, while that is out of the scope of LuaRocks. For this same reason, LuaRocks does not know how to find the include dir and lib dir of external dependencies all by itself, making out-of-the-box compilation of packages with dependencies a hit-or-miss experience. LuaRocks doesn’t specify a required build toolchain for Windows, so you might need to have multiple versions of Visual Studio and MinGW before you get a decent number of packages built. This also affects binary rocks, which may come in linked against various versions of msvcrt.
How is it different from LuaDist?
FIXME: What follows is only the luapower author’s biased opinion of LuaDist. Someone else should write this, ideally an user of both systems. Feedback welcome.
LuaDist is a git-based binaries-included distro with many similarities to luapower and a large module collection. LuaDist supports more platforms and more compilers than luapower, although binaries are not always included for all platforms. LuaDist requires declaring all package dependencies. Building LuaDist binaries requires knowledge of cmake and LuaDist’s own custom macros. Because LuaDist binaries are in separate branches, portable installations under version control are not possible (a deployment step is necessary to get to a running system). LuaDist requires maintaining a strict versioning scheme for packages and for dependency declarations. LuaDist has a full-fledged package manager, while luapower has a simple shell script that leverages git, and a reflection library for package analysis.
How are the libraries chosen?
The included libraries are chosen based on license, portability, speed and maturity, usually in that order.
Where’s the package database?
Package information is computed on-the-fly using the luapower module (which is also what drives this website), except for module dependency information which has to be computed for each platform on that respective platform (because not all modules have the exact same dependency list on all platforms, and because for some modules we have to actually try and load the module to know if the platform is supported or not). That dependency information is stored in luapower_db and it’s updated automatically every time a module changes.
How is versioning maintained?
A package’s version is the result of
git describe --tags --long --always, which returns a string of form
tag is the latest major version,
N is the number of commits after that version, and
hash is the hash prefix of the last commit. This way versioning is unambiguous, not prone to human error, and doesn’t require maintenance. For every incompatible API change, the major version gets bumped. The HEAD is kept compatible across all libraries (incompatible development happens in separate branches, except for new modules that nobody depends on).
Tip: To clone package foo at tag point r5 (which indicates the 5th release), do
mgit clone foo=r5. To clone the same package at a known commit point, do
mgit clone foo=r5-2-a43cf7 or just
mgit clone foo=a43cf7.
Why is your code in Public Domain?
Because I don’t support copyright law.
Where can I get help?
Go to the luapower forum and ask away. There’s no such thing as a stupid question there, any discussion is welcome. Incidentally, that is also the place where you can share your plans for world domination, so go introduce yourself!
How do I report bugs?
For software bugs, use the github issues for that specific piece of software (all software is on github, including this website). For anything else, use the forum.
How can I help?
Making new packages, reporting bugs, writing docs, sending pull requests, are great ways to help luapower grow, and probably make some friends in the process.
If you have a great idea, or you would rather make things differently, just go to the forum and say it. Luapower is at an early stage, so now is a good time to influence where it’s going.
Who are you?
I’m Cosmin Apreutesei, a programmer from Bucharest.
Where are you going with this?
My goal is to create a cross-platform environment for creating desktop apps that run close-to-identically on every platform, with pixel-perfect vector-graphics including text shaping and rendering, complex interactivity beyond standard widget systems, peer-to-peer communication, a multi-threading/multi-process architecture, and fine-grained access to communication peripherals like webcams and pen tablets.
This requires a large number of high-quality packages with extensive APIs that are well below the “scripting” level of abstraction. Achieving this in an open source environment requires a model for development and collaboration with lower friction and a higher level of specificity than what current module distributions provide.
Luapower is an attempt to create that model.
2 months ago
Edit on GitHub