On Wed, Apr 3, 2013 at 11:21 AM, Jake Thomas Petroules
jake.petrou...@petroules.com
mailto:jake.petrou...@petroules.com wrote:
Can't you just set __MAC_OS_X_VERSION_MAX_ALLOWED to 1060 with the
10.8 SDK?
On 4/3/13 20:29 , Josh Faust wrote:
No, the Apple API headers don't use that to
On 4/4/13 12:24 , Tor Arne Vestbø wrote:
And passing -D__MAC_OS_X_VERSION_MAX_ALLOWED=1060 results clang building
with -triple x86_64-apple-macosx10.6.0.
Actually, strike that, the triple is set based on the
-mmacosx-version-min, so __MAC_OS_X_VERSION_MAX_ALLOWED is just a
figment of the
On 4/2/13 23:46 , Josh Faust wrote:
I've created https://bugreports.qt-project.org/browse/QTBUG-30487
I can provide a tarball of the 10.6 SDK for anyone who needs it to test.
It's semi-painful to extract from an old version of xcode.
Building against the 10.6 SDK relies on the Xcode version
The question is why you want to build against the 10.6 SDK?
Because it's recommended across the internet as the only way to
compile-time check that you're only using 10.6 APIs (and, despite what you
say, it does generally work). We started building Qt with it because
various configuration
Can't you just set __MAC_OS_X_VERSION_MAX_ALLOWED to 1060 with the 10.8 SDK?
--
Jake Petroules
Chief Technology Officer
Petroules Corporation · www.petroules.com
Email: jake.petrou...@petroules.com
On Apr 3, 2013, at 2:10 PM, Josh Faust jfa...@suitabletech.com wrote:
The question is why you
No, the Apple API headers don't use that to compile-out API based on the
max-allowed version. It's only for user code.
On Wed, Apr 3, 2013 at 11:21 AM, Jake Thomas Petroules
jake.petrou...@petroules.com wrote:
Can't you just set __MAC_OS_X_VERSION_MAX_ALLOWED to 1060 with the 10.8
SDK?
Previously it was possible to just pass '-sdk path' to the configure
script. That's no longer possible, due to changes in how the configure
script works. Is there any way to build against a custom SDK in 5.1?
Josh
___
Development mailing list
Actually, this seems to go beyond just using a custom SDK path. If I place
the 10.6 SDK alongside the others inside the Xcode application folder and
configure with:
./configure -developer-build -release -opensource -confirm-license -shared
-nomake examples -nomake demos -nomake docs -no-c++11
On Apr 2, 2013, at 9:51 PM, Josh Faust jfa...@suitabletech.com wrote:
Actually, this seems to go beyond just using a custom SDK path. If I place
the 10.6 SDK alongside the others inside the Xcode application folder and
configure with:
./configure -developer-build -release -opensource
Looks like it's a problem with using the g++ binary xcrun finds:
$ xcrun -sdk macosx10.6 g++ test.cpp -isysroot
/Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX10.6.sdk
-mmacosx-version-min=10.6 -o test
ld: library not found for -lstdc++
collect2: ld
I've created https://bugreports.qt-project.org/browse/QTBUG-30487
I can provide a tarball of the 10.6 SDK for anyone who needs it to test.
It's semi-painful to extract from an old version of xcode.
Josh
On Tue, Apr 2, 2013 at 2:17 PM, Josh Faust jfa...@suitabletech.com wrote:
Looks like it's
11 matches
Mail list logo
