You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
[Feature request] have IntelliSenseMode option with unknown platform, compiler and arch #6813
I'm working on a project that targets embedded systems.
working on Macbook Pro
target system: Arduino (tiny ARM board)
#6745 added definitions for Linux, macOS, WIndows, but no other definitions.
I think it would be nice to have a option that allows users to define their own settings for a particular system without automatically adding them. (like "intelliSenseMode": "bare")
Akihiro YAMAZAKI (@zakkie) Would just the platform being unknown be sufficient, e.g. unknown-gcc-x64? I think our parser will require the compiler and architecture to be known.
It should be possible to workaround this issue via removing the defines in the the *.json file (that matches the target intelliSenseMode) next to the extension binaries, but the modification would need to reapplied after any extension update.
This looks very similar to #4653 This issue goes a bit further, but I suspect the up-votes on the other issue are in favor of what this issue is requesting. So, closing this issue in favor of the other one.
Akihiro YAMAZAKI (@zakkie) If there is something here that is not tracked by the other issue, please let us know.
Activity
sean-mcmanus commentedon Jan 20, 2021
Akihiro YAMAZAKI (@zakkie) Would just the platform being unknown be sufficient, e.g. unknown-gcc-x64? I think our parser will require the compiler and architecture to be known.
sean-mcmanus commentedon Feb 3, 2021
I'm seeing multiple users hitting this, e.g. #2086 (comment)
sean-mcmanus commentedon Feb 3, 2021
It should be possible to workaround this issue via removing the defines in the the
*.jsonfile (that matches the target intelliSenseMode) next to the extension binaries, but the modification would need to reapplied after any extension update.Colengms commentedon Apr 16, 2021
This looks very similar to #4653 This issue goes a bit further, but I suspect the up-votes on the other issue are in favor of what this issue is requesting. So, closing this issue in favor of the other one.
Akihiro YAMAZAKI (@zakkie) If there is something here that is not tracked by the other issue, please let us know.