[SERVER-27378] Enabling the enterprise module should not require recompiling the world Created: 12/Dec/16 Updated: 05/Apr/17 Resolved: 06/Feb/17 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Build |
| Affects Version/s: | None |
| Fix Version/s: | 3.5.3 |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Andrew Morrow (Inactive) | Assignee: | Andrew Morrow (Inactive) |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Backwards Compatibility: | Fully Compatible |
| Sprint: | Platforms 2017-01-23, Platforms 2017-02-13 |
| Participants: |
| Description |
|
Enabling the enterprise module causes MONGO_ENTERPRISE_VERSION to be defined for every TU in the build, even if it has no effect. Much like we enable injecting support for individual third party libraries to reduce the scope of effects, we should make it possible to selectively inject awareness of the enterprise (or any other) module. This would make it much faster to switch between community and enterprise builds. |
| Comments |
| Comment by Githook User [ 06/Feb/17 ] |
|
Author: {u'username': u'acmorrow', u'name': u'Andrew Morrow', u'email': u'acm@mongodb.com'}Message: |
| Comment by Githook User [ 06/Feb/17 ] |
|
Author: {u'username': u'acmorrow', u'name': u'Andrew Morrow', u'email': u'acm@mongodb.com'}Message: |