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
315 stars 39 forks source link

stdio.h: No such file or directory #include <stdio.h> #2

Closed terriblefire closed 5 years ago

terriblefire commented 5 years ago

I'm pretty sure i would work round this issue but I wanted to give you feedback on a clean machine running the project for the first time.

Perhaps some hard coded path in there somwhere that needs updated?


> Executing task: c:\Users\stephen\.vscode\extensions\bartman-abyss.amiga-debug-0.7.0\bin\gnumake.exe -f Makefile8mingw -j4 <

Makefile8mingw:41: target 'obj8mingw/main.o' given more than once in the same rule
Compiling bin/elf2hunk.c
C:/github/vscode-amiga-debug/bin/elf2hunk.c:10:10: fatal error: stdio.h: No such file or directory
 #include <stdio.h>
          ^~~~~~~~~
compilation terminated.
gnumake: *** [Makefile8mingw:44: obj8mingw/elf2hunk.o] Error 1
The terminal process terminated with exit code: 1

I wonder if this is only triggered due to the modification date on a clean checkout?

BartmanAbyss commented 5 years ago

Hmm.. what did you do? There's no need to compile elf2hunk.c. That's coming from within the extension. I think your project folder isn't set up right.

BartmanAbyss commented 5 years ago

OTOH, there may be some new bug here.. Hold on, I'm taking a look...

terriblefire commented 5 years ago

i'll wipe the folder and checkout again. Just to be sure.

terriblefire commented 5 years ago

with a clean checkout.

  1. Launch VS Code.
  2. Open the folder.
  3. Run Amiga: Init Amiga Project
  4. Press F5

I see the error above.

I skipped the kickstart step this time to reduce the reproduction steps. It wouldnt make a difference until runtime though correct?

BartmanAbyss commented 5 years ago

something broke with the latest VS Code update. Trying to fix...

terriblefire commented 5 years ago

No worries. :) Thanks

BartmanAbyss commented 5 years ago

Hmm.. seems I was just seeing a problem running a development build of the extension. When I ran the installed extension, everything was working fine.. Can you make sure your project folder is empty and try "Init Amiga Project" again? Also, by any chance did your project folder path contain any spaces?

BartmanAbyss commented 5 years ago

See here how it's supposed to work...

terriblefire commented 5 years ago

Ok i got it. The unintuitive bit is not your fault. its how the Amiga-Assembly project worked.

Basically i ran Init Amiga Project in the git checkout folder. I can see this isnt correct but I can also see other users making the same mistake. May want to think about how to avoid getting asked this dumb question over and over.

BartmanAbyss commented 5 years ago

Cool! Any idea how I could clarify it in the README?

BartmanAbyss commented 5 years ago

I think I could add a check for "Init Amiga Project" to make sure the folder is empty...

terriblefire commented 5 years ago

Yeah. that would save you some headaches methinks.

BartmanAbyss commented 5 years ago

done. 0.7.1 uploaded