Chromium Code Reviews
chromiumcodereview-hr@appspot.gserviceaccount.com (chromiumcodereview-hr) | Please choose your nickname with Settings | Help | Chromium Project | Gerrit Changes | Sign out
(645)

Issue 81213003: Fix default ARCHS value for iOS project. (Closed)

Created:
7 years, 1 month ago by sdefresne
Modified:
7 years ago
Reviewers:
Nico, justincohen
CC:
gyp-developer_googlegroups.com, noyau (Ping after 24h)
Visibility:
Public.

Description

Fix default ARCHS value for iOS project. Xcode 5.0.0 only default to x86_64 when building Mac project, not iOS projects (since default target of iOS 5.0 does not supports 64-bits binaries). Patch by Sylvain Defresne <sdefresne@chromium.org>; BUG=chromium:322075 R=thakis@chromium.org Committed: https://code.google.com/p/gyp/source/detail?r=1798

Patch Set 1 #

Patch Set 2 : Simpler fix #

Patch Set 3 : Expand comment of _DefaultArch & add unittests #

Patch Set 4 : Add a file that does not compile in 64-bit #

Total comments: 8

Patch Set 5 : Addressing comments #

Unified diffs Side-by-side diffs Delta from patch set Stats (+109 lines, -29 lines) Patch
M pylib/gyp/xcode_emulation.py View 1 2 1 chunk +17 lines, -2 lines 0 comments Download
A + test/ios/app-bundle/TestApp/only-compile-in-32-bits.m View 1 2 3 4 1 chunk +3 lines, -2 lines 0 comments Download
A + test/ios/app-bundle/TestApp/only-compile-in-64-bits.m View 1 2 3 4 1 chunk +3 lines, -2 lines 0 comments Download
A + test/ios/app-bundle/test-archs.gyp View 1 2 3 4 4 chunks +40 lines, -23 lines 0 comments Download
A test/ios/gyptest-archs.py View 1 2 3 4 1 chunk +46 lines, -0 lines 0 comments Download

Messages

Total messages: 11 (0 generated)
sdefresne
Please take a look.
7 years, 1 month ago (2013-11-21 17:19:02 UTC) #1
Nico
Can you add a test for this?
7 years, 1 month ago (2013-11-22 01:40:07 UTC) #2
sdefresne
I've tested more, and in fact, Xcode does not default to x86_64 when building iOS ...
7 years ago (2013-11-25 14:38:06 UTC) #3
Nico
lgtm Sounds like this makes things better than before. https://codereview.chromium.org/81213003/diff/90001/test/ios/app-bundle/TestApp/only-compile-in-32-bits.m File test/ios/app-bundle/TestApp/only-compile-in-32-bits.m (right): https://codereview.chromium.org/81213003/diff/90001/test/ios/app-bundle/TestApp/only-compile-in-32-bits.m#newcode7 test/ios/app-bundle/TestApp/only-compile-in-32-bits.m:7: ...
7 years ago (2013-11-25 19:39:07 UTC) #4
Nico
(since this is a gyp CL, say "BUG=chromium:12345", to make clear this isn't for a ...
7 years ago (2013-11-25 19:39:53 UTC) #5
sdefresne
I've addressed all the comments. I don't have commit access, so could you commit the ...
7 years ago (2013-11-26 09:29:15 UTC) #6
justincohen
Committed patchset #5 manually as r1798 (presubmit successful).
7 years ago (2013-11-26 14:19:44 UTC) #7
scottmg
On 2013/11/26 14:19:44, justincohen wrote: > Committed patchset #5 manually as r1798 (presubmit successful). This ...
7 years ago (2013-11-26 20:31:32 UTC) #8
justincohen
Apologies. I can revert, but there's a CL in review here to disable the tests ...
7 years ago (2013-11-26 20:33:13 UTC) #9
scottmg
On 2013/11/26 20:33:13, justincohen wrote: > Apologies. I can revert, but there's a CL in ...
7 years ago (2013-11-26 20:40:01 UTC) #10
sdefresne
7 years ago (2013-11-26 22:49:22 UTC) #11
Message was sent while issue was closed.
On 2013/11/26 20:40:01, scottmg wrote:
> On 2013/11/26 20:33:13, justincohen wrote:
> > Apologies.  I can revert, but there's a CL in review here to disable the
tests
> > (the bots are running a very old Xcode)
> > 
> > https://codereview.chromium.org/88813002/
> > 
> > Should I revert or wait for this?
> 
> Oh that's fine, I didn't see the other CL.
> 
> (Also, I didn't mean for my comment to sound so passive-aggressive, I never
seem
> to remember that "git cl try" doesn't work, and that the magic --no_search is
> required. :)

Sorry, it's my fault. I only have the most recent version of Xcode installed,
and I did use "git cl try" (as strongly encouraged by the message [1] that I got
when I tried to run "git try") to run the bots, without realizing that it does
not
work.

Maybe this message should be made conditional on the fact that the repository
is chromium. Or "git cl try" should be fixed to work on gyp repository too.

[1]: https://codereview.chromium.org/74273002/patch/1/10001

Powered by Google App Engine
This is Rietveld 408576698