MarkMoxon wrote: ↑Mon Mar 25, 2024 9:33 pm
My project has lots of "entry points" - one for every binary that the project builds, and there are lots of them (about 150 in all). Any advice on which one I should choose? There is no overall parent.
Wow, that's a big project! For these multi-target cases, we want to store the path to all the compile targets. This is to make it consistent with your build process i.e. every BeebASM.exe -i fileXX.asm, we want the path to fileXX.asm in the settings.json file.
As an example, one of the test projects I used is Tricky's PacMan. It builds game.asm and build.asm, and my settings.json looks like this:
Code: Select all
{
"beebvsc": {
"sourceFile": [
"/Users/tomtom/Documents/Beeb/Games/Tricky's PacMan Source/PacManSrc/game.asm",
"/Users/tomtom/Documents/Beeb/Games/Tricky's PacMan Source/PacManSrc/build.asm"
],
"targetName": "build.ssd"
}
}
If you're on Windows, I guess the paths will look quite different but hopefully this is something that can be generated fairly easily based on your existing make file.
MarkMoxon wrote: ↑Mon Mar 25, 2024 9:33 pm
Where do I choose the file from? If I press F10 then the command field changes to "Create new build target: Choose a file", but I don't know what to do next. I was expecting a list of files to drop down from the command field or something, but I don't get that. This an absolutely huge project, with 1000s of .asm files, so might that be an issue?
The F10 command just searches the workspace root directory in vscode, so probably you have all the files in a subfolder and we aren't picking them up. However, given the large number you mentioned, you won't want to be pressing F10 150 times to add the files one at a time! So just editing the settings.json directly probably makes sense.
MarkMoxon wrote: ↑Mon Mar 25, 2024 9:33 pm
Bit confused really, so sorry about that! I would like get rid of all these errors, though...
Sorry it's misbehaving, you may have better luck downgrading to an earlier version. Someone else mentioned they found 0.1.2 working better. It misses out on some nice new features but if changing the settings.json doesn't solve the problem then that could be a temporary fix until we can work out a better solution.
By the way, on startup it will attempt to build a tree of relationships between source files. So the 150 compile targets will be opened and scanned for INCLUDE statements, then recursively do the same for all included source files. It might take a moment depending on how big those are and the disk speed.
