Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 357927 - Scanner discovery should figure out options to use like -std=c++0x automatically
Summary: Scanner discovery should figure out options to use like -std=c++0x automatically
Status: RESOLVED DUPLICATE of bug 388484
Alias: None
Product: CDT
Classification: Tools
Component: cdt-build (show other bugs)
Version: 8.0   Edit
Hardware: All All
: P3 normal with 4 votes (vote)
Target Milestone: ---   Edit
Assignee: cdt-build-inbox@eclipse.org CLA
QA Contact: Andrew Gvozdev CLA
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-09-16 07:41 EDT by Andrew Gvozdev CLA
Modified: 2013-07-22 01:24 EDT (History)
5 users (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Andrew Gvozdev CLA 2011-09-16 07:41:16 EDT 
-- Created from bug 356062 Comment 7 --

We should make it easier for the user to keep the build-settings in sync with the compiler inspection done as part of the scanner discovery. Many of the compiler options influence the predefined macros and/or the predefined include search path. The option -std=c++0x is just an example for that.

There are probably two use cases:
(1) Managed build:
    The user has to add the compiler option for the build and separately
    he needs to adjust the command-line for the compiler inspection.
    Can we reuse the settings specified for the build?
(2) Unmanaged build:
    The option has to be defined somewhere in a makefile.
    Can we grab the compiler options via the build-output parser?
Comment 1 Matt Hargett CLA 2011-12-04 09:21:22 EST 
This would be extremely useful for mixed C/C++ projects, where one configuration builds a given file as C, and another configuration builds the same given files as C++. It's also extremely useful since specific files being compiled with -std=c99 or -std=c++11 will have slightly different built-in symbols.
Comment 2 Andrew Gvozdev CLA 2013-07-21 04:33:01 EDT 
*** Bug 404913 has been marked as a duplicate of this bug. ***
Comment 3 Andrew Gvozdev CLA 2013-07-22 01:24:05 EDT 
There are separate bugs open for both issues.
(1) is covered by bug 404913 and (2) by bug 388484.

*** This bug has been marked as a duplicate of bug 388484 ***