Community
Participate
Working Groups
Some of the change we did to accomodate the Indexer; A bug that makes it run two times when opening a project affected the binaryContainer(It does not show up) The Problem is since we no longer go through the resource deltas when a project is open, the BinaryContainer is no longer aware of new binaries in the project. This was fix in the head, and would like to move the fix to the branch(2.0.1). The fix is simple. The bug for example will affect the debugger when looking for executables. Any objections ?
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
