I took a quick look and:
- protobuf module - there's actually an open issue for this
(https://bugreports.qt.io/browse/QBS-563) so maybe you could take ownership ;)
- cuda, gsoap... potentially useful, but I'm not that familiar with them
- libs/... good, but set up in a way that seems fairly speci
On 21/11/2017 10:46 PM, Christian Kandeler wrote:
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
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 pro
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 provide, you may
even like to upstream them
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. Perhaps
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
_
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 # or cmake
> -DCMAK
