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
* 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
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".
* 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
* Fixed an issue when configuration file options partly ignored when using custom ``--project-conf`` // Resolve#3034
* Py2 compatible makedirs
* Fix circle dependency
* Fix broken import in test examples
* Fix history
* Remove YAPF markers
* PyLint fix
* Fix invalid project conf path
* Move PIO Core to the root on Windows, issue with long CPPPATHs
* Respect global PLATFORMIO_BUILD_CACHE_DIR env var
* Fix Appveyor paths
* Minor changes
* 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
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
Ivan Kravets