Does anyone think about we can use cross compilation on Linux.
e.g. on Ubuntu 12.04, the mingw-w64 4.6.3 can works well with Qt.
It will fast, and can use make -j option.
But it can't run the QTest (maybe? I am not sure).
2012/9/11 K. Frank <[email protected]>
> Hai Kai!
>
> On Tue, Sep 11, 2012 at 4:10 AM, <[email protected]> wrote:
> >> -----Original Message-----
> >> [...]
> >> Does anyone else see the slowness when first executing "run"
> >> when debugging a Qt gui application with gdb?
> >>
> >> Can anyone proactively confirm that the slowness does not occur with
> some
> >> specific mingw-w64 build (preferably 4.7.0 or later) when using gdb to
> debug
> >> a Qt gui application built with that mingw-w64 build? If so, what
> mingw-w64
> >> build would that be?
> >
> > I just tried debugging a basic Qt console application with both
> mingw64-gcc-4.7.1-2-rubenvb and Mingw-builds-4.7.1 (both 64 bit native) in
> Qt Creator: The gdb from Ruben's build is indeed much slower. It takes 12
> seconds from startup to hitting a breakpoint in main.cpp, compared to 4
> seconds with the gdb from niXman. Digging further, the `-break-insert
> "\"main.cpp\":5"` that's executed on startup from Ruben's build takes 6,7
> seconds to return, while it's only 1,4 seconds for mingw-builds. But we're
> sending the commands interleaved, so it might be that the -break-insert
> response is delayed by other commands, too ...
>
> Thank you for the feedback.
>
> It sounds like you are seeing some slowness with Ruben's build, but
> nothing on the scale I'm seeing. (As I mentioned, it takes minutes
> for my application to launch after executing the gdb "run" command.)
>
> Would you be able to try your test with a simple Qt gui application?
>
> Also, how is your application built? In my case, I built Qt with the
> same mingw-w64 compiler, and built it "out of the box," in that I used
> all of the Qt default build configuration settings. My Qt application
> is also an "out of the box" build, in that I don't use any non-default
> setting (other than adding "CONFIG += console" so that diagnostic
> messages will be visible.)
>
> > So yes, something's fishy here. Both are using a quite similar gdb
> version: 7.5.50.20120816-cvs (rubenv's) vs 7.5 (mingw-builds). The only
> other difference from the log is that rubenv's gdb also prints some
> '=cmd-param-changed,param="' messages, while mingw-builds does not.
>
> What log is this? I haven't notices gdb emitting any unexpected
> messages, but I'd be glad to look if this might be a hint about
> something.
>
> > Regards
> >
> > Kai
>
> Thanks for checking this.
>
>
> K. Frank
>
>
> ------------------------------------------------------------------------------
> Live Security Virtual Conference
> Exclusive live event will cover all the ways today's security and
> threat landscape has changed and how IT managers can respond. Discussions
> will include endpoint security, mobile security and the latest in malware
> threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
> _______________________________________________
> Mingw-w64-public mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/mingw-w64-public
>
--
Best Regards
Yuchen
------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and
threat landscape has changed and how IT managers can respond. Discussions
will include endpoint security, mobile security and the latest in malware
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
_______________________________________________
Mingw-w64-public mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/mingw-w64-public
