On quinta-feira, 3 de março de 2016 07:50:51 PST Knoll Lars wrote: > >It matters because it breaks the build. > > > >Please remove it from the build. It's ok for it to be present, but don't > >compile it. > > > Which build are you talking about? The split source packages shouldn't have > a problem with this.
The convenience build for the "qt-everywhere" tarball. > For the unified source packages, we should probably simply skip the module > if the compiler is not c++11 compliant. Please see Stefan Walter's email. He got failures while using -std=c++0x, so this trick won't work. > But I see no reason to remove it > for compilers that can handle it. It's certainly not different from other > modules such as web engine that also have stricter requirements on > compilers or platforms than e.g. Qtbase. So long as they don't break the build. -- Thiago Macieira - thiago.macieira (AT) intel.com Software Architect - Intel Open Source Technology Center _______________________________________________ Development mailing list [email protected] http://lists.qt-project.org/mailman/listinfo/development
