Urgh, that's annoying. I'm probably way too late to this discussion, but why isn't it sufficient to generate a chromium-ia32 and a chromium-x64 xcode project. That seems to be what is done on Linux where we are building and shipping both 64 bit and 32 bit versions?
-- Mads On Mon, May 17, 2010 at 1:40 PM, Mark Mentovai <[email protected]> wrote: > Xcode’s model doesn’t allow for per-architecture files. A file’s > either in or it’s out. You need to use #ifdefs to select it for > compilation. > > We can’t handle this at the GYP level because if we don’t present > everything to Xcode, we lose the ability to do universal builds. There > can’t be any meaningful concept of “v8_target_arch” on the Mac - in > order for everything to work properly, there can’t be any target > architecture selection until compilation time. > > Mark > > [email protected] wrote: >> Mark, I might be missing something here, but selecting the right files to >> compile seems like something the build tools should be able to handle? >> >> There should be no need to have ifdefs like these in every architecture >> dependent file so that they can all be included on every build no matter the >> architecture. >> >> Shouldn't gyp handle this? Include all the files in the project and do the >> right XCode thing to select the files to be compiled for various targets? > -- v8-dev mailing list [email protected] http://groups.google.com/group/v8-dev
