Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 341139 - provide a mechanism to suppress the compiling and linking of big.c.
Summary: provide a mechanism to suppress the compiling and linking of big.c.
Status: ASSIGNED
Alias: None
Product: RTSC
Classification: Technology
Component: Core (show other bugs)
Version: unspecified   Edit
Hardware: All All
: P3 enhancement (vote)
Target Milestone: ---   Edit
Assignee: Dave Russo CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-03-28 12:49 EDT by Alan DeMars CLA
Modified: 2012-01-10 16:56 EST (History)
2 users (show)

See Also:

Attachments
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 Alan DeMars CLA 2011-03-28 12:49:32 EDT 
Build Identifier: 3,21

This will allow custom libraries to include big.c in their build flow.

Reproducible: Always
Comment 1 Chris Ring CLA 2011-10-18 14:46:28 EDT 
If using configuro, the --generationOnly flag may provide what you're looking for.  Does that suffice?
Comment 2 Dave Russo CLA 2011-12-05 17:54:41 EST 
Alan is this still an issue?  Can we close this bug?
Comment 3 Alan DeMars CLA 2011-12-05 18:09:43 EST 
My thinking was that this would give us a simple path to achieving whole_program performance by including big.c in with the custom library sources.

Is there a corresponding flag in the Pkg.addConfiguration() API that suppresses the compile and link of the big.c file?