Thanks to visit codestin.com
Credit goes to github.com

Skip to content

Document purpose of "C/C++ Include Paths and Symbols" properties for Core Build Makefile projects. #1328

@ewaterlander

Description

@ewaterlander

This issue was split from issue #1041

The "C/C++ Include Paths and Symbols" properties page class IncludesSymbolsPropertyPage was deprecated in 2010 (adfdd48) and re-activated in 2017 (d9b8eb3) by Doug.

The reason for reactivating was to create a backup for the user in case the build output parsing would fail to get all the compile options for indexing. So far I never ran into this issue, but I can imagine that users would appreciate this backup method in case the indexing goes wrong and the user sees false syntax errors.

The problem here is that it is not made clear to the user that the property page is only a backup for the indexer. It's not for setting extra include paths and macros for the build step. Any include path or macro specified here must also have been specified in the Makefile.

Image

Metadata

Metadata

Assignees

No one assigned

    Labels

    buildBuild components of CDT, anything to do with running the compiler, using Make, CMake, or any builder

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions