[SERVER-7023] Visual Studio rebuilds jsscan.c unnecessarily Created: 12/Sep/12 Updated: 18/Oct/22 Resolved: 30/Sep/12 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Build |
| Affects Version/s: | 2.2.0 |
| Fix Version/s: | 2.3.0 |
| Type: | Bug | Priority: | Minor - P4 |
| Reporter: | Tad Marshall | Assignee: | Tad Marshall |
| Resolution: | Done | Votes: | 0 |
| Labels: | VisualStudio | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Environment: |
Windows Visual Studio build |
||
| Backwards Compatibility: | Fully Compatible |
| Operating System: | Windows |
| Participants: |
| Description |
|
The Windows Visual Studio build rebuilds src/third_party/js-1.7/jsscan.c on every build of mongod.exe, mongos.exe, mongo.exe or test.exe, forcing a relink each time. Linking release builds takes forever, so this is really annoying. The problem is that we are unconditionally running jskwgen.exe to create jsautokw.h before starting the mongo {x}rebuild; we do this in a Pre-build step. This pre-build step should only recreate jsautokw.h when it is out-of-date, which will be "never" after it's been built once. Some custom JScript code should be able to do this test. |
| Comments |
| Comment by auto [ 30/Sep/12 ] |
|
Author: {u'date': u'2012-09-30T11:30:00-07:00', u'email': u'tad@10gen.com', u'name': u'Tad Marshall'}Message: For the Visual Studio builds, add a run_if_newer.js JScript file and use |