Re: [Qbs] Licensing of my own QBS modules

2017-11-21 Thread Карелин Павел
21.11.2017 21:26, Карелин Павел пишет: 21.11.2017 20:03, Jake Petroules пишет: Hi Pavel, As the author and copyright holder, you're free to use whatever license you want. MIT is certainly a good choice. Ok, this is great! However, depending on the kind of functionality your modules

Re: [Qbs] Licensing of my own QBS modules

2017-11-21 Thread Jake Petroules
Hi Pavel, As the author and copyright holder, you're free to use whatever license you want. MIT is certainly a good choice. However, depending on the kind of functionality your modules provide, you may even like to upstream them to the Qbs project for inclusion in the official release.

[Qbs] Licensing of my own QBS modules

2017-11-21 Thread Карелин Павел
Hi, guys! I wrote several modules that slightly extend the functionality of QBS. I want to place them on GitHub, for using their in both open source and commercial projects. Under what license should I place my modules? Can I use a MIT license? -- BR, Pavel Karelin

Re: [Qbs] Tighter clang tooling integration

2017-11-21 Thread Christian Kandeler
On Tue, 21 Nov 2017 18:01:32 +1300 Christian Gagneraud wrote: > Qbs can generate a clang compilation database. > Some (most) clang-based tools are not multi-cpu aware. > > For example a typical use of clang-check is > cd repo.git > qbs generate -g clangdb profile:someprofile #