Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 359146 - [Scanner Discovery] Discovery Optioons "Compiler Invocation Command" does not respect active configuration
Summary: [Scanner Discovery] Discovery Optioons "Compiler Invocation Command" does not...
Status: NEW
Alias: None
Product: CDT
Classification: Tools
Component: cdt-build (show other bugs)
Version: 8.0   Edit
Hardware: PC Linux
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: cdt-build-inbox@eclipse.org CLA
QA Contact: Jonah Graham CLA
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-09-27 17:15 EDT by Paul Molodowitch CLA
Modified: 2020-09-04 15:20 EDT (History)
2 users (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Paul Molodowitch CLA 2011-09-27 17:15:45 EDT
Build Identifier: 20110615-0604

Ie, if I'm using "Managed Build System - per project scanner info profile"

"Debug" Configuration:
Compiler invocation command: debug
Compiler invocation arguments: foo

"Release" Configuration:
Compiler invocation command: release
Compiler invocation arguments: bar

...then, regardless of which configuration is active when I do the build, it always seems to use my Debug Configuration (ie, "debug foo").  (I believe it's using whatever is the "first" configuration defined, but I haven't tested that).  In no circumstances does it ever seem to use the release command, "release bar".

My project was a non-managed Makefile project, and my discovery profile scope was per-language (though, for testing, i set both languages to do the same thing  per configuration).


Reproducible: Always

Steps to Reproduce:
1. Create a makefile project

2. Create two build configurations

3. In the discovery options for the first configuration, set:
Discovery profiles scope: Per Language
(For each language):
Discovery profile: Managed Build System - per project scanner info profile
Compiler Invocation command: echo
Compiler invocation arguments: FirstConfig
Show output in a dedicated console: on

4. Set the discovery options for the 2nd configuration the same, except:
Compiler invocation arguments: SecondConfig

5. Set the active configuration to the 2nd configuration.

6. Build.  In the "normal" build window, you should see that it does whatever you set up for the 2nd configuration... but in the "CDT Built-In Specs Console, GNU C+++" console, you will see that it has echoed "FirstConfig"