search

BartmanAbyss / vscode-amiga-debug

One-stop Visual Studio Code Extension to compile, debug and profile Amiga C/C++ programs compiled by the bundled gcc 12.2 with the bundled WinUAE/FS-UAE.
GNU General Public License v3.0
312 stars 39 forks source link

Populate compiler path setting in template #134

Closed grahambates closed 1 year ago

grahambates commented 1 year ago

Currently the project template includes a fixed path to a named user directory which won't be valid on another machine. This has the effect that it will fall back to the system GCC, which doesn't know about Amiga libraries etc.

I've changed this to a placeholder which gets replaced with the path of the bundled GCC binary.

BartmanAbyss commented 1 year ago

Is this even still used? I thought this was only used until I used my own configurationProvider. I think the settings.json file should simply be deleted.

Or have you noticed a different behavior?

grahambates commented 1 year ago

yes as far as I can see it does get used on the project once it's initialised. I get this error:

image

It falls back to the system GCC which doesn't know about NDK includes.

image

When configured with the correct path to the bundled GCC everything works fine and I get working Intellisense. The other option would be to just configure the include path, but using a known version of GCC seems more reliable.

grahambates commented 1 year ago

Actually ignore me, you're right. This setting should come from the BartmanAbyss.amiga-debug config provider. The only problem is that the value in settings.json takes priority so deleting this file is the correct solution. I'll create another PR for this.