> That’s correct. In Qt Creator master branch (i.e. 3.1 series) you can choose > the code model of different languages to use clang as a code model backend
What are the pros/cons of the two options for C++ as it currently stands? Regards, Rob. On 23 January 2014 07:55, Ziller Eike <[email protected]> wrote: > > On Jan 22, 2014, at 8:31 PM, Cristian Adam <[email protected]> wrote: > >> On 22.01.2014 19:35, ext Olivier Goffart wrote: >>> Regarding the use of libclang for the code model in Qt creator, there >>> was no progress in a long time. >> >> I think the clang code model branch has been merged into master: >> http://lists.qt-project.org/pipermail/qt-creator/2013-December/003028.html >> >> The next version of Qt Creator should have the clang code model as a >> plugin. > > That’s correct. In Qt Creator master branch (i.e. 3.1 series) you can choose > the code model of different languages to use clang as a code model backend, > or Qt Creator’s built-in. (If you pointed Qt Creator to libclang (and dev > headers) at Qt Creator compile time.) > > Br, Eike > > > -- > Eike Ziller, Senior Software Engineer - Digia, Qt > > Digia Germany GmbH, Rudower Chaussee 13, D-12489 Berlin > Geschäftsführer: Mika Pälsi, Juha Varelius, Tuula Haataja > Sitz der Gesellschaft: Berlin, Registergericht: Amtsgericht Charlottenburg, > HRB 144331 B > > _______________________________________________ > Development mailing list > [email protected] > http://lists.qt-project.org/mailman/listinfo/development _______________________________________________ Development mailing list [email protected] http://lists.qt-project.org/mailman/listinfo/development
