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

Bug 326170

Summary:

BuildDescriptionManager should handle out-of-workspace build-resources

Product:

[Tools] CDT

Reporter:

Baltasar Belyavsky <bbelyavsky>

Component:

cdt-build-managed

Assignee:

Project Inbox <cdt-build-managed-inbox>

Status:

NEW ---

QA Contact:

Jonah Graham <jonah>

Severity:

major

Priority:

CC:

marcin.swiezawski, yevshif

Version:

8.0

Target Milestone:

---

Hardware:

OS:

Windows XP

Whiteboard:

Attachments:

Description	Flags
Patch - applies to workspace.	none
Patch in Git format	none

Description Baltasar Belyavsky

2010-09-24 11:41:28 EDT

Build Identifier: I20100608-0911 (Eclipse 3.6.0, CDT 7.0.0)

During incremental managed makefile builds, the BuildDescriptionManager deletes build-resources affected by the source-delta before 'make' runs.  This ensures that if the incremental build fails, any stale build-resources get deleted (like object files, and the build artifact file).  The problem is that only workspace build-resources are handled.  Our tool-chain supports redirecting the object-files and the build-artifact to anywhere on the filesystem, and all our build-resources which are outside of the workspace get ignored by the BuildDescriptionManager.

The attached patch adds handling of out-of-workspace build-resources.

Reproducible: Always

Steps to Reproduce:
This can't really be reproduced in CDT's GCC integration, because it does not support redirecting of build-artifacts to any arbitrary location.  But our tool-chain integration implements custom compiler output-name-providers and command-line-generators to support such redirection, and this use-case is very important to our users.

Comment 1 Baltasar Belyavsky

2010-09-24 11:43:01 EDT

Created attachment 179529 [details]
Patch - applies to workspace.

Comment 2 Baltasar Belyavsky

2012-05-31 12:30:04 EDT

Created attachment 216588 [details]
Patch in Git format

This is still a problem for us in the latest CDT (8.1.0). Is there any way this patch can be accepted?

Basically, we need to remove the assumption that all build-resources are always physically within the project directory. As I've mentioned, this assumption always holds true for the generic CDT-supplied GCC tool-chain implementation (because it does not allow routing of OBJ files to arbitrary locations). But for custom tool-chains which do have that support, this is a significant limitation...

I'm attaching an updated patch, in GIT format.