Re: [Qbs] Licensing of my own QBS modules
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 specific to your system. Could be useful if made more general I'm curious about your need for the functions in GccUtl. Why do you need the full path to libstdc++.a? And why gcc-ar instead of ar? It's possible we might want to make this configurable in Qbs, since there's an llvm-ar as well and there's presumably reasons a user might want to use the toolchain archiver vs the system archiver (same with the assembler). > On Nov 21, 2017, at 10:26 AM, Карелин Павел wrote: > > > > 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 to the Qbs project for inclusion in the >> official release. Perhaps you could upload the modules and we can take a >> look and see if it's a fit? > Xm, I do not think that you will find in my modules that it is really > valuable :) These are just small utilities. I did not intend to publish > them, but so were the circumstances. > The modules are attached. > > -- > Pavel. > > P.S. > I work in the Russian-language segment, so all comments are in Russian. If an > incredible thing happens, and you like something, then you are ready to make > explanations in English. > >> >> Cheers. >> >>> On Nov 21, 2017, at 3:10 AM, Карелин Павел wrote: >>> >>> 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 >>> >>> >>> ___ >>> Qbs mailing list >>> Qbs@qt-project.org >>> http://lists.qt-project.org/mailman/listinfo/qbs > > -- Jake Petroules - jake.petrou...@qt.io The Qt Company - Silicon Valley Qbs build tool evangelist - qbs.io ___ Qbs mailing list Qbs@qt-project.org http://lists.qt-project.org/mailman/listinfo/qbs
Re: [Qbs] Tighter clang tooling integration
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 profile:someprofile # or cmake
-DCMAKE_EXPORT_COMPILE_COMMANDS=ON find path/to/some/code -name
'*.cpp' | xargs clang-check -analyze -p=someprofile
As a side note, in my case CMake generate one database per "module"
(lib, app, ...), whereas qbs generate a single database for the whole
project. I do prefer the single database right now, but the one database
per Qbs product could be interested too.
The plugin could be improved by adding an optional product name on the
command line.
There are a few annoying things with this: - First you need to give
clang-check which file you want to check - clang-check will process
all the files one after another, even if you have multi CPU
This one you can probably work around, e.g. using GNU parallel.
Thanks for the tips! I wasn't aware of this one, maybe that's all I need
(i'm looking for a simple solution).
- find path/to/some/code -name '*.cpp' might retun files that
should not be compiled.
Wouldn't it be nice if we could ask qbs to run a clang-based tools
on all the source files and with proper load distribution?
Is this something that looks doable? Is it even wanted?
This has come up before. It looked deceptively tempting at first to
just set the compiler to the clang tool and then "build" as normal,
but upon closer inspection, there were some issues. The most obvious
one would be that you'd have to somehow stop after the "compile"
step, but there were others as well (I forgot the details). If you
Agree, it doesn't seems like the right approach even if sounds "easy" at
first.
play around a bit in that area (perhaps with a dedicated module?),
you'll probably get more insight into where the problems lie.
I could maybe use a custom Rule item, one that "transform" every .cpp
file into, say a .clazy file (output of clazy on the .cpp file).
But then i would have to tell qbs that i want a "master" file that
depends on all the individual '.clazy' files.
This still looks like a hack.
Can't stop thinking of a 'qbs for-each-cpp somecommand --someflag {}'
(similar to the 'find' and 'git for-each' commands)
Chris
___
Qbs mailing list
Qbs@qt-project.org
http://lists.qt-project.org/mailman/listinfo/qbs
Re: [Qbs] Licensing of my own QBS modules
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 provide, you may even like to upstream them to the Qbs project for inclusion in the official release. Perhaps you could upload the modules and we can take a look and see if it's a fit? Xm, I do not think that you will find in my modules that it is really valuable :) These are just small utilities. I did not intend to publish them, but so were the circumstances. The modules are attached. -- Pavel. P.S. I work in the Russian-language segment, so all comments are in Russian. If an incredible thing happens, and you like something, then you are ready to make explanations in English. Sorry: "I" are ready to make explanations in English. Cheers. On Nov 21, 2017, at 3:10 AM, Карелин Павел wrote: 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 ___ 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
Re: [Qbs] Licensing of my own QBS modules
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 to the Qbs project for inclusion in the official release. Perhaps you could upload the modules and we can take a look and see if it's a fit? Xm, I do not think that you will find in my modules that it is really valuable :) These are just small utilities. I did not intend to publish them, but so were the circumstances. The modules are attached. -- Pavel. P.S. I work in the Russian-language segment, so all comments are in Russian. If an incredible thing happens, and you like something, then you are ready to make explanations in English. Cheers. On Nov 21, 2017, at 3:10 AM, Карелин Павел wrote: 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 ___ Qbs mailing list Qbs@qt-project.org http://lists.qt-project.org/mailman/listinfo/qbs QbsExt.tar.gz Description: application/gzip ___ Qbs mailing list Qbs@qt-project.org http://lists.qt-project.org/mailman/listinfo/qbs
Re: [Qbs] Licensing of my own QBS modules
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 you could upload the modules and we can take a look and see if it's a fit? Cheers. > On Nov 21, 2017, at 3:10 AM, Карелин Павел wrote: > > 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 > > > ___ > Qbs mailing list > Qbs@qt-project.org > http://lists.qt-project.org/mailman/listinfo/qbs -- Jake Petroules - jake.petrou...@qt.io The Qt Company - Silicon Valley Qbs build tool evangelist - qbs.io ___ Qbs mailing list Qbs@qt-project.org http://lists.qt-project.org/mailman/listinfo/qbs
[Qbs] Licensing of my own QBS modules
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 ___ Qbs mailing list Qbs@qt-project.org http://lists.qt-project.org/mailman/listinfo/qbs
Re: [Qbs] Tighter clang tooling integration
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 > -DCMAKE_EXPORT_COMPILE_COMMANDS=ON > find path/to/some/code -name '*.cpp' | xargs clang-check -analyze > -p=someprofile > > There are a few annoying things with this: > - First you need to give clang-check which file you want to check > - clang-check will process all the files one after another, even if you > have multi CPU This one you can probably work around, e.g. using GNU parallel. > - find path/to/some/code -name '*.cpp' might retun files that should not > be compiled. > > Wouldn't it be nice if we could ask qbs to run a clang-based tools on > all the source files and with proper load distribution? > > Is this something that looks doable? Is it even wanted? This has come up before. It looked deceptively tempting at first to just set the compiler to the clang tool and then "build" as normal, but upon closer inspection, there were some issues. The most obvious one would be that you'd have to somehow stop after the "compile" step, but there were others as well (I forgot the details). If you play around a bit in that area (perhaps with a dedicated module?), you'll probably get more insight into where the problems lie. Christian ___ Qbs mailing list Qbs@qt-project.org http://lists.qt-project.org/mailman/listinfo/qbs
