Bugzilla – Full Text Bug Listing
| Summary: | RFE: make Binaries folder use build directory instead of assuming | ||
|---|---|---|---|
| Product: | [Tools] CDT | Reporter: | Jeff Johnston <jjohnstn> |
| Component: | cdt-build | Assignee: | cdt-build-inbox <cdt-build-inbox> |
| Status: | CLOSED INVALID | QA Contact: | Andrew Gvozdev <angvoz.dev> |
| Severity: | normal | ||
| Priority: | P3 | CC: | cdtdoug, malaperle |
| Version: | 7.0.2 | ||
| Target Milestone: | --- | ||
| Hardware: | PC | ||
| OS: | Linux | ||
| Whiteboard: | |||
The binaries search uses the Output Folders setting in the project. What does it look like in these projects? (In reply to comment #1) > The binaries search uses the Output Folders setting in the project. What does > it look like in these projects? The Output Folders under Paths and Symbols is set correctly. With a little experimentation, I found that if I clean and rebuild, it works fine. This problem occurs just after I add a new configuration and set it active so my initial guess as to what was happening is incorrect. This appears to be a bug somewhere. The sequence is: Create an Autotools Hello World project. Let it build. You will find the Binaries folder. Go to Project Properties and create a new configuration. Set it active. Apply, close, and rebuild. Binary folders will be gone. Output Folder will be set properly and so will the Build directory. Clean and rebuild, Binaries folder reappears. Interesting. Definitely sounds like a bug. Maybe a missing event. I'm going to close this and open a new bug. |
The autotools plug-in uses configurations to specify multiple autotools configurations (one to one mapping). The default autotools configuration builds in the top-level directory. When built, the CDT correctly finds the resulting binary and puts it in the Binaries folder. However, when a 2nd or more configuration is added, autotools uses the configuration name to form a build-${configname} directory where configname may be massaged to replace blanks, etc... with underscores. A build occurs successfully, but the CDT is unable to find the binary and so no Binaries folder shows up. With some experimentation, renaming the build-XXXX directory to XXXX causes the Binaries folder to appear. It appears that somewhere the build directory is assumed to be the configuration name though it doesn't seem to occur when the top-level directory is used. This RFE requests that the code to build the Binaries folder use the current known build directory rather than making the assumption.