Open GoogleCodeExporter opened 9 years ago
This will be fairly involved. Should probably be done in conjunction with
extracting
Cygwin in general from the Chromium build.
Original comment by sgk@chromium.org
on 6 Aug 2009 at 5:24
Original comment by sgk@chromium.org
on 18 Aug 2009 at 8:10
Is this still valid? I use gyp without cygwin all the time.
Original comment by mal@chromium.org
on 18 Jun 2010 at 3:46
Sadly this is still valid.
Gyp has a dependency on the quasi-hermetic copy of cygwin checked into chromium
third_party.
So when you build, cygwin gets used a little bit.
It's not too much of a problem for chrome, as it requires cygwin for perl and
gcc -E, and make anyway.
The mozc guys literally last week checked this same copy of cygwin into p4 so
that they could use gyp inside.
It also leads to a certain amount of escaping madness in the bowels of
actions/rules, but really the plan with that was to be more strict about what
an action can look like.
Original comment by bradnelson@google.com
on 18 Jun 2010 at 4:04
Original comment by yukawa@chromium.org
on 23 Nov 2013 at 5:31
Original issue reported on code.google.com by
bradnel...@google.com
on 26 Apr 2009 at 10:53