Re: [Qbs] build graph and dependency visualisation

On 1/11/2017 11:02 PM, Christian Kandeler wrote: On Tue, 31 Oct 2017 12:42:33 +1300 Christian Gagneraud wrote: Is it possible to dump the build graph (eg for graphviz), There is the dump-nodes-tree command, which gives you a textual representation. You won't have much fun

Re: [Qbs] Passing unescaped flags to the linker

Hi, > I use the latest versions (Qt Creator 4.4.1 and QBS 1.9.1) available on > Windows. > I just configured a Kit with my ARM toolchain, created a minimal qbs > project that compile > and run the static analyzer. What I did was to set up scan-build as a compiler wrapper in my qbs file, so

Re: [Qbs] Passing unescaped flags to the linker

2017-11-02 11:19 GMT+01:00 Timur Kristóf : >> For instance I need to pass "--specs=nano.specs" to g++. If I put it >> in cpp.linkerFlags it does >> not work as qbs will escape it with "-Wl". I can put it in >> cpp.driverFlags, but then it get passed >> to every call to g++

Re: [Qbs] Passing unescaped flags to the linker

On Thu, 2 Nov 2017 11:19:11 +0100 Timur Kristóf wrote: > @Christian: > > >> Yes, that is a bit of a problem. We really need cpp.linkerDriverFlags with > >> the semantics "flags to pass only when linking using the compiler binary". > >> The need for that has been debated

Re: [Qbs] Passing unescaped flags to the linker

@Christian: >> Yes, that is a bit of a problem. We really need cpp.linkerDriverFlags with >> the semantics "flags to pass only when linking using the compiler binary". >> The need for that has been debated in the past, but I think the case is >> pretty clear now. Could you please create a task

Re: [Qbs] Passing unescaped flags to the linker

2017-11-01 11:09 GMT+01:00 Christian Kandeler : > > Yes, that is a bit of a problem. We really need cpp.linkerDriverFlags with > the semantics "flags to pass only when linking using the compiler binary". > The need for that has been debated in the past, but I think the