Bug 1420355 - Don't link logalloc against the static runtime on Windows. r?njn draft
authorMike Hommey <mh+mozilla@glandium.org>
Tue, 28 Nov 2017 17:11:40 +0900
changeset 704800 47afa94a3fa4db110d22925d19108be7cbcf8f5a
parent 704194 5b33b070378ae0806bed0b5e5e34de429a29e7db
child 704801 ef8d52dd28a9a086e7eece3fca0da9a0a3e4e538
push id91252
push userbmo:mh+mozilla@glandium.org
push dateWed, 29 Nov 2017 00:22:21 +0000
reviewersnjn
bugs1420355
milestone59.0a1
Bug 1420355 - Don't link logalloc against the static runtime on Windows. r?njn This was never strictly required (for instance, DMD doesn't do that), and would make things harder with the subsequent changes.
memory/replace/logalloc/logalloc.mozbuild
--- a/memory/replace/logalloc/logalloc.mozbuild
+++ b/memory/replace/logalloc/logalloc.mozbuild
@@ -5,17 +5,16 @@
 # file, You can obtain one at http://mozilla.org/MPL/2.0/.
 
 SOURCES += [
     'FdPrintf.cpp',
     'LogAlloc.cpp',
 ]
 
 DisableStlWrapping()
-USE_STATIC_LIBS = True
 NO_PGO = True
 DEFINES['MOZ_NO_MOZALLOC'] = True
 # Avoid Lock_impl code depending on mozilla::Logger.
 DEFINES['NDEBUG'] = True
 DEFINES['DEBUG'] = False
 
 # Use locking code from the chromium stack.
 if CONFIG['OS_TARGET'] == 'WINNT':