The generated executable depends on files in the source tree

It is unexpected that the compiled executable requires the build dir to remain present. This additionally makes it problematic to include this software in any operating system distribution.

Currently the main() function sources main.lua at run-time using load() with a filename, and consequentially all of its required files are also read from the source tree at run-time. Furthermore version.lua parses the changelog at run-time to determine the version number. There might be more similar constructs. I have not looked further.

In order to make the built executable self-sustained, one might wish to use constructs which injects the actual Lua source files into the Rust source using e.g. include_str!(). The AsChunk trait has the required implementations for a &str to be given to load().

As for version strings, the best solution would probably to be solve issue #9, which would make the version string available at build-time in Rust context using the env!() macro with CARGO_PKG_VERSION. If that for some reason is not desired or possible, parsing the changelog at build time using a build.rs script would be an alternative.

从 crates/luals/src/main.rs 开始，尤其关注 main() 入口点和 script/version.lua；按照建议检查其他运行时文件加载路径。构建可执行文件，然后在构建目录和源代码目录不可用的情况下对其进行测试。当可执行文件无需源代码树中的文件即可运行，并且无需在运行时解析 changelog 就能报告其版本时，即表示完成。