On Wed, Oct 7, 2009 at 7:46 PM, Thomas Van Lenten thoma...@chromium.orgwrote:
It seems like another approach would be to use the target types to indicate
if the library or executable is for the host or native (ie-add types for
host vs. target), then you could use target_conditions to have
On Wed, Oct 7, 2009 at 7:06 PM, Antoine Labour pi...@google.com wrote:
If you don't care about gyp or cross-compiling, you can skip this message.
I've been experimenting with adding host support for cross-compiling into
gyp. By this, I mean being able to use the cross-compiler to build Chrome,
On Thu, Oct 8, 2009 at 9:49 AM, Evan Martin e...@chromium.org wrote:
On Wed, Oct 7, 2009 at 7:06 PM, Antoine Labour pi...@google.com wrote:
If you don't care about gyp or cross-compiling, you can skip this
message.
I've been experimenting with adding host support for cross-compiling into
On Thu, Oct 8, 2009 at 12:49 PM, Evan Martin e...@chromium.org wrote:
3- Well, it only works for the make build. The current patch probably
breaks
the scons one. XCode and MSVS should be mostly unaffected - but won't
supposrt this, which I don't think is a big deal.
How about 32/64-bit
It seems like another approach would be to use the target types to indicate
if the library or executable is for the host or native (ie-add types for
host vs. target), then you could use target_conditions to have different
flags.
TVL
On Wed, Oct 7, 2009 at 10:06 PM, Antoine Labour
