On Wednesday 03 December 2014 12:46:55 Sarajärvi Tony wrote: > Now would be the time to read this through, and comment if you have anything > to say about this ;)
Hi Tony > Default configs runs for all submodule builds: > > linux-arm-gnueabi-g++_Ubuntu_11.10_x86 -> to be moved to Ubuntu 14.04 > linux-g++_shadow-build_Ubuntu_11.10_x86 -> to be moved to Ubuntu 14.04 > > linux-g++_developer-build_qtnamespace_qtlibinfix_Ubuntu_11.10_x64 -> to be > removed Looks good, considering there's a namespace+infix left running below. > linux-g++_no-widgets_Ubuntu_12.04_x64 > > linux-android-g++_Ubuntu_12.04_x64 > linux-android_armeabi-g++_Ubuntu_12.04_x64 > linux-imx6-armv7a_Ubuntu_12.04_x64 > linux-qnx-armv7le_Ubuntu_12.04_x64 > linux-qnx-x86_Ubuntu_12.04_x64 > > linux-g++_developer-build_OpenSuSE_13.1_x64 > > linux-g++_developer-build_qtnamespace_qtlibinfix_RHEL65_x64 > > macx-clang_developer-build_qtnamespace_OSX_10.7 -> to be removed I don't see any other 10.7 remaining. Does this means we'll slowly stop supporting 10.7? I will not be sorry to see it go, but if it goes I promise you we'll break 10.7 support within one week (the forkfd work failed on 10.7 for unknown reasons and I will submit it with clear conscience as soon as the 10.7 it out of CI). > macx-clang_no-framework_OSX_10.8 > > macx-clang_developer-build_OSX_10.9 > > macx-ios-clang_OSX_10.9 > > macx-clang_developer-build_OSX_10.10 -> to be replaced by > clang_developer-build_qtnamespace_OSX_10.10 > > win32-mingw47_developer-build_qtlibinfix_Windows_7 -> to be replaced by > win32-mingw49_developer-build_qtlibinfix_Windows_7 > win32-mingw48_developer-build_qtlibinfix_opengl_Windows_7 -> to be moved to > nightly builds > > win32-msvc2010_Windows_7 -> to be removed > win32-msvc2010_developer-build_qtnamespace_Windows_7 > win32-msvc2010_developer-build_angle_Windows_7 -> to be removed > win32-msvc2010_opengl_dynamic_Windows_7 -> to be moved to windows 10 > eventually > > wince70embedded-armv4i-msvc2008_Windows_7 > > win64-msvc2012_developer-build_qtnamespace_Windows_81 -> to be moved to > nightly builds win64-msvc2013_developer-build_qtnamespace_Windows_81 > > winphone-arm-msvc2013_Windows_81 > > winrt-x64-msvc2013_Windows_81 Rest looks fine. > When building the whole Qt5 (not e.g. QtBase) we have these added already, > but we would change them as following: > > linux-g++_bin-pkg-config_Ubuntu_11.10_x86 -> to be moved to nighty builds > (state builds) linux-g++_static_Ubuntu_12.04_x64 > macx-clang_bin-pkg-config_OSX_10.7 -> to be moved to nighty builds > macx-clang_static_OSX_10.9 > win32-msvc2010_bin-pkg-config_Windows_7 -> to be moved to nightly builds > win32-msvc2010_static_Windows_7 -> to be moved to windows 10 eventually > > Also we might add RHEL5.8 to nightly builds if it looks like we have spare > time. > ------------------------------------------------------------------ > PRIVACY AND CONFIDENTIALITY NOTICE > This message and any attachments are intended only for use by the named > addressee and may contain privileged and/or confidential information. If > you are not the named addressee you should not disseminate, copy or take > any action in reliance on it. If you have received this message in error, > please contact the sender immediately and delete the message and any > attachments accompanying it. Digia Plc does not accept liability for any > corruption, interception, amendment, tampering or viruses occurring to this > message. ------------------------------------------------------------------ Can you drop this note from the message when posting to the mailing list.You've posted to a public mailing list and the email got archived all over the internet. -- Thiago Macieira - thiago.macieira (AT) intel.com Software Architect - Intel Open Source Technology Center _______________________________________________ Development mailing list Development@qt-project.org http://lists.qt-project.org/mailman/listinfo/development