[iklask]

Ah I understand now thank you!

[iklask]

Ah I see, is it  the “Enabled via Plugin” option of “Embedded RTOS Support”?

[iklask]

So I’ve noticed while importing, the build flags don’t get filled in automatically. I know the project is for a device which is not in any VGDB library. Is it expected I specify them manually or is it not importing correctly?

[iklask]

Okay thank you. Looking through that code I think I’ve come up with a strategy.

Like I said, I’m on CrossWorks v3.6.5 and it does not generate a *.ind file. However I downloaded a trial of CrossWorks v4 and it does generate the file. My v4 trial wont fully build my project since it is in trial mode, but I don’t think that matters. Looking at the .ind file generated, I can see exactly which paths VGDB is looking for. I can either:

1. Supress the warning and manually input these later
2. Just copy this .ind file to my older CrossWorks output folder for the import

Is there a tutorial on the site for modifying these BSPtools and using them with VGDB?

[iklask]

Thanks for the quick reply! Ahh I see in my CodeModel.json it was grabbing “bin/arm-none-eabi-gcc”. When I change the regex in the edp.xml to “^bin/arm-.*” it works. So i’ll just update my Arduino platform.txt so it doesn’t need that “bin/”

 

Thank you!

[Author]

Posts