On 18 June 2018 at 20:58, Christian Kandeler <christian.kande...@qt.io> wrote: > On Mon, 18 Jun 2018 11:01:10 +1200 > Christian Gagneraud <chg...@gmail.com> wrote: > >> Last thing, Qbs has built-in support for different compilers/linkers, >> this is nice b/c I can just express my toolchian flags in a toolchain >> agnostic way, but... >> - Qbs will have to continuously catch up with the fast moving toolchain world >> - Users depend on Qbs core team to gain support for exotic compilers > > How so? You can just provide your own cpp backend, if you wish. Or provide a > patch to extend an existing one.
Sorry wrote the email in a rush, "Qbs core team" => Qbs developer. Of course qbs users can contribute, but users don't always have time/willing to dig into Qbs source code and hack it around. How can i provide my own backend? Do I have to write code, and build it against Qbs source tree? Or can it be provided via a local qbs file? Chris > > > Christian > _______________________________________________ > Qbs mailing list > Qbs@qt-project.org > http://lists.qt-project.org/mailman/listinfo/qbs _______________________________________________ Qbs mailing list Qbs@qt-project.org http://lists.qt-project.org/mailman/listinfo/qbs
