Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
RE: [cdt-dev] why create a Binary (ICElement) only if it's in an output directory?

Well, that's good, but it puts a damper on any other view that wants to display binaries. Such a view may display a targeted set of files and as such there is no need to try to limit the discovery of them to a particular directory (for performance reasons). This is the case for the Modules view.

It would be nice if the limiting logic wasn't that low in the stack. I'll need to figure out an alternate route for creating the Binary for the Modules view. I'll be doing this to fix a long standing issue: elements in the view are expandable only if they happen to be in an output directory of a project.


At 02:24 PM 7/30/2008, Schaefer, Doug wrote:
It's more like a performance enhancement. It's pretty expensive to
figure out whether a file is a binary or not so the output folder is
there to help speed it up if you need.


> -----Original Message-----
> From: cdt-dev-bounces@xxxxxxxxxxx
> [mailto:cdt-dev-bounces@xxxxxxxxxxx] On Behalf Of John Cortell
> Sent: Wednesday, July 30, 2008 1:56 PM
> To: cdt-dev@xxxxxxxxxxx
> Subject: [cdt-dev] why create a Binary (ICElement) only if
> it's in an output directory?
> I'm trying to understand why we restrict the display of a
> binary (obj, dll, executable, lib, etc) as an expandable
> Binary object in our views only if it's located in the output
> directory of a project.
> The restriction in the code is in CModelManager.create(IFile,
> IBinaryFile, ICProject). Same thing for static libraries (archives).
> Anyone know the reasoning behind this?
> John
> _______________________________________________
> cdt-dev mailing list
> cdt-dev@xxxxxxxxxxx
cdt-dev mailing list

Back to the top