You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As the situation stands, we need to install Lua internals, separate version of Luarocks for that Lua and Pallene Tracer before we manually install Pallene in system. That is too much of a hassle to do by hand. A script to automate it would be nice to have.
The text was updated successfully, but these errors were encountered:
Interesting idea! I had forgotten about that script.
Do you know how that installer deals with the C bits of Pallene? Pallene needs to install C header files and shared libraries; if those aren't in a standard directory such as /usr/local then one may need to pass extra flags to the C compiler and linker...
The Pallene compiler does not have an easy way to specify a local Lua directory and I decided against hacking it so you will have to pass CFLAGS as an environment variable for it to work.
We should also pay attention to the installation instructions for the CI, inside .github/workflows. It would be lovely if we could keep those build instructions in sync with the install.sh and the README. Perhaps by having the CI workflow call the install.sh?
As the situation stands, we need to install Lua internals, separate version of Luarocks for that Lua and Pallene Tracer before we manually install Pallene in system. That is too much of a hassle to do by hand. A script to automate it would be nice to have.
The text was updated successfully, but these errors were encountered: