[cdt-dev] why create a Binary (ICElement) only if it's in an output dire

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]

[cdt-dev] why create a Binary (ICElement) only if it's in an output directory?

From: John Cortell <john.cortell@xxxxxxxxxxxxx>
Date: Wed, 30 Jul 2008 12:55:56 -0500
Delivered-to: cdt-dev@xxxxxxxxxxx
List-archive: <https://dev.eclipse.org/mailman/private/cdt-dev>
List-help: <mailto:cdt-dev-request@eclipse.org?subject=help>
List-subscribe: <https://dev.eclipse.org/mailman/listinfo/cdt-dev>, <mailto:cdt-dev-request@eclipse.org?subject=subscribe>
List-unsubscribe: <https://dev.eclipse.org/mailman/listinfo/cdt-dev>, <mailto:cdt-dev-request@eclipse.org?subject=unsubscribe>

I'm trying to understand why we restrict the display of a binary(obj, dll, executable, lib, etc) as an expandable Binary object inour 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

Follow-Ups:
- RE: [cdt-dev] why create a Binary (ICElement) only if it's in an output directory?
  - From: Schaefer, Doug

Prev by Date: [cdt-dev] How to tell if a project is a library project
Next by Date: Re: [cdt-dev] Created make targets not saved to .cproject
Previous by thread: [cdt-dev] How to tell if a project is a library project
Next by thread: RE: [cdt-dev] why create a Binary (ICElement) only if it's in an output directory?
Index(es):
- Date
- Thread

Breadcrumbs