Community
Participate
Working Groups
Anomaly 1: 1. Click New/C++ Project and open the wizard. 2. Select "Makefile project". At that point the whole toolchain selection control disappears, so you cannot select any toolchain. See attached picture. 3. Resize the window. Now the toolchains appear and can be selected. See 2-nd attached picture. 4. (optional) Select different project type (Executable is good) and reselect "Makefile project". Now no amount of resizing will let you see any toolchains for makefile project. Anomaly 2: 1. Click New/C++ Project and open the wizard. 2. Enter some project name and select "Makefile project". Click Next. Note "Default" configuration on the second page. 3. Click Next (navigating to "Test Page" - why it is even there in 5.0.0 Final released version? whatever.) Click Back. Somewhat richer but unexpected set of configurations "Debug" and "Release" appear. Anomaly 3: I was poking around and in some cases your project (with the name from "Project name" field) gets created in background and stays while you are on the first page of the wizard - disallowing you to complete the wizard pressing "Finish" button (which is not grayed in this case). But at the moment I am not able to reproduce that one. I'll update the task with reproducible steps when hopefully I run into this again. Thanks Oh right, I am using 5.0.0 Final CDT build 5.0.0.200806171202
Created attachment 107121 [details] before resizing
Created attachment 107123 [details] after resizin
After trying to reproduce with new installation, scratching my head, and plenty of file copying found out that file org.eclipse.cdt.ui.prefs in my workspace (.metadata\.plugins\org.eclipse.core.runtime\.settings\) developed: wizard.preferred.toolchains=NULL and that phenomena is the cause of the anomalies.
See bug 292534 and bug 292535 for more anomalies.
(In reply to bug 323039 comment #0) > I am writing a template that uses my new Builder options feature for a Makefile > project. However, when I get the list of configurations, it includes a single > entry and it's a null pointer. Hmm, I wonder if this circumstance is causing phenomenon described in comment 3.
