Bug 240768 - CDT tries to build configurations using unsupported toolchains.
Summary: CDT tries to build configurations using unsupported toolchains.
Status: NEW
Alias: None
Product: CDT
Classification: Tools
Component: cdt-core (show other bugs)
Version: 5.0   Edit
Hardware: PC Linux
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: Project Inbox CLA
QA Contact: Jonah Graham CLA
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2008-07-15 02:48 EDT by Mark Espiritu CLA
Modified: 2020-09-04 15:27 EDT (History)
0 users

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Mark Espiritu CLA 2008-07-15 02:48:18 EDT
Build ID: I20080617-2000

Steps To Reproduce:
1. On Windows, create a C++ project with all available build configurations.
2. Switch to unsupported configuration. (e.g. MacOSX)
3. Build

More information:
In the extension point we are using is org.eclipse.cdt.managedbuilder.core.buildDefinitions. The "toolChain" entry that enumerates the supported platforms. ("win32", "linux", "solaris", "hpux", "aix")

However, when you try to build an unsupported platform, CDT will allow you to do so (and fail). 

We think that build configurations based on toolchains that don't support the current platform should be prevented from running. (e.g. Debug_with_MacOSX GCC should not be built on Windows platform). The information about which configuration/toolchain is valid can be taken from osList in toolChain entry.

Perhaps an implementation could be that the UI will not allow you to set the "active build configuration" to be one of the unsupported ones(?)

We are currently hitting this problem on CDT 4.0.3. But it seems the same on Ganymede.

We hope the community will consider this enhancement request.

Thanks!