Tags: vixcpp/cli
Tags
fix(run): detect Vix runtime scripts correctly in CMake fallback - fix script feature detection for `using namespace vix` and related patterns - make generated fallback CMakeLists use the Vix runtime branch when needed - ensure Vix runtime scripts link against the umbrella `vix::vix` target - keep `--local-cache` behavior working for generated script projects Result: - `vix run file.cpp` works for Vix runtime scripts - `vix run file.cpp --local-cache` works too - generated fallback projects now enter the correct Vix linking path
feat(run,check): add --local-cache for script mode and unify cache be… …havior - add localCache option to run and check commands - support --local-cache to use local .vix-scripts directory - default to global ~/.vix/cache/scripts for clean DX - update ScriptCMake to switch between local/global cache - propagate option through RunFlow, RunScript, and CheckScript - fix build break due to updated get_scripts_root signature - document --local-cache in CLI help
feat(run,build): add SQLite/MySQL flags and clean support - add --with-sqlite and --with-mysql to vix build - add --with-sqlite and --with-mysql to vix run - inject DB options into generated CMake (script mode) - extend make_script_cmakelists signature with DB flags - propagate flags through RunDetail, RunFlow, RunScript - add --clean support to vix run (clean build directory before configure) - fix CheckScript call to new make_script_cmakelists signature - keep behavior consistent between build and run commands This enables database backends to be activated without modifying CMake manually.
feat(make): add config generator with interactive prompts - introduce 'config' make kind - generate dynamic config.json via vix make config <name> - add ConfigGenerator (hpp/cpp) - support sections: server, logging, waf, websocket, database - add CLI flags: --websocket, --database, --no-* - implement interactive mode (vix make:config) - update dispatcher and MakeOptions - expose config in help and output
feat(cli): handle CMake build errors with structured diagnostics - detect and handle common CMake failures (cache mismatch, missing package, compiler not found, etc.) - extract useful context (target, package, file, line) from raw logs - provide clear, actionable hints for each error - unify output style with CLI (error, hint, colored fields) - improve developer experience by replacing noisy CMake output with readable diagnostics This makes CMake failures understandable and directly actionable.
PreviousNext