Community
Participate
Working Groups
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.
Created attachment 179529 [details] Patch - applies to workspace.
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.
