Re: [QBS] Qbs IncrediBuild in QtCreator

2014-07-23 Thread Thomas Epting
> Why? The internal one would not be used for building. Of course you'd > lose the benefits of the integration and would need custom run > configurations and so on; that just follows from diverging from the > default workflow. Hmm ... that sounds feasible, but still inconvenient to some extend. I

Re: [QBS] Qbs IncrediBuild in QtCreator

2014-07-23 Thread Christian Kandeler
On 07/23/2014 05:01 PM, Thomas Epting wrote: > > If you really want to run the command line version of qbs, you'll have > > to use a different profile than the one you have opened your project > > with. Maybe clone the kit? > > I'm somehow unsure, how would that help? As far as I understand it,

Re: [QBS] Qbs IncrediBuild in QtCreator

2014-07-23 Thread Thomas Epting
> If you really want to run the command line version of qbs, you'll have > to use a different profile than the one you have opened your project > with. Maybe clone the kit? I'm somehow unsure, how would that help? As far as I understand it, we still would end with an internal buildgraph and an ext

Re: [QBS] Qbs IncrediBuild in QtCreator

2014-07-23 Thread Christian Kandeler
On 07/23/2014 04:18 PM, Thomas Epting wrote: > > > I'm not knowledgeable about Incredibuild at all, but any solution that > > > calls the qbs command line tool seems entirely wrong. > > > Why not just start Creator via ibconsole? > > > > While this works in theory, it has some major impac

Re: [QBS] Qbs IncrediBuild in QtCreator

2014-07-23 Thread Thomas Epting
> > I'm not knowledgeable about Incredibuild at all, but any solution that > > calls the qbs command line tool seems entirely wrong. > > Why not just start Creator via ibconsole? > > While this works in theory, it has some major impacts on usability. The > most important one is that your work

Re: [QBS] Qt, QtCreator and cpp.systemIncludePaths

2014-07-23 Thread Tobias Hunger
On Tuesday 22 July 2014 22:52:51 at-2500 wrote: > Also, I found that QtCreator doesn't add the cpp.systemIncludePaths to > the internal searchpaths for autocompletion of the #include statement > etc. This also prevents going into the header file using F2. > cpp.includePaths are searched. You are r

[QBS] Qt, QtCreator and cpp.systemIncludePaths

2014-07-23 Thread at-2500
Hi, I found that the Qt QBS module uses cpp.includePaths to add its include path to the compiler flags, while it should use cpp.systemIncludePaths. Why? Paths in cpp.systemIncludePaths are added to e.g. clang using -isystem/path/you/added (in gcc it uses the -I flag instead of -i). The system f