c1906714ee
Give a constant "PlatformIO" name for the C/C++ configuration
2020-11-14 20:10:22 +02:00
77e66241f7
Do not provide "intelliSenseMode" option when generating configuration for VSCode C/C++ extension
2020-11-12 18:56:34 +02:00
3dcc189740
Use custom Pre-Debug task only for multi-env project
2020-11-12 15:35:19 +02:00
48eca22a00
Force VSCode's intelliSenseMode to "gcc-x64" when GCC toolchain is used
2020-11-11 14:19:58 +02:00
2e66c5f807
Generate a working "projectEnvName" for PlatformIO IDE's debugger for VSCode
2020-10-31 19:07:04 +02:00
2a30ad0fdf
Allow in-progress language standards in IDE templates // Resolve #3653
...
Note: VS Code only supports finalized names
2020-09-09 13:56:00 +03:00
adc2d5fe7c
Update VSCode template
...
Starting with cpptools v0.29 escaped paths in compilerArgs field don't work on Windows.
2020-07-28 15:10:52 +03:00
ac1210fbea
Add -imacros files to forcedInclude field in VSCode template
2020-04-26 00:35:22 +03:00
24c04057e9
CLion: Add paths to libraries specified via lib_extra_dirs option ( #3463 )
...
* Add paths to libraries specified via lib_extra_dirs option
Besides, global folders in SRC_LIST seem a bit unnecessary
since there might be unused libraries in these folders
* Refactor processing of includes when exporting IDE/Editor projects
Split includes according to their source. That will help export includes in a more flexible way.
For example some IDEs don't need include paths from toolchains
* Add new record to history log
* Typo fix
2020-04-21 17:37:55 +03:00
154be7fa81
Improve VSCode template structure ( #3385 )
...
* Switch to click argument parser
* Typo fix
* Tidy up VSCode template
Co-authored-by: Ivan Kravets <me@ikravets.com >
2020-02-17 12:19:00 +02:00
ed4452b115
Get rid of direct imports
2020-02-14 17:09:48 +02:00
fbfbf340c1
Add "forceInclude" field to VSCode template
...
VScode doesn't recognize header files included via "-include" flag in "compilerArgs" field.
Instead, absolute paths to these files should be specified in a special section "forceInclude".
2020-02-14 16:43:20 +02:00
d0a6861369
Fix "TypeError: TypeError: write() argument 1 must be unicode" when generating project on Windows/Python 2
2020-02-12 15:14:58 +02:00
86f2dde6f3
Do not overwrite a custom items in VSCode's "extensions.json" // Resolve #3374
2020-02-08 21:36:32 +02:00
0b0b63aa7d
Update templates for Atom, VSCode, CLion ( #3371 )
...
* Wrap flags with whitespace chars when exporting data for IDEs
* Update IDEs templates
Take into account compiler flags that can contain whitespace characters (e.g. -iprefix)
* Update template for VSCode
* Add history record
2020-02-07 11:26:45 +02:00
b15ddc00a5
Pass extra files with compiler options to VSCode IntelliSense tool
2019-12-17 22:40:28 +02:00
44a9de6dcb
Pass -m and -i flags to VSCode Intellisense analyzer
2019-11-15 15:11:13 +02:00
a2830dd527
Automatically normalize file system paths to UNIX-style for Project Generator // Resolve #2857
2019-08-19 14:43:39 +03:00
1a3720cfb9
Ability to set "databaseFilename" for VSCode and C/C++ extension // Resolve #2825
2019-08-18 00:40:59 +03:00
51115c1254
Ignore vscode-cpptools cache ( #2623 )
...
One of the recent updates to the vscode-cpptools extension made it start caching in .vscode/ipch, and this cache can be quite big for even small projects. Since they're cache files, they should be ignored by default. This may be a short-lived suggestion, as there is already some mention that the IntelliSense cache folder may be moved to workspace storage, rather than 'per project' storage... although the 'when' is anyone's guess.
See here for more: https://github.com/microsoft/vscode-cpptools/issues/3347
2019-06-16 12:37:32 +03:00
4266cba53b
Cleanup ".piolibdeps"
2019-05-25 01:10:35 +03:00
5fe4de626b
Implement unified project workspace storage ".pio" // Resolve #1778
2019-05-20 17:01:54 +03:00
bb17630571
Set manifest version of VSCode C/C++ configuration file
2019-03-30 13:00:10 +02:00
e089c4a546
Project Generator: fixed a VSCode C/C++'s "Cannot find" warning when CPPPATH folder does not exist
2019-03-29 21:26:45 +02:00
4ca71e7df1
Project Generator: fixed a warning "Property !!! WARNING !!! is not allowed" for VSCode // Resolve #2243
2019-03-22 21:16:02 +02:00
f539513376
Fixed spurious project's "Problems" for PlatformIO IDE for VSCode when ARM mbed framework is used
2018-12-12 01:28:37 +02:00
16df5474e4
VSCode IntelliSense config: Typo fix with useless bracket
2018-11-29 15:59:22 +02:00
d475f44e49
Escape string when generating manifest for VSCode C/C++ IntelliSense service
2018-11-27 00:54:59 +02:00
4a17a9b5b3
Improved IntelliSense for PlatformIO IDE for VSCode via passing extra compiler information for C/C++ Code Parser
2018-11-21 15:00:13 +02:00
e96078b4e3
Exclude upcoming ".pio" from VCS
2018-10-27 14:18:47 +03:00
b7ac59066f
Revert back "PIO Debug (skip Pre-Debug)" debug configuration for VSCode
2018-09-06 22:21:46 +03:00
a477e8cb23
Default VSCode Debug configuration without Pre-Debug
2018-09-06 16:34:27 +03:00
78c383eb68
Use Pre-Debug task by its VSCode defination
2018-08-27 18:55:08 +03:00
d448a0ec5c
Switch docs to HTTPS
2018-08-15 19:44:02 +03:00
8f88939aa0
Shorten a name for VSCode debug launch configurations
2018-07-04 00:06:44 +03:00
6dada01e70
Disable macOS frameworks for VSCode IntelliSense
2018-07-03 14:17:38 +03:00
3243a84dba
Fix incorrect handling of C/C++ standards passed via build_flags
2018-05-31 16:38:33 +03:00
2bb22a86d7
New UI for PIO Unified Debugger and VSCode
2018-05-08 18:23:27 +03:00
b1caaa2208
Export path to SVD file for IDEs
2018-04-27 20:37:41 +03:00
f46072f769
Generate beta configuration for the new PIO Debugger for VSCode
2018-04-27 18:01:08 +03:00
3ce62fbafe
Escape compiler path for Win
2018-04-20 14:00:40 +03:00
b77160d363
Upgrade VSCode CPP manifest to v3
2018-04-20 13:56:04 +03:00
50b2bc07dc
Add PlatformIO IDE as recommended extension for VSCode's workspace
2018-03-22 12:10:16 +02:00
ef861ed702
Use workspace folder for VSCode CPP tool DB files
2018-03-06 10:38:41 +02:00
e95354afeb
Bump version to 3.5.2rc1
2018-02-24 01:51:07 +02:00
cfb9ec77ce
Keep VSCode CPP DB in workspace
2018-02-24 01:40:49 +02:00
17dc5f594f
VSCode: Show debug console for each session
2018-02-02 17:51:54 +02:00
c9e578f977
Do not show debug console by default for VSCode
2018-01-31 01:11:25 +02:00
1890162f3f
VSCode: add a new "Pre-Debug" task and run it before debugging session
2018-01-30 21:33:56 +02:00
6cddaf9eb7
Ignore VSCode launch.json for VCS
2018-01-13 19:01:27 +02:00
Ivan Kravets