Am 07.02.2013 um 02:59 schrieb Scott Aron Bloom :
> Just a suggestion...
>
> If you use a "Project" directory, for source and building, add that directory
> to your virus system as a white listed directory, ie don't check it.
Guido already stated that he's not using any virus scanner ;)
My sec
Hi all,
I try to find the QWebElement at the clickposition in a QWebView
(Qt-5.0) witch the follwing code snippet:
void WebView::mousePressEvent(QMouseEvent *e)
{
QWebFrame* frame = page()->frameAt(e->pos());
QWebHitTestResult hit = frame->hitTestContent(e->pos());
qDebug() << Q_
On 6/02/2013 5:30 PM, Hamish Moffatt wrote:
> We're building successfully with Qt 4.8.4 on VS2008 and I'm trying to
> upgrade to 2012. However any project of ours which specifies Win32
> resources is failing to link with duplicate resource errors.
It seems VS2012 is including the compiled resource
Just a suggestion...
If you use a "Project" directory, for source and building, add that directory
to your virus system as a white listed directory, ie don't check it.
I typically see at least a 2X improvement on compilation/linking time
Scott
-Original Message-
From: interest-bounces+
On 02/07/2013 05:51 AM, Guido Seifert wrote:
>> I guess you have an application running that has that file open. Close all
>> Qt-based applications.
> Impossible. I am just compiling Qt. No other app could use it.
I get these errors because my antivirus is accessing files during
compilation. Espe
On quinta-feira, 7 de fevereiro de 2013 10.38.42, Hamish Moffatt wrote:
> Is it possible to inspect the makespec inside a .pro project? The
> documentation implies it should be in $$QMAKESPEC, but that always seems
> to be empty when I print it with message() or test it with contains().
The mkspec
Is it possible to inspect the makespec inside a .pro project? The
documentation implies it should be in $$QMAKESPEC, but that always seems
to be empty when I print it with message() or test it with contains().
thanks,
Hamish
___
Interest mailing list
Am Mittwoch, 6. Februar 2013, 21:28:24 schrieb Guido Seifert:
> > What's the path for your qt source and binary directory then? Might be
> > that
> > some absolute path used by the mkdir and cd during compilation are too
> > long.
>
> This sounds interesting and something I could try. Though I don
What EXACT version of VS2010 do you have? Are you trying to compile a 64bit
version of Qt? If so you MUST have the Service Pack 1 for VS2010. Without it
building Qt4 is worthless as the 64 bit compiler has bugs that Qt will
exercise. You *might* be seeing these bugs. Maybe.
Mike Jackson
On Feb
It's been a few years, but I think maybe it might come down to a 64/32 bit
issue with the MS resource tool. I can't quite remember it, but there is
somethign about 32/64 that requires an alternate resource program to be used on
64 bit machines.
From: Guido Se
Nope, take it back. Not the same.
Guido
> Looks like I have been bitten by this one:
> https://bugreports.qt-project.org/browse/QTBUG-6470
>
> Guido
>
>
> > > What's the path for your qt source and binary directory then? Might be
> > > that
> > > some absolute path used by the mkdir and cd
Looks like I have been bitten by this one:
https://bugreports.qt-project.org/browse/QTBUG-6470
Guido
> > What's the path for your qt source and binary directory then? Might be
> > that
> > some absolute path used by the mkdir and cd during compilation are too
> > long.
>
> This sounds intere
> What's the path for your qt source and binary directory then? Might be
> that
> some absolute path used by the mkdir and cd during compilation are too
> long.
This sounds interesting and something I could try. Though I don't really know
why repeated nmakes should solve this problem.
C:\Users
Am Mittwoch, 6. Februar 2013, 21:08:26 schrieb Guido Seifert:
> I am the 1%. I don't have a virus scanner. :-)
>
> > 99% of the time, this is due to a virus scanner scanning the file and
> > denying access while it does so.
What's the path for your qt source and binary directory then? Might be th
I am the 1%. I don't have a virus scanner. :-)
> 99% of the time, this is due to a virus scanner scanning the file and
> denying access while it does so.
___
Interest mailing list
Interest@qt-project.org
http://lists.qt-project.org/mailman/listinfo/inte
99% of the time, this is due to a virus scanner scanning the file and denying
access while it does so.
From: Guido Seifert
To: interest@qt-project.org
Sent: Wednesday, February 6, 2013 2:54 PM
Subject: Re: [Interest] I am trying to compile Qt 4.8 with VS2010
Sorry, you are right.
VS2010: SDK v7.1
Qt: Latest 4.8 from git. Cloned a few hours ago.
Windows 7/64 bit
Seems to work now after a few repeated 'nmake'. Strange.
G.
> What version of VS2010? What version of Windows? what exact version of Qt
> 4.8? .0, .1, .2, .3, .4? 32 or 64 bit?
>
> MJ
>
>
> I guess you have an application running that has that file open. Close all
> Qt-based applications.
Impossible. I am just compiling Qt. No other app could use it.
> Another idea is that your filesystem is corrupt. Try running the disk
> checker tools, including searching for bad sectors.
Hope
What version of VS2010? What version of Windows? what exact version of Qt 4.8?
.0, .1, .2, .3, .4? 32 or 64 bit?
MJ
On Feb 6, 2013, at 2:13 PM, Guido Seifert wrote:
> I get:
> Failed to write to updated resource file qico4.dll.
> The operation failed.
>
> Any ideas?
>
> Guido
> _
On quarta-feira, 6 de fevereiro de 2013 20.13.35, Guido Seifert wrote:
> I get:
> Failed to write to updated resource file qico4.dll.
> The operation failed.
>
> Any ideas?
I guess you have an application running that has that file open. Close all Qt-
based applications.
Another idea is that
I get:
Failed to write to updated resource file qico4.dll.
The operation failed.
Any ideas?
Guido
___
Interest mailing list
Interest@qt-project.org
http://lists.qt-project.org/mailman/listinfo/interest
On Wednesday, 2 January 2013 17:42:53 CEST, Stephen Kelly wrote:
> Of course it's a bug and an odd mistake that
> Q_DECLARE_METATYPE(QList) is in qsslsocket.h instead of
> qsslerror.h.
Hi Stephen,
using qtbase v5.0.0-320-ge17dddf, the following code fails to build:
$ cat test-qdeclaremetatype.
22 matches
Mail list logo