[SERVER-11658] Standardize on SCons 'Library' target for internal libraries Created: 11/Nov/13 Updated: 11/Jul/16 Resolved: 19/Nov/13 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Build |
| Affects Version/s: | None |
| Fix Version/s: | 2.5.5 |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Andrew Morrow (Inactive) | Assignee: | Unassigned |
| Resolution: | Done | Votes: | 0 |
| Labels: | build-system-cleanup | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Backwards Compatibility: | Fully Compatible |
| Participants: |
| Description |
|
For internal libraries (as opposed to the client libraries), we currently use a mix of the 'Library' and 'StaticLibrary' rules. By default, 'Library' means the same thing as 'StaticLibrary', so there is no difference. We should standardize and change all current calls to 'StaticLibrary' to 'Library', and reserve 'StaticLibrary' and 'SharedLibrary' for the explicit case where we wish to produce a library of particular type. This will also make it easier if, in the future, we ever want to inject particular behavior into our internal libraries, as we will only need to override the 'Library' target, but can leave 'StaticLibrary' and 'SharedLibrary' alone. |
| Comments |
| Comment by Githook User [ 08/Jan/14 ] |
|
Author: {u'username': u'acmorrow', u'name': u'Andrew Morrow', u'email': u'acm@10gen.com'}Message: |
| Comment by Githook User [ 19/Nov/13 ] |
|
Author: {u'username': u'acmorrow', u'name': u'Andrew Morrow', u'email': u'acm@10gen.com'}Message: |
| Comment by Githook User [ 19/Nov/13 ] |
|
Author: {u'username': u'acmorrow', u'name': u'Andrew Morrow', u'email': u'acm@10gen.com'}Message: |