support output_dir generator flag in more generators about gyp

[GoogleCodeExporter]

Original comment by [email protected] on 1 Jul 2009 at 7:00

• Added labels: Type-Enhancement
• Removed labels: Type-Defect

[GoogleCodeExporter]

Original comment by [email protected] on 6 Aug 2009 at 6:30

• Added labels: Priority-High
• Removed labels: Priority-Medium

[GoogleCodeExporter]

Original comment by [email protected] on 18 Aug 2009 at 8:07

• Added labels: MSVS, SCons, Xcode

[GoogleCodeExporter]

Node.js would also like this change. Is it possible to do with MSVS?

Original comment by [email protected] on 23 Aug 2011 at 9:16

[GoogleCodeExporter]

note that -G output_dir is a bit buggy. for chromium build deps (.d/.raw) are 
placed into wrong dir (but things seem to work otherwise, i.e it's wrong in all 
places symmetrically)

so i have chromium-browser-24.0.1312.45 build with:

python build/gyp_chromium \
    --format=make \
    -Goutput_dir=../out \
    build/all.gyp \
...

which results such dirs:
$ du -s out/Release/ 
720M    out/Release/

$ du -s out/Release/out/Release/
330M    out/Release/out/Release/

the second dir (out/Release/out/Release) contains .d and .raw files:
$ find out/Release/out/Release/ -type f|sed -re 's/.+\.([^.]+)$/\1/'|sort -u
d  
raw

Original comment by [email protected] on 2 Jan 2013 at 8:26