support output_dir generator flag in more generators

jasonbrianhall / gyp

Automatically exported from code.google.com/p/gyp

0 stars 0 forks source link

support output_dir generator flag in more generators #40

Open GoogleCodeExporter opened 9 years ago

GoogleCodeExporter commented 9 years ago

the make generator is the only one that supports -G output_dir=name, it 
would be nice to support it on the other generators that dictate a path (xcode 
currently doesn't so it might not need to honor this)

Original issue reported on code.google.com by thomasvl@chromium.org on 1 Jul 2009 at 6:59

GoogleCodeExporter commented 9 years ago

Original comment by thomasvl@chromium.org on 1 Jul 2009 at 7:00

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

GoogleCodeExporter commented 9 years ago

Original comment by sgk@chromium.org on 6 Aug 2009 at 6:30

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

GoogleCodeExporter commented 9 years ago

Original comment by sgk@chromium.org on 18 Aug 2009 at 8:07

Added labels: MSVS, SCons, Xcode

GoogleCodeExporter commented 9 years ago

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

Original comment by coldredl...@gmail.com on 23 Aug 2011 at 9:16

GoogleCodeExporter commented 9 years ago

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 elan.ruu...@gmail.com on 2 Jan 2013 at 8:26