VS Code doesn't like complex build projects. :(

Hi,

I have several projects whereby one set of code compiles to numerous data fields. This is managed by monkey.jungle but because I cannot be arsed to hand edit a file nine times when I want to update a family of dials, for example, I have a shell script that redirects compiler to a specific monkey jungle and manifest by filename. (EG: Rather than compile with monkey.jungle and manifest.xml, I might compile with monkeyA.jungle and manifestA.xml.)

HOWEVER...

The default behaviour of the VS Code plugin appears to be to scan through *.jungle to use ALL of them at the same time, so I cannot test anything due to errors like:

ERROR: monkeyA.jungle:1: Attempting to reset project property 'manifest'.
The terminal process "<SNIPPED>" terminated with exit code: 104.

Terminal will be reused by tasks, press any key to close it.

Is there any way to STOP VSCode plugin doing this ridiculous thing?

Thanks,

0 9635560 over 4 years ago

ETA: On one project, I have been able to use -f "monkey.jungle" to get it to run, but in another project (where I use a shed load of annotations, in case it is relevant) I instead get to:

Error: Symbol Not Found Error
Details: Could not find symbol 'initResources'

ETA: And in fact, on the project that had been working, I am now seeing the same error (but for a different class) there.

0 Kyle.ConnectIQ over 4 years ago

Please file bugs in our bugs forum. I've gone ahead and filed this one but in the future please create a bug report for any VS Code issues.

0 9635560 over 4 years ago in reply to Kyle.ConnectIQ

Will do.

Couldn't see it in the bug reports forum, so I guess that's on an internal list.

I see you did an update overnight, and the initResources thing has fixed, but I am still struggling to get it to respect my -f "monkey.jungle" in general.

0 Kyle.ConnectIQ over 4 years ago in reply to 9635560

9635560 said:
I see you did an update overnight, and the initResources thing has fixed, but I am still struggling to get it to respect my -f "monkey.jungle" in general.

The way the extension is currently setup the -f command to the compiler won't work. We'll evaluate this as part of the ticket I mention above.

0 9635560 over 4 years ago in reply to Kyle.ConnectIQ

Any movement on this one?

I'm really loving the VS Code extension.... but I cannot use it for most of my projects!

0 Kyle.ConnectIQ over 4 years ago in reply to 9635560

It's near the of our backlog of things to fix. For breaking issues that affect everyone we'll do an emergency release. For all other issues they'll get released with the next planned release.