docs/windows_incremental_linking.md - Issue 2549443004: Remove the docs for incremental linking on Windows.

Side by Side Diff

Use n/p to move between diff chunks; N/P to move between comments. Draft comments are only viewable by you.

Keyboard Shortcuts

	File
u :	up to issue
j / k :	jump to file after / before current file
J / K :	jump to next file with a comment after / before current file
	Side-by-side diff
i :	toggle intra-line diffs
e :	expand all comments
c :	collapse all comments
s :	toggle showing all comments
n / p :	next / previous diff chunk or comment
N / P :	next / previous comment
<Up> / <Down> :	next / previous line

	Issue
u :	up to list of issues
j / k :	jump to patch after / before current patch
o / <Enter> :	open current patch in side-by-side view
i :	open current patch in unified diff view

	Issue List
j / k :	jump to issue after / before current issue
o / <Enter> :	open current issue

Side by Side 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:

OLD	NEW
	(Empty)
1 # Windows incremental linking

2

3 Include in your `GYP_DEFINES`: `incremental_chrome_dll=1`. This turns on the

4 equivalent of Use Library Dependency Inputs for the large components in the

5 build.

6

7 And if you want faster builds, it would be best to include to

8 `component=shared_library` too unless you need a fully static link for some

9 reason.

10

11 Note that `incremental_chrome_dll=1` will probably not work on Visual Studio

12 2008 builds. It may not work on Visual Studio 2010 builds either (pamg couldn't

13 get it to work as of Nov 2012, encountering numerous link errors). You may have

14 to use [ninja](ninja_build.md), which has incremental linking on by default.

OLD	NEW

« no previous file with comments | « no previous file | no next file » | no next file with comments »