For understand these part, read build_instructions.md and build_toolchain.md first
-
verify if its to test a container
- if its to test a container , creates and launch that container and end build
-
creates the encryption key (basically its creates a file called src/macros.encrypt_key.h ) containing a macro called vibescript_get_key that its used to get the encryption key check key_obfuscate for more details
-
Installs the dependencies
-
create the assets embed vars Assets docs
-
make silver chain src organization read build_toolchain.md for more details
-
create the build_functions and stores on a table, to be able to be called correlated to command lines
-
iterate over the build functions and call the function that matches the command line
- amalgamation_build generate the release/vibescript.c file that contains all the source code of the project
- alpine_static_build.lua build the project using alpine linux and static linking and generates the release/vibescript.out binary
- debian_static_build.lua build the release/vibescript.deb package
- local_linux_build.lua build the project using the local linux and generates the vibescript binary in the root folder of the project
- rpm_static_build.lua build the release/vibescript.rpm package
- windows64_build.lua build the project using windows 64bits and generates the release/vibescript64.exe binary
- windowsi32_build.lua build the project using windows 32bits and generates the release/vibescripti32.exe binary