Chromium Code Reviews
chromiumcodereview-hr@appspot.gserviceaccount.com (chromiumcodereview-hr) | Please choose your nickname with Settings | Help | Chromium Project | Gerrit Changes | Sign out
(409)

Unified Diff: docs/windows_incremental_linking.md

Issue 2549443004: Remove the docs for incremental linking on Windows. (Closed)
Patch Set: Created 4 years ago
Use n/p to move between diff chunks; N/P to move between comments. Draft comments are only viewable by you.
Jump to:
View side-by-side diff with in-line comments
Download patch
« no previous file with comments | « no previous file | no next file » | no next file with comments »
Expand Comments ('e') | Collapse Comments ('c') | Show Comments Hide Comments ('s')
Index: docs/windows_incremental_linking.md
diff --git a/docs/windows_incremental_linking.md b/docs/windows_incremental_linking.md
deleted file mode 100644
index 213741d68312320454125f37f6a963d50b7de53b..0000000000000000000000000000000000000000
--- a/docs/windows_incremental_linking.md
+++ /dev/null
@@ -1,14 +0,0 @@
-# Windows incremental linking
-
-Include in your `GYP_DEFINES`: `incremental_chrome_dll=1`. This turns on the
-equivalent of Use Library Dependency Inputs for the large components in the
-build.
-
-And if you want faster builds, it would be best to include to
-`component=shared_library` too unless you need a fully static link for some
-reason.
-
-Note that `incremental_chrome_dll=1` will probably not work on Visual Studio
-2008 builds. It may not work on Visual Studio 2010 builds either (pamg couldn't
-get it to work as of Nov 2012, encountering numerous link errors). You may have
-to use [ninja](ninja_build.md), which has incremental linking on by default.
« no previous file with comments | « no previous file | no next file » | no next file with comments »

Powered by Google App Engine
This is Rietveld 408576698