[SERVER-33190] Add support for generating separate debug info as an emitted target Created: 08/Feb/18 Updated: 12/Jun/19 Resolved: 28/Feb/19 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Build |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | New Feature | Priority: | Major - P3 |
| Reporter: | Andrew Morrow (Inactive) | Assignee: | Andrew Morrow (Inactive) |
| Resolution: | Duplicate | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Sprint: | Dev Tools 2019-03-11 | ||||||||
| Participants: | |||||||||
| Description |
|
We currently create separate debug info manually by invoking objcopy while running the installBinary function. In order to allow the proposed tagging system to know which install targets should be associated with the debug files, we should re-organize this such that separate debug info files are emitted as part of calling .Program and .SharedLibrary. |
| Comments |
| Comment by Andrew Morrow (Inactive) [ 28/Feb/19 ] |
|
This feature was implemented as part of |