ac1210fbea
Add -imacros files to forcedInclude field in VSCode template
2020-04-26 00:35:22 +03:00
a556573a4f
Move env dependent directories to appropriate CMAKE_BUILD_TYPE // Issue #3460
...
This will allow to dynamically populate list of sources depending on
selected environment. At the same time "src" and "lib" folders remain
common for all environments
2020-04-21 22:01:07 +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
b9fd97dae4
Changes required for CLion PlatformIO plugin ( #3298 )
2020-03-09 15:47:41 +02: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
8675d3fa46
Use proper CMake variables for setting compilation flags
2019-11-21 00:39:05 +02:00
b37814976c
Fix project generator for CLion
2019-11-20 23:31:35 +02:00
7eab5d567e
Fix CLion generator when one env is used
2019-11-17 00:35:56 +02:00
44a9de6dcb
Pass -m and -i flags to VSCode Intellisense analyzer
2019-11-15 15:11:13 +02:00
f3992f8e53
Create dummy target for CLION
2019-11-05 15:59:06 +02:00
66cc557d2f
Export SVD Path to CLion
2019-11-05 15:16:50 +02:00
9786b3e1b9
Fix CLion integration when project name contains a space
2019-11-05 15:16:35 +02:00
3de2d84e2b
Fixed an issue with a GCC Linter for PlatformIO IDE for Atom // Resolve #3218
2019-10-31 22:42:22 +02:00
087a8f6dd0
Fix Visual Studio template files encoding // Resolve #3183
2019-10-25 14:27:47 +03:00
ed6c9a08ce
Add custom "PLATFORMIO_BUILD_DEBUG" target for CLion
2019-10-24 17:21:02 +03:00
7a07a2e63e
Generate `.ccls` LSP file for Emacs
2019-09-03 15:31:33 +03:00
f966eeb604
Fixed an issue with project generator for CLion IDE when 2 environments were used // Resolve #2824
2019-08-30 16:40:44 +03:00
34176f974b
Fix generator for CLion when project is empty // Issue #2824
2019-08-30 15:45:21 +03:00
db6f983364
Fix issue for CLion project generator when environment contains space // Issue #2824
2019-08-30 10:55:13 +03:00
e08527a0af
Cleanup CLion project generator
2019-08-29 16:58:18 +03:00
4a6d5e8395
Added support for multi-environment PlatformIO project for CLion IDE // Resolve #2824 Resolve #2944
2019-08-29 16:26:51 +03:00
1c8666e946
Clion integration, resolves #2824 ( #2944 )
...
* Better environement integration :
- Environement can be selected in the build target menu of CLion
- Platformio target runs on the selected environment
- Changing environment changes defined preprocessor variables and includes accordingly
- Added 'All' build profile that runs targets on all environment if there are multiple of them (Original behaviour)
* Calling get_project_dir() only once.
* Fixed include path not being converted to unix style.
Removed duplicate and not normalized definition
2019-08-29 15:01:50 +03:00
223a85baca
CCLS LSP for VIM // Resolve #2952
2019-08-29 14:20:24 +03: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
c69e80249d
Append system PATH to overridden in CDT project // Resolve #810
2019-07-04 22:56:54 +03:00
2a4b25705c
More pre-configured target for Eclipse IDE
2019-07-04 22:53:36 +03:00
412a1f78cd
Fixed an issue when generating invalid "Eclipse CDT Cross GCC Built-in Compiler Settings" if a custom PLATFORMIO_CORE_DIR is used // Resolve #806
2019-07-04 20:07:44 +03:00
6739d5a570
In the current version of this template all build targets result ( #2714 )
...
in
pio -c -f eclipse debug run target <mytarget>
The commit fixes this to be
pio -c -f eclipse run target <mytarget>
See also discussion in forum:
https://community.platformio.org/t/pio-4-0-0b3-potential-bug-in-cprojet-tpl/8390
2019-06-29 12:48:24 +03:00
e61caa37a8
Fix issue when CMakeListsUser.txt is not included // Resolve #2712
2019-06-27 14:04:16 +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
9ce9171a36
Fix typo
2019-05-28 01:19:51 +03:00
fea7e97112
Fix an issue with hardcoded C stadard version when generating project for CLion IDE // Resolve #2527
2019-05-25 20:47:39 +03:00
7beb332b31
Support custom CMake configuration for CLion IDE using `CMakeListsUser.txt` file
2019-05-25 20:46:56 +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
e0b9d080fa
Project Generator: add new targets for CLion IDE "BUILD_VERBOSE" and "MONITOR" (serial port monitor) // Resolve #359
2019-02-23 22:34:36 +02:00
63075c9607
CLion: Improve project portability using "${CMAKE_CURRENT_LIST_DIR}" instead of USER_HOME
2019-01-17 18:04:52 +02:00
286a53991c
Use GCC C++ compiler for Eclipse project indexer // Issue #1010
2019-01-11 12:52:00 +02:00
a092f87c50
Eclipse: Provide language standard to a project C/C++ indexer // Resolve #1010
2019-01-10 21:57:39 +02:00
4dfa885a85
CLion: Improve project portability using "${CMAKE_CURRENT_LIST_DIR}" instead of full path
2018-12-13 17:30:10 +02:00
Valerii Koval