Summary: | BinaryContainer not showing up | ||
---|---|---|---|
Product: | [Tools] CDT | Reporter: | Alain Magloire <alain> |
Component: | cdt-core | Assignee: | Alain Magloire <alain> |
Status: | VERIFIED FIXED | QA Contact: | |
Severity: | normal | ||
Priority: | P3 | CC: | aniefer, cdtdoug, dave.daoust, gheorghe, twolff |
Version: | 2.0 | ||
Target Milestone: | 2.0.1 | ||
Hardware: | PC | ||
OS: | Linux | ||
Whiteboard: |
Description
Alain Magloire
2004-08-27 10:31:52 EDT
I'm not seeing missing Binaries folder when I close and open a project. Do you have the steps? Managed or Std? I'm looking for the scenario when the executable exists, but not the Binaries folder, I guess. I tried turning off autobuild, then clean, so no Binaries folder nor exec exists, close project, turn on autobuild, open project, but then I see the exec and Binaries folder. - Create a std make project, say "bla" - create another folder inside that project, say "bla/folder" - copy a binary to it "bla/folder/myexec" see the binary container appearing (the little blue losange) - close the project - reopen the project No binary container. TWolff, You asked for the steps and it was added to the PR. I would like to close this today. Any other objections? Ok I can reproduce now... it's a bug :) Alain, it is your call. If you want to fix this, we have no problems doing a re-spin and we will re-validate the build. Please let us (andrew :-) know as soon as it is fixed (or if you decide it shouldn't be) and we will "turn the crank". > Alain, it is your call. Thanks, the fix is a one liner. And it will help the debug side, i.e the debugger relies on this container to find binaries/executables. Fix applied to the branch. > Please let us (andrew :-) know as soon as it is fixed Andrew, it is in. Thanks, sorry for the last minutes chaos. Tanya has verified this one, marking it so |