I think, you shall write custom module based on gcc module.
16 серп. 2015 09:06 "Stephan Gatzka" пише:
>
> > Well, you could put each file in its own Group and set
> cpp.commonCompilerFlags in each Group. I'm not suggesting you
> > actually do this due to the inconvenience, but it raises an inter
> Well, you could put each file in its own Group and set
> cpp.commonCompilerFlags in each Group. I'm not suggesting you
> actually do this due to the inconvenience, but it raises an interesting
> question about how we could potentially make
> something like this more usable.
>
> I think a new
> On Aug 15, 2015, at 9:16 AM, Stephan Gatzka wrote:
>
> Hi again!
>
> I miss a functionality I could easily achieve with cmake.
>
> To make a reproducible build with gcc, I need to call gcc with
> -frandom-seed=.
>
> As the man page of gcc states:
> "The number should be different for every
Hi again!
I miss a functionality I could easily achieve with cmake.
To make a reproducible build with gcc, I need to call gcc with
-frandom-seed=.
As the man page of gcc states:
"The number should be different for every file you compile"
The hash itself could be easily calculated with qbs.getH
Hi again!
I have to different directories with qbs files to build and run unit tests.
In both files the Project has an AutotestRunner { }. I can correctly build
and run these single qbs file.
Now I have a top level product that shall build an run all tests:
Project {
name: "all tests"
minimu
