googletest does not build with newer versions of Xcode (4.1/4.2) due to hardcoded sdk that are not available anymore

[GoogleCodeExporter]

What steps will reproduce the problem?
Try to build googletest with Xcode 4.1 or newer and it will fail mainly because 
osx10.4u sdk does not exist anymore.

The project files should use the default SDK from the machine, allowing them to 
build with newer SDK versions.

The most problems are from inside General.xcconfig:

// Default SDK and minimum OS version is 10.4
SDKROOT = $(DEVELOPER_SDK_DIR)/MacOSX10.4u.sdk
MACOSX_DEPLOYMENT_TARGET = 10.4
GCC_VERSION = 4.0

Usage of any of these line will break the build.

SDKROOT is supposed to be a key value, not a path and especially not two 
releases old sdk. Currently 10.4 and 10.5 are not delivered anymore. 
http://developer.apple.com/library/mac/#documentation/DeveloperTools/Reference/X
codeBuildSettingRef/1-Build_Setting_Reference/build_setting_ref.html

MACOSX_DEPLOYMENT_TARGET better not to specify it, this will allow to build on 
ancient and bleeding age systems.

GCC_VERSION = 4.0 will break the build because 4.0 is not a valid version with 
xcode4, better not to specify it because it will pickup the default compiler.

Original issue reported on code.google.com by sorin.sb...@gmail.com on 16 Aug 2011 at 1:49

[GoogleCodeExporter]

Removing those settings in will prevent developers from targeting Tiger and 
Leopard systems, which still comprise ~25% of the market. Instead, it's better 
to document the problem and ways for fixing it. I will update the README file 
and add an FAQ entry with explanations.

Original comment by vladlosev on 18 Aug 2011 at 11:05

• Changed state: Accepted
• Added labels: Component-Scripts, OpSys-OSX

[GoogleCodeExporter]

I am not sure where you got your market share numbers but mine are "quite" 
different. Here are some I found on the net that are 6 months: 
http://gigaom.com/apple/snow-leopard-goes-out-with-a-market-share-roar/ ... 6%

Original comment by sorin.sb...@gmail.com on 18 Aug 2011 at 11:14

[GoogleCodeExporter]

Updated the README file and added an FAQ entry to explain the issue an the 
workaround.

Original comment by vladlosev on 22 Aug 2011 at 11:08

• Changed state: Fixed