[SERVER-20978] Use fast linking for Windows Debug builds Created: 16/Oct/15 Updated: 22/Apr/16 Resolved: 22/Apr/16 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Build |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Eric Milkie | Assignee: | DO NOT USE - Backlog - Platform Team |
| Resolution: | Won't Fix | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Backwards Compatibility: | Fully Compatible |
| Participants: |
| Description |
|
On VS2015 Update 1, we can use /DEBUG:FASTLINK on our Debug builds to improve link times and reduce the size of the PDB files. We can't do this for optimized/production builds, however, as we want the PDB files to contain all the debug info so that we can distribute them without the obj files. |
| Comments |
| Comment by Mark Benvenuto [ 22/Apr/16 ] |
|
Yes, that is correct. The pdb file has a link to the object files so you have to copy over ALL the object files for them to work. I have been experimenting with /DEBUG:FASTLINK in my VS 2015 patch builds, and saw bad stack traces as a result of this switch. The stack trace code will not crash with these partial pdb, but we will just not have useful information in them as a result. |
| Comment by Eric Milkie [ 21/Apr/16 ] |
|
I'm not sure that's a complete description of what the problem is. With fast linking you will still get a "single file pdb". |
| Comment by Mark Benvenuto [ 21/Apr/16 ] |
|
We also cannot do this on MCI at all, because even debug builders need a single file pdb. |