docs/GypVsCMake.md - Issue 1292053003: Lots of documentation cleanup

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

Unified Diff: docs/GypVsCMake.md

Issue 1292053003: Lots of documentation cleanup (Closed) Base URL: https://chromium.googlesource.com/external/gyp@md-pages

Patch Set: update w/ note about "fetch gyp" Created 5 years, 4 months ago

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

Jump to:

Index: docs/GypVsCMake.md

diff --git a/docs/GypVsCMake.md b/docs/GypVsCMake.md

index b4aa3d90137a0b9667d3d62632d77ecc36c41d95..6d659a6123b661b55f68caff401d3a5b2c8ab7af 100644

--- a/docs/GypVsCMake.md

+++ b/docs/GypVsCMake.md

@@ -1,4 +1,4 @@

-# GYP vs. CMake #

+# vs. CMake

GYP was originally created to generate native IDE project files (Visual Studio, Xcode) for building [Chromium](http://www.chromim.org).

@@ -29,10 +29,8 @@ absent from cmake, but not strictly required for Chromium.

1. Ability to incrementally transition on Windows. It took us about 6 months

to switch fully to gyp. Previous attempts to move to scons had taken a long

time and failed, due to the requirement to transition while in flight. For a

-substantial period of time, we had a hybrid of checked in vcproj and

-gyp generated

-vcproj. To this day we still have a good number of GUIDs pinned in the

-gyp files,

+substantial period of time, we had a hybrid of checked in vcproj and gyp generated

scottmg 2015/08/13 23:06:41 80 col for these two I guess

+vcproj. To this day we still have a good number of GUIDs pinned in the gyp files,

because different parts of our release pipeline have leftover assumptions

regarding manipulating the raw sln/vcprojs. This transition occurred from

the bottom up, largely because modules like base were easier to convert, and

« no previous file with comments | « docs/Buildbot.md ('k') | docs/Hacking.md » ('j') | docs/Hacking.md » ('J')