[Development] Qt Creatror can require a patched Clang build?

[Eike Ziller]

> On 10. Sep 2019, at 13:49, Lisandro Damián Nicanor Pérez Meyer <perezmeyer at gmail.com> wrote:
> 
> And by the way, is there any tag to relate a patch to the bug but not
> close it if it gets accepted?

Task-number:

(Only “Fixes:” closes the associated task)

> 
> On Tue, 10 Sep 2019 at 08:41, Lisandro Damián Nicanor Pérez Meyer
> <perezmeyer at gmail.com> wrote:
>> 
>> On Mon, 9 Sep 2019 at 18:20, Thiago Macieira <thiago.macieira at intel.com> wrote:
>>> 
>>> On Monday, 9 September 2019 14:07:59 PDT Lisandro Damián Nicanor Pérez Meyer
>>> wrote:
>>>> Is this acceptable? I really think it is not, but...
>>> 
>>> It's not. Requiring people to build LLVM + Clang, whcih is huge, is not
>>> something we should do.
>>> 
>>> Please work around.
>> 
>> In the meantime I propose this:
>> https://codereview.qt-project.org/c/qt-creator/qt-creator/+/273375
>> In this way our users will know that the plugin needs a specific patch
>> in clang. But better if we didn't. Or at very least the plugin wasn't
>> build at all, with a proper warning at build time.
> 
> 
> 
> -- 
> Lisandro Damián Nicanor Pérez Meyer
> http://perezmeyer.com.ar/
> http://perezmeyer.blogspot.com/
> _______________________________________________
> Development mailing list
> Development at qt-project.org
> https://lists.qt-project.org/listinfo/development

-- 
Eike Ziller
Principal Software Engineer

The Qt Company GmbH
Erich-Thilo-Straße 10
D-12489 Berlin
eike.ziller at qt.io
http://qt.io
Geschäftsführer: Mika Pälsi,
Juha Varelius, Mika Harjuaho
Sitz der Gesellschaft: Berlin, Registergericht: Amtsgericht Charlottenburg, HRB 144331 B