On Sat, Sep 24, 2016 at 9:00 AM, Thiago Macieira
wrote:
> It probably comes from the environment variables of the machine that built
> the
> package.
Indeed. Using my own Qt build resolves the issue (installed mkspec doesn't
contain the mentioned line either).
Thanks for the assistance!
___
On sábado, 24 de setembro de 2016 04:25:05 PDT Konstantin Shegunov wrote:
> Curiously enough, that line isn't present in the Qt's source for the same
> version I have from git. Is it possible it was inserted automatically on
> install, or whatever process is used for packaging the binaries for debi
On Sat, Sep 24, 2016 at 3:50 AM, Konstantin Shegunov
wrote:
> On Sat, Sep 24, 2016 at 3:23 AM, Thiago Macieira <
> thiago.macie...@intel.com> wrote:
>>
>> run qmake with -d -d switches and look for where that "-g -O2" is coming
>> from.
>
>
> The best I can tell it comes from this line:
> QMAKE_C
On Sat, Sep 24, 2016 at 3:23 AM, Thiago Macieira
wrote:
>
> run qmake with -d -d switches and look for where that "-g -O2" is coming
> from.
The best I can tell it comes from this line:
QMAKE_CXXFLAGS = -g -O2 -fdebug-prefix-map=/build/
qtbase-opensource-src-1gAkgj/qtbase-opensource-src-5.6.1+df
On sábado, 24 de setembro de 2016 00:37:54 PDT Konstantin Shegunov wrote:
> I'm building a module and what I observe is getting -g -O2 for
> CONFIG+=debug. One thing I was able to infer was that
> setting QMAKE_CXXFLAGS to nothing seems to solve it for me. I wouldn't even
> dream of speculating why
On Sat, Sep 24, 2016 at 1:35 AM, Allan Sandfeld Jensen
wrote:
>
> Maybe it is following Qt's configuration instead of the one you request
> locally.
Yes, that'd be my guess too. What I imagine is happening is that I have -O2
coming from the configure flags Qt was built with (in my case release,
On Friday 23 September 2016, Konstantin Shegunov wrote:
> On Fri, Sep 23, 2016 at 5:31 AM, Thiago Macieira
>
>
> wrote:
> > The flag is not passed to the build.
> >
> > Debug builds use -O0 on Linux.
>
> I'm building a module and what I observe is getting -g -O2 for
> CONFIG+=debug. One thing I
On Fri, Sep 23, 2016 at 5:31 AM, Thiago Macieira
wrote:
>
> The flag is not passed to the build.
>
> Debug builds use -O0 on Linux.
>
I'm building a module and what I observe is getting -g -O2 for
CONFIG+=debug. One thing I was able to infer was that
setting QMAKE_CXXFLAGS to nothing seems to sol
On sexta-feira, 23 de setembro de 2016 01:52:28 PDT Konstantin Shegunov wrote:
> Hello,
> What's the rationale of having -O2 for debug builds on Linux (g++)? As the
> compiler moves the assembly around it becomes hell stepping through with
> the debugger. Is the flag passed intentionally (and why)?
On Fri, Sep 23, 2016 at 2:19 AM, Giuseppe D'Angelo <
giuseppe.dang...@kdab.com> wrote:
>
> Hope this helps
>
It does, thanks! I wasn't talking about profiling, but your answer pointed
me in the right direction. Apparently I have a sneaky flag somewhere in my
build configuration which shouldn't be
Hi,
Il 23/09/2016 00:52, Konstantin Shegunov ha scritto:
> What's the rationale of having -O2 for debug builds on Linux (g++)? As
> the compiler moves the assembly around it becomes hell stepping through
> with the debugger. Is the flag passed intentionally (and why)?
This kind of builds ("profil
Hello,
What's the rationale of having -O2 for debug builds on Linux (g++)? As the
compiler moves the assembly around it becomes hell stepping through with
the debugger. Is the flag passed intentionally (and why)?
Kind regards.
___
Interest mailing list
I
12 matches
Mail list logo
