But your guess was right:

xcodebuild -showsdks
iOS SDKs:
        iOS 10.0                        -sdk iphoneos10.0

iOS Simulator SDKs:
        Simulator - iOS 10.0            -sdk iphonesimulator10.0

macOS SDKs:
        macOS 10.12                     -sdk macosx10.12

tvOS SDKs:
        tvOS 10.0                       -sdk appletvos10.0

tvOS Simulator SDKs:
        Simulator - tvOS 10.0           -sdk appletvsimulator10.0

watchOS SDKs:
        watchOS 3.0                     -sdk watchos3.0

watchOS Simulator SDKs:
        Simulator - watchOS 3.0         -sdk watchsimulator3.0



> Am 21.10.2016 um 16:11 schrieb Fabian Wein <fabian.w...@fau.de>:
> 
> Did not work:
> 
> -DCMAKE_OSX_SDK=macosx10.12
> 
> in cmake ../paraview-superbuild -DENABLE_cxx11=ON -DENABLE_hdf5=ON 
> -DENABLE_qt5=ON -Dsuperbuild_download_location=~/tmp/pvsb_downloads 
> -DCMAKE_OSX_ARCHITECTURES=x86_64 -DCMAKE_OSX_DEPLOYMENT_TARGET=10.12 
> -DCMAKE_OSX_SYSROOT=/Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX10.12.sdk
>  -DCMAKE_OSX_SDK=macosx10.12
> 
> results in 
> 
> erforming build step for 'qt5'
> Info: creating cache file 
> /Users/fwein/tmp/pvsb/superbuild/qt5/build/qtbase/.qmake.cache
> /Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/ranlib:
>  file: ../../../lib/libQt5Bootstrap.a(qvector.o) has no symbols
> /Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/ranlib:
>  file: ../../../lib/libQt5Bootstrap.a(qvector.o) has no symbols
> clang: warning: libstdc++ is deprecated; move to libc++ with a minimum 
> deployment target of OS X 10.9
> clang: warning: libstdc++ is deprecated; move to libc++ with a minimum 
> deployment target of OS X 10.9
> Makefile:13164: warning: overriding commands for target 
> `.moc/qeventdispatcher_cf.moc'
> Makefile:12994: warning: ignoring old commands for target 
> `.moc/qeventdispatcher_cf.moc'
> clang: warning: libstdc++ is deprecated; move to libc++ with a minimum 
> deployment target of OS X 10.9
> Undefined symbols for architecture x86_64:
>  "std::__1::__vector_base_common<true>::__throw_length_error() const", 
> referenced from:
>      void std::__1::vector<QMetaMethodBuilderPrivate, 
> std::__1::allocator<QMetaMethodBuilderPrivate> 
> >::__push_back_slow_path<QMetaMethodBuilderPrivate>(QMetaMethodBuilderPrivate&&)
>  in qmetaobjectbuilder.o
>      void std::__1::vector<QMetaPropertyBuilderPrivate, 
> std::__1::allocator<QMetaPropertyBuilderPrivate> 
> >::__push_back_slow_path<QMetaPropertyBuilderPrivate>(QMetaPropertyBuilderPrivate&&)
>  in qmetaobjectbuilder.o
>      void std::__1::vector<QMetaEnumBuilderPrivate, 
> std::__1::allocator<QMetaEnumBuilderPrivate> 
> >::__push_back_slow_path<QMetaEnumBuilderPrivate>(QMetaEnumBuilderPrivate&&) 
> in qmetaobjectbuilder.o
>  "void std::__1::__sort<std::__1::__less<int, int>&, int*>(int*, int*, 
> std::__1::__less<int, int>&)", referenced from:
>      QString::multiArg(int, QString const**) const in qstring.o
>      
> QSortFilterProxyModelPrivate::_q_sourceHeaderDataChanged(Qt::Orientation, 
> int, int) in qsortfilterproxymodel.o
>      QSortFilterProxyModel::removeRows(int, int, QModelIndex const&) in 
> qsortfilterproxymodel.o
>  "std::bad_alloc::bad_alloc()", referenced from:
>      qBadAlloc() in qglobal.o
>      QVector<QList<bool (*)(void**)> >::reallocData(int, int, 
> QFlags<QArrayData::AllocationOption>) in qglobal.o
> ld: symbol(s) not found for architecture x86_64
> clang: error: linker command failed with exit code 1 (use -v to see 
> invocation)
> make[6]: *** [../../lib/QtCore.framework/QtCore] Error 1
> make[5]: *** [sub-corelib-make_first] Error 2
> make[4]: *** [sub-src-make_first] Error 2
> make[3]: *** [module-qtbase-make_first] Error 2
> CMake Error at /Users/fwein/tmp/pvsb/superbuild/sb-qt5-build.cmake:43 
> (message):
>  Failed with exit code 2
> 
> I have the impressions that my other issues and comments on the gitlab issue 
> tracker are removed, so I stop posting reports of attempts there.
> 
> 
> 
>> CMAKE_OSX_SDK needs to be something like `macosx10.9`.  I forget the command 
>> to make XCode list the valid sdk versions available.  For your case I would 
>> guess `macosx10.12` is the correct value.  Qt looks up the path to the SDK 
>> from that string.
>> 
>> HTH,
>> Shawn
>> 
>> On Fri, Oct 21, 2016 at 7:07 AM, Fabian Wein <fabian.w...@fau.de> wrote:
>> I added a lot of the stuff to the issue tracker.
>> 
>> I’m currently lost with building qt5 on macOS 10.12. It’s a qmake issue, I 
>> tracked it down to
>> 
>> Creating qmake... Running configuration tests... Failed to process makespec 
>> for platform ‚macx-clang' Info: creating stash file 
>> /Users/fwein/tmp/pvsb/superbuild/qt5/build/qtbase/.qmake.stash Project 
>> ERROR: QMAKE_MAC_SDK can only contain short-form SDK names (eg. macosx, 
>> iphoneos) CMake Error at 
>> /Users/fwein/tmp/pvsb/superbuild/sb-qt5-configure.cmake:43 (message):
>> 
>> And it has a connection to the CMAKE_OSX_SDK I do not know what to set. 
>> CMAKE_OSX_SDK=macosx does not help.
>> 
>> Any qt5 configuration expert reading?
>> 
>>> Am 20.10.2016 um 17:18 schrieb Ben Boeckel <ben.boec...@kitware.com>:
>>> 
>>> On Thu, Oct 20, 2016 at 15:13:51 +0300, Gena Bug via ParaView wrote:
>>>> Now, with RC2, fontconfig warns me about blank section:
>>>> 
>>>> Fontconfig warning: line 160: blank doesn't take any effect anymore.
>>>> please remove it from your fonts.conf
>>> 
>>> We're now using a newer fontconfig, so the fontconfig may be newer than
>>> your system, so this is just fontconfig being more pedantic than your
>>> distro. Looking at fontconfig, there's no environment variable to
>>> suppress these warnings.
>>> 
>>>> However, that all -- no more new folder "fontconfig" in the running
>>>> directory. Thank you, that was really annoying!
>>>> 
>>>> Also, lib-dynload is still missing in the lib/python2.7
>>> 
>>> Ah, the superbuild didn't get bumped for that fix yet. I'll do that
>>> today.
>>> 
>>> --Ben
>>> _______________________________________________
>>> Powered by www.kitware.com
>>> 
>>> Visit other Kitware open-source projects at 
>>> http://www.kitware.com/opensource/opensource.html
>>> 
>>> Please keep messages on-topic and check the ParaView Wiki at: 
>>> http://paraview.org/Wiki/ParaView
>>> 
>>> Search the list archives at: http://markmail.org/search/?q=ParaView
>>> 
>>> Follow this link to subscribe/unsubscribe:
>>> http://public.kitware.com/mailman/listinfo/paraview
>> 
>> _______________________________________________
>> Powered by www.kitware.com
>> 
>> Visit other Kitware open-source projects at 
>> http://www.kitware.com/opensource/opensource.html
>> 
>> Please keep messages on-topic and check the ParaView Wiki at: 
>> http://paraview.org/Wiki/ParaView
>> 
>> Search the list archives at: http://markmail.org/search/?q=ParaView
>> 
>> Follow this link to subscribe/unsubscribe:
>> http://public.kitware.com/mailman/listinfo/paraview
>> 
> 
> _______________________________________________
> Powered by www.kitware.com
> 
> Visit other Kitware open-source projects at 
> http://www.kitware.com/opensource/opensource.html
> 
> Please keep messages on-topic and check the ParaView Wiki at: 
> http://paraview.org/Wiki/ParaView
> 
> Search the list archives at: http://markmail.org/search/?q=ParaView
> 
> Follow this link to subscribe/unsubscribe:
> http://public.kitware.com/mailman/listinfo/paraview

_______________________________________________
Powered by www.kitware.com

Visit other Kitware open-source projects at 
http://www.kitware.com/opensource/opensource.html

Please keep messages on-topic and check the ParaView Wiki at: 
http://paraview.org/Wiki/ParaView

Search the list archives at: http://markmail.org/search/?q=ParaView

Follow this link to subscribe/unsubscribe:
http://public.kitware.com/mailman/listinfo/paraview

Reply via email to