Open GoogleCodeExporter opened 9 years ago
Extensive discussion of this at http://code.google.com/p/chromium/issues/detail?
id=15924.
Original comment by sgk@chromium.org
on 6 Aug 2009 at 5:53
I guess I'l fix it myself. Taking the bug.
Original comment by maruel@chromium.org
on 9 Nov 2009 at 4:38
Go for it. I'm too mired in memory task force.
In case it's helpful: There two key hassles the last time I looked. Changes
to the
msvs generator and/or NaCl introduction revealed problems in how actions +
rules
execute custom scripts. For --generator-output= to work with minimal hassle,
we need
to cd back to the source directory to execute the script with the input file
names
all being expressed relative to the source script. The output file names have
to get
massaged to point back to the generator-output directory. Paths need to be
relative,
not absolute, so the entire morass is relocatable.
A complication for gyp development is that the Chrome production build uses
cygwin
for command execution but the test infrastructure doesn't, so there are
different
code paths involved GenerateExternalRule().
Original comment by sgk@chromium.org
on 9 Nov 2009 at 6:44
Sorry, up a layer in the stack. That last mention should be to
_PrepareActionRaw().
Original comment by sgk@chromium.org
on 9 Nov 2009 at 6:45
Just to mention that I got a quick patch for UNIX makefile generator:
http://groups.google.com/group/gyp-developer/browse_thread/thread/52fa6b688518c1
2b
Original comment by haohui....@gmail.com
on 12 Oct 2011 at 2:38
Original issue reported on code.google.com by
bradnel...@google.com
on 11 May 2009 at 10:38