On Tue, Oct 11, 2016 at 7:43 AM, Robert Iakobashvili <corobe...@gmail.com> wrote: > Hi, > Configuring Qt-5.6.2 at the recent Mac 10.12 > with C++-11 built versus SDK-12 as: > > ./configure -opensource -debug-and-release -c++std c++11 -qt-zlib > -qt-libpng -qt-libjpeg \ > -system-proxies -nomake tests -nomake examples -skip qtxmlpatterns -skip qt3d > \ > -skip qtactiveqt -skip qtcanvas3d -skip qtconnectivity -skip > qtdeclarative -skip qtlocation -skip qtscript \ > -skip qtsensors -skip qtserialport -skip qtwebchannel -skip > qtquickcontrols -skip qttranslations -skip qtenginio -skip > qtwebsockets \ > -skip qtwebengine -skip multimedia -no-sql-sqlite \ > -no-openssl -securetransport > > it builds and works properly, > but it is using the new C++ library libc++ > > clang -v > Apple LLVM version 8.0.0 (clang-800.0.38) > > When trying -no-c++11 flag, Qt was using the old C++ library libstdc++, > but clang was warning about its deprecation and suggesting to use > the new C++ library "available since 10.9 target". > > Qt in its turn sets 10.7 as the minimal deployment target. > > The question is at which minimal deployment target it will work? > 10.7? > 10.8? > 10.9?
Here's the exact warning when building with -no-c++11 flag clang: warning: libstdc++ is deprecated; move to libc++ with a minimum deployment target of OS X 10.9 And libc++.dylib was available at 10.7 - sort of contradiction. My problem is that I do not have a 10.7 or 10.8 targets. Your comments, thoughts would be appreciated. Kind regards, Robert _______________________________________________ Interest mailing list Interest@qt-project.org http://lists.qt-project.org/mailman/listinfo/interest