Description
Would there be any interest in separating the patched compiler, tools and gcc8_support etc into a separate project?
Seems like there's a reasonably natural boundary between the toolset and the vscode extension which uses it, and it might make the toolset more approachable to non-vscode users.
Personally, I'd just love to be able to easily drop in the commandline tools to quickly port an existing (non vscode) game project to amiga. Most other platforms I support (nds, megadrive, pce, cx16, sdl2...), setting up the environment is usually just a case of adding an appropriate bin directory to the path. I can kind of do that at the moment using the binaries in the installed extension, but it feels a bit messy having a path like:
EXPORT PATH="$PATH:$HOME/.vscode/extensions/bartmanabyss.amiga-debug-1.7.7/bin/linux/opt/bin:$HOME/.vscode/extensions/bartmanabyss.amiga-debug-1.7.7/bin/linux"
...
Things like issue #53 would also help - having to include the support code in every project is just a tiny extra bit of friction that could be smoothed off.