LinkedIn
Andy Fillebrown 님이 LinkedIn 1촌 신청 메일을 보냈습니다.
--
LinkedIn에서 제 비즈니스 인맥에 추가하고 싶습니다.
Andy Fillebrown 님의 초대 메일 수락
http://www.linkedin.com/e/fvmjka-hxmdfep2-k/o0JrIwFC-cwpD35mwa4KmfJallSplZWGoGQHsNeF/blk/I284350178_246
On Thu, Aug 1, 2013 at 12:06 PM, Laszlo Papp wrote:
> On Thu, Aug 1, 2013 at 4:45 PM, Thiago Macieira > wrote:
>
>> On quinta-feira, 1 de agosto de 2013 09:59:44, Laszlo Papp wrote:
>> > I would be personally more than happy for scene graph to become compact,
>> > i.e. qml and qtquick being a se
I don't build the WebKit module anymore, but when I did I made sure the Qt
source tree was in a directory with a very short name, like D:\Qt-5.1.0.
That way the command line stays small enough to make it through the build.
Cheers,
~ andy.f
On Thu, May 16, 2013 at 4:05 PM, Bruno Souza Cabrral
Hi Yang,
I've had similar issues in the past. After a lot of head scratching I
discovered the error was due to a very long command line in the
QtWebKit make file. The only way I could figure out to work around
the problem was to move the Qt source tree closer to the root
directory of the hard dr
On Sat, Apr 21, 2012 at 10:06 PM, andy fillebrown
wrote:
>> my bad, fixed:
>> https://builds.qt-project.org/job/gdb-windows/53/artifact/build-creator-gdb-mingw/qtcreator-gdb-7.4-MINGW32_NT-6.1-i686.tar.gz
>
> This works well. No breakpoint or callstack issues. Unfortunatel
On Sat, Apr 21, 2012 at 11:38 AM, wrote:
>
> On Apr 21, 2012, at 01:07 , ext André Pönitz wrote:
>> This is
>>
>> https://bugreports.qt-project.org/browse/QTCREATORBUG-5200
>>
>>
>> There had been rumours that this was solved in (really) recent gdb
>> builds like the ones that are intended to
On Fri, Apr 20, 2012 at 7:07 PM, André Pönitz
wrote:
> On Fri, Apr 20, 2012 at 06:33:54PM -0400, andy fillebrown wrote:
>> Here are some attachments from a run using Creator 2.5 beta. The
>> project was built with the mingwbuild containing gcc 4.6.2 and gdb
>> 7.4. The .
On Fri, Apr 20, 2012 at 3:23 PM, André Pönitz
wrote:
> On Fri, Apr 20, 2012 at 03:08:01PM -0400, andy fillebrown wrote:
>> [...]
>> GCC 4.6.2 and 4.7.0 from mingwbuilds do not have the slow startup
>> problem. There are still two issues, though.
>
> I still don'
On Fri, Apr 20, 2012 at 8:07 AM, André Pönitz
wrote:
> On Fri, Apr 20, 2012 at 11:19:50AM +0200, Pau Garcia i Quiles wrote:
>> On Fri, Apr 20, 2012 at 11:12 AM, andy fillebrown
>> wrote:
>> > On Fri, Apr 20, 2012 at 2:01 AM, André Pönitz
>> > wrote:
>>
On Fri, Apr 20, 2012 at 2:01 AM, André Pönitz
wrote:
> On Thu, Apr 19, 2012 at 10:34:21PM -0400, andy fillebrown wrote:
>> I would add to the "proper compiler" list the ability to set debug
>> breakpoints quickly and proper display of call stacks across .dll
>> bou
I would add to the "proper compiler" list the ability to set debug
breakpoints quickly and proper display of call stacks across .dll
boundaries. IMO those are the two things that bug me the most about
the "distros" already mentioned. Waiting 2+ minutes for the debugger
to start, and then not bein
st stable mingw-w64 release (gcc 4.6.1).
> See this recent thread in the mingw-w64 mailing list:
>
> http://thread.gmane.org/gmane.comp.gnu.mingw.w64.general/3622
>
>
> On Sat, Oct 29, 2011 at 12:06 AM, andy fillebrown
> wrote:
>> AFAIK, python enabled gdb doe
AFAIK, python enabled gdb does not compile with any version of 64 bit mingw.
Cheers,
~ andy.f
On Fri, Oct 28, 2011 at 10:28 AM, Pau Garcia i Quiles
wrote:
> Hi,
>
> According to the wiki, MinGW will only be supported for 32-bit compilations.
>
> http://developer.qt.nokia.com/wiki/Qt_5.0
>
> I
13 matches
Mail list logo
