Closed terriblefire closed 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.
OTOH, there may be some new bug here.. Hold on, I'm taking a look...
i'll wipe the folder and checkout again. Just to be sure.
with a clean checkout.
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?
something broke with the latest VS Code update. Trying to fix...
No worries. :) Thanks
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?
See here how it's supposed to work...
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.
Cool! Any idea how I could clarify it in the README?
I think I could add a check for "Init Amiga Project" to make sure the folder is empty...
Yeah. that would save you some headaches methinks.
done. 0.7.1 uploaded
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?
I wonder if this is only triggered due to the modification date on a clean checkout?