ww3877989 / google-breakpad

Automatically exported from code.google.com/p/google-breakpad
0 stars 0 forks source link

Build fails on MacOSX using xcodebuild #532

Open GoogleCodeExporter opened 9 years ago

GoogleCodeExporter commented 9 years ago
What steps will reproduce the problem?
1. get the latest code on MacOSX
2. run xcodebuild -sdk macosx 10.7 -project src/client/mac/Breakpad.xcodeproj 
-configuration Release -target
All GCC_VERSION=com.apple.compilers.llvmgcc42

What is the expected output? What do you see instead?
I expect the build to succeed, but it fails to compile:

  In file included from .../google-breakpad-read-only/src/client/mac/tests/BreakpadFramework_Test.mm:34:
  .../google-breakpad-read-only/src/client/mac/../../common/mac/testing/GTMSenTestCase.h:57:40: error: SenTestingKit/SenTestingKit.h: No such file or directory

What version of the product are you using? On what operating system?
Last Changed Rev: 1188
$ xcodebuild -version
Xcode 4.6.2
Build version 4H1003

Please provide any additional information below.

Original issue reported on code.google.com by psm...@nuodb.com on 28 May 2013 at 8:49

GoogleCodeExporter commented 9 years ago
Any update on this?

Original comment by parab...@gmail.com on 13 Oct 2013 at 9:11

GoogleCodeExporter commented 9 years ago
I'm also seeing this issue. I can build the chrome_23 branch just fine but not 
the trunk.

Original comment by rsuss...@gmail.com on 27 Nov 2013 at 12:50

GoogleCodeExporter commented 9 years ago
Note that the compile error is from this code in 
common/mac/testing/GTMSenTestCase.h:

#if (!GTM_IPHONE_SDK) || (GTM_IPHONE_USE_SENTEST)
#import <SenTestingKit/SenTestingKit.h>
#else
#import <Foundation/Foundation.h>
#ifdef __cplusplus
extern "C" {
#endif

Note that the top branch of the #if is being included but it looks like that is 
for iphone? Wouldn't we want the bottom branch? 

The compile errors go away if I hack in the following to the top of 
GTMSenTestCase.h:
#define GTM_IPHONE_USE_SENTEST 0
#define GTM_IPHONE_SDK 1

but then we end up with link errors. 

What's the proper fix? 

Original comment by rsuss...@gmail.com on 27 Nov 2013 at 12:55