prb28
commented
5 years ago I understand your frustration. Please see this extensions as an hobby project and not a full professional grade IDE for the Amiga. My main purpose was to have something really easy to use for simple projects to learn and have fun with the asm on a amiga (copper/blitter) not for combined big vbcc/vasm/vlink projects.
So yes, this is not adapted for your needs because there is no build system (makefile / cmake / gradle / etc.) all the files are compiled into one dir and linked together because it is the simplest way to do with little projects, and that's what I wanted! (really!) (the link order is missing it will be fixed in the next release thanks to a pull request from @bSr43). The debugger will certainly not work with C projects because it will not resolve the symbols, and will not attach to the sources and that may be a lot of work to do.
In your case, you have to disable the vlink option and, as you figured out, to create a task in vscode to call a makefile (the cpp plugin will do that). If you have a not too big example I can try to configure it with you and see if a feature may be created in the extension, at least an FAQ.
But as you seem ready to dig into it and in the documentation, that would be a great contribution, really appreciated, I'm not a good documentation writer (as at least you and @abelanet noted) and I'm using vscode for some time so a lot of things seem natural for me. So the documentation is in markdown and this documentation on how to make pull requests on project wiki may be a good way to start. A video may be easier to understand ?
lastebil
geijer
mithrendal
In help->toggle developer tools ->console I get this ...
When I install it than the language server crashes... For what do I need it ?
I've used vasm and vlink quite a bit in the past, and was hoping to be able to use the syntax highlighting and debugging of this project, but I'm very confused about makefile support - both in visual studio code and using your plugin.
Visual Studio Code seems to have recently changed the way makefiles are triggered - via a "tasks.json" with no documented location. There is a lot of confusion (see, for example, https://stackoverflow.com/questions/34268034/where-is-the-tasks-json-file-in-vscode for which the accepted answer no longer works (F1 does nothing) and the last answer indicates it MIGHT work with the .vs or .vscode folder...) Other searches have led me to many confused people and no clear answers.
However, your setup appears to be ... overloading vlink to just operate on all the files in a directory? (I honestly can't figure out why anyone would do this (: ) But it is not creating a tasks.json file. So your method seems to be at odds with the vscode documentation.
How is one supposed to go about adding a method of building, other than the suggested "just throw everything in a directory and hope vslink can figure it out" (which will not work for my project, and I anticipate it won't work well for any vbcc and vasm combined projects either.)
(I also have to echo the already open report that the documentation is very lacking - if you don't know VS Code, it's basically unusable. Instead of working on Amiga code, I'm fighting an editor, trying to get it to work... not optimal...
But despite my frustration, I'd be willing to help write better documentation on "how to get started" and "how to migrate an existing project." As I can't do either of those things now, learning how would enable me to write that documentation...)