Bug 295772 - [Managed project] Binaries are not parsed when not in build directories
Summary: [Managed project] Binaries are not parsed when not in build directories
Status: NEW
Alias: None
Product: CDT
Classification: Tools
Component: cdt-core (show other bugs)
Version: 6.0.1   Edit
Hardware: All All
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: Project Inbox CLA
QA Contact: Jonah Graham CLA
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-11-20 20:25 EST by Marc-André Laperle CLA
Modified: 2020-09-04 15:23 EDT (History)
0 users

See Also:

Attachments
Screenshot of the problem (34.77 KB, image/png)
2009-11-20 20:36 EST, Marc-André Laperle CLA 		no flags Details
View All Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Marc-André Laperle CLA 2009-11-20 20:25:12 EST 
Using CDT 6.0.1,

When a binary is copied or imported in a managed project (See Bug 91622 comment 12 and 14), the file will not be seen as a binary. On the other hand, if I drag the file to a build directory (Debug, Release) it shows up as an executable. It looks like only resources in build directories are parsed. I noticed 'Output location' in the Makefile project properties > C/C++ General > Paths and symbols. Is the purpose of these locations to tell explicitly the parser where to look? Maybe the managed project has only the build directories as Output locations and there is no way to change it in the UI? 

Steps to reproduce: 
1. Create a managed project.
2. Copy an executable in the project directory or import an executable (in any directory except a build directory like Debug, Release...)
3. The file is seen as a normal file, not as a binary
Comment 1 Marc-André Laperle CLA 2009-11-20 20:36:37 EST 
Created attachment 152775 [details]
Screenshot of the problem

Notice how testBinary1 and 2 are not showing as binaries but testBinary3 and 4 do.