* Fixes to QuickJS marshaling.
* Handle more primitive types in `GetInfo`.
* Fix generator kind CLI option matching.
* Alias QuickJS generator kind to `quickjs`.
* General CLI code cleanups.
* Default to x64 platform over x86 for the CLI.
* Implement new Lua bindings file and commands for CLI tool.
* Fix QuickJS primitive type marshaling to take target sizes into account.
* Minor code cleanup.
* Avoid generating includes to units when generating the QuickJS module.
* Update file generation naming pattern for QuickJS files.
* Update QuickJS JS_GetOpaque and JS_GetAnyOpaque references to work with latest upstream.
* Update QuickJS runtime and support code to work with latest upstream.
* Avoid generating properties when generating QuickJS register code.
* Update QuickJS test suite to bootstrap its own QuickJS runtime.
* Update QuickJS test suite to use a Lua bindings definition file.
* Minor fixes to test header files.
* Fix C++ warning about return values for event invokes.
* Disable some non working tests for QuickJS.
* Enable QuickJS testing on CI.
* Fix shell color attributes for test scripts when under CI.
* WIP CI fixes.
* Fix warnings in QuickJS support runtime code.
* Use C99 designated initializers for all QuickJS class def members.
* Disable QuickJS CI steps on Windows.
* Clean up error handling for `JS_ToBool`.
* More QuickJS support code fixes.
* Rename Signal.cpp to QuickJS nomenclature.
* Fix QuickJS JS_ToBigUint call.
* Remove QuickJS test script verbosity.
* More CI fixes.
* Verbose build.
* Extension fix.
* support clang 15.0.7
* Fix Premake archive logic to work with official releases.
* Try and upgrade CI to latest OS versions.
* Try and fix LLD link call in parser.
* CI fixes.
* Enable VS 2019 and VS 2022 for LLVM windows workflow.
* Update to a more recent LLVM revision.
* More build fixes.
* Use the system linker for linking symbols libraries outside Windows.
Builtin lld is giving some weird linking errors when linking with the
new LLVM version. We probably need to set some custom options. Using the
system linker should be a better idea anyway, more robust and future
proof.
---------
Co-authored-by: you74674 <you74674@gmail.com>