On 03/03/16 08:54, "Development on behalf of Thiago Macieira"
<development-bounces+lars.knoll=theqtcompany....@qt-project.org on behalf of
thiago.macie...@intel.com> wrote:
>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.
I guess he's using gcc 4.4 or something similar. One solution could be to add a
configure test and disable the module if it doesn't pass.
>
>> 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.
Agree, it shouldn't break the build.
Cheers,
Lars
_______________________________________________
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development
