Tor Arne Vestbø c45595d648 Use tools from the SDK's toolchain instead of the ones in /usr/bin ... For Mac OS X we currently specify build tools without an absolute path, which means we end up using the ones in /usr/bin. This is wrong, we should be using the tools from the toolchain of the chosen SDK. For iOS we do specify an absolute path, by resolving the toolchain path in the iOS makespecs. To solve the situation on Mac OS X, we move the logic of resolving the toolchain path to sdk.prf, and share it between OSX and iOS. For configure we need to duplicate some of the logic from sdk.prf, as configure pulls out QMAKE_CC and QMAKE_CXX for running some initial tests and building qmake. The new macSDKify function also solves the issue of missing sysroot and deployment version in the flags. Change-Id: Ib1d239c9904cf3ccee5214b313cf6205869a1462 Reviewed-by: Oswald Buddenhagen <oswald.buddenhagen@digia.com>		2013-03-13 18:40:26 +01:00
..
default_post.prf	Initial import from the monolithic Qt.	2011-04-27 12:05:43 +02:00
default_pre.prf	Initial import from the monolithic Qt.	2011-04-27 12:05:43 +02:00
objective_c.prf	Initial import from the monolithic Qt.	2011-04-27 12:05:43 +02:00
rez.prf	Initial import from the monolithic Qt.	2011-04-27 12:05:43 +02:00
sdk.prf	Use tools from the SDK's toolchain instead of the ones in /usr/bin	2013-03-13 18:40:26 +01:00