Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 313587

Summary: The "Paths and Symbols" window lacks an "Output Location" tab.
Product: [Tools] CDT Reporter: Barry Morris <barry.morris>
Component: cdt-build-managedAssignee: Project Inbox <cdt-build-managed-inbox>
Status: RESOLVED DUPLICATE QA Contact: Chris Recoskie <recoskie>
Severity: normal    
Priority: P3    
Version: 7.0   
Target Milestone: ---   
Hardware: PC   
OS: Linux   
Whiteboard:

Description Barry Morris CLA 2010-05-19 13:40:43 EDT 
Build Identifier: 20100218-1602

I want to put my ".a" and ".so" files someplace other than ../Release and I want Eclipse to do it for me in the "managed make" configuration.  Other IDEs let me place my binaries where I want (other than the default directories) so I assume Eclipse can/should also.

My problem is similar to message #523839 at http://www.eclipse.org/forums/index.php?t=selmsg&frm_id=80&mr=1&start=40&reply_count=0

Reproducible: Always

Steps to Reproduce:
1. Project | Properties | C/C++ General | Paths and Symbols
2. Observe only tabs "Includes", "Symbols", "Source Location", and "References"
3. Where is "Output Location" tab?   (Please!)
Comment 1 Andrew Gvozdev CLA 2010-05-19 14:26:48 EDT 
You are misinterpreting the purpose of "Output Location" tab. For unmanaged build CDT doesn't know which files are the product of the build and you specify those so CDT could treat them not as source files. For managed build MBS controls the files it creates so there is no need.

What you are requesting is to define location of build artifact and so this bug is a duplicate of bug 180451 or bug 300930. Take your pick.
Comment 2 Barry Morris CLA 2010-05-19 16:39:27 EDT 
(In reply to comment #1)
> You are misinterpreting the purpose of "Output Location" tab. For unmanaged
> build CDT doesn't know which files are the product of the build and you specify
> those so CDT could treat them not as source files. For managed build MBS
> controls the files it creates so there is no need.
> 
> What you are requesting is to define location of build artifact and so this bug
> is a duplicate of bug 180451 or bug 300930. Take your pick.

You are quite right! I read 180451 & 300930.  My "bug" would not have been written had I seen those two; I did look!  You were _very_ kind to respond so quickly.
Comment 3 Andrew Gvozdev CLA 2010-05-19 21:53:08 EDT 
OK, I am marking it as duplicate of bug 300930.

*** This bug has been marked as a duplicate of bug 300930 ***