| Summary: | CVS project wizard doesn't finish after 'internal' C++ project wizard | ||
|---|---|---|---|
| Product: | [Tools] CDT | Reporter: | Daniel van der Velde <contact> |
| Component: | cdt-core | Assignee: | Project Inbox <cdt-core-inbox> |
| Status: | RESOLVED DUPLICATE | QA Contact: | |
| Severity: | normal | ||
| Priority: | P3 | ||
| Version: | 5.0 | ||
| Target Milestone: | --- | ||
| Hardware: | PC | ||
| OS: | Windows XP | ||
| Whiteboard: | |||
|
Description
Daniel van der Velde
Sounds similar to bug 107343. Can you reproduce this bug reliable? Can you provide exact sequence of your actions? Also I've seen some anomalies described in bug 240374. Can you check .metadata\.plugins\org.eclipse.core.runtime\.settings\org.eclipse.cdt.ui.prefs, if there is entry wizard.preferred.toolchains=NULL? In fact, it's the exact same problem as bug 107343 making this bug a duplicate. However, the steps I did were the following: - New project: 'Projects from CVS' - Use existing repository location, select it and 'next' - Use an existing module, select it and 'next' - Checkout as project configured using the New Project Wizard, 'next' - By default, 'HEAD' tag is selected, so just 'Finish' - Select 'C++ Project' and 'next' - Type project name, select 'static library'/MinGW and 'next' - By default, the Debug and Release configurations are selected, so just 'Finish' At this point I see the project being created in the Project Explorer, but the 'CVS select tag' window remains on screen and no files are being checked out. I noticed that when you select 'Advanced settings...' from the last dialog (Select Configurations) and Cancel it immediately and then 'Finish', it works correctly (project created and files checked out). For completeness, the entry 'wizard.preferred.toolchains=NULL' is NOT present in the file you describe. Also, note that the workspace I use with Ganymede CDT now, was originally created by the Europa winter edition. Lastly, originally I described that C projects work and C++ projects don't. I now found them to react identically. I've tested a lot longer now. Marking as duplicate *** This bug has been marked as a duplicate of bug 107343 *** |