This PR refactor flag handling in vab and vab.cli to be a bit more ergonomic to work with. The existing flag.FlagParser functionality is preserved, but deprecated.
This is the first step in simplifying the way vab works internally (and programmatically via vab.xyz usage).
The plan going forward is to allow for easier extending/reusing vab's powerful functionality in user space.
I hope to bring support for user space supplied commands that can be installed and run via vab itself to allow for extending vab's support for user space projects.
And example of such a user space command, could be a command that brings vlang/sdl support to vab via e.g.:
vab sdl --archs arm64-v8a run ~/.vmodules/sdl/examples/basic_window the same could then be done for e.g. various raylib wrappers etc.
This PR refactor flag handling in
vabandvab.clito be a bit more ergonomic to work with. The existingflag.FlagParserfunctionality is preserved, but deprecated.This is the first step in simplifying the way
vabworks internally (and programmatically viavab.xyzusage).The plan going forward is to allow for easier extending/reusing
vab's powerful functionality in user space.I hope to bring support for user space supplied commands that can be installed and run via
vabitself to allow for extendingvab's support for user space projects.And example of such a user space command, could be a command that brings
vlang/sdlsupport tovabvia e.g.:vab sdl --archs arm64-v8a run ~/.vmodules/sdl/examples/basic_windowthe same could then be done for e.g. variousraylibwrappers etc.