Lua package paths are not instantiated sanely at build time via cmake #15588
|
The new Lua config features are awesome and I'm having a lot more fun getting things setup properly. As a multi-decades user of Awesome I feel like I've found my way home! That being said there are currently a lot of "paper cuts" involved β things that could be smoothed over for a smother user experience, especially integrating with the rest of the system. As the Arch Linux package maintainer, I was just looking into cleaning up one issue but don't see a way to do it. The Cmake config looks at the pkg-config data for the system Lua installation and uses it to build against the right Lua headers, but it doesn't take advantage of some of the variables provided. Notably in a running instance of Hyprland neither the The correct paths are available in the PkgConfig file or can be derived from calling the system |
Replies: 2 comments 10 replies
|
At least this works, but standard distro packages are very much supposed to be supported, so they should be made work by default... package.path = '/usr/share/lua/' .. _VERSION:sub(5) .. '/?.lua;/usr/share/lua/' .. _VERSION:sub(5) .. '/?/init.lua;' .. package.path
posix = require 'posix' |
|
I don't know if doing them at comptime is perfect. For example on nix, it makes much more sense to derive them from env. |
So yes, my testing was off:
hyprland reloadgot rid of the override in my user config, but I had not restarted the binary. Having done that now this does look right!