OK, got it to work in VS2013 x64 cross-compiling, seem like my -G flag was
not register into the cmake command, du to a non printable character from
utf-8 copy paste to ainsi (damn Windows console sometime). The reason why I
end up with a solution and not the Makefiles as an output from the cmake.
VS2013 x64 Native Tools Command Prompt
On Fri, Jun 26, 2015 at 4:34 PM, Samuel Gaist
wrote:
> Hi,
>
> There's no such limitation, you can build it in 64bit.
>
> Did you start your build from a amd64 or x86_amd64 cross-compiling console
> ?
>
>
> On 26 juin 2015, at 21:04, Jérôme Godbout wrote:
Hi,
There's no such limitation, you can build it in 64bit.
Did you start your build from a amd64 or x86_amd64 cross-compiling console ?
On 26 juin 2015, at 21:04, Jérôme Godbout wrote:
> I'm trying to compile GammaRay, anybody manage to compile it in x64 under
> Windows?
>
> I manage to com
I have compile it with VTK for x86, but does not give me much, since I end
up with only i686 probe.
I used to be able to compile it with nmake and the generated makefiles (I
still have the 2.1 version installed on my machine compile against the Qt
5.2 x64).
Now with the Visual studio .sln generat
I'm trying to compile GammaRay, anybody manage to compile it in x64 under
Windows?
I manage to compile VTK and set the proper env (VTK_DIR) against Qt 5 x64.
I couldn't compile Graphiz in x64 (complaining about missing
header textspan.h, manually give it to him, still cannot compile it in x64,
the
On Friday 26 June 2015 13:20:07 Michael Jackson wrote:
> On our application, we have a peculiar problem on OS X. After we select our
> "Quit" menu the application cleans itself up, the event loop exits but the
> actual application menu remains. Has anyone ever seen anything like this?
> Looking at
On our application, we have a peculiar problem on OS X. After we select our
"Quit" menu the application cleans itself up, the event loop exits but the
actual application menu remains. Has anyone ever seen anything like this?
Looking at terminal, there is no sign of the application actually still
On Friday 26 June 2015 09:55:57 André Somers wrote:
> Ilya Diallo schreef op 25-6-2015 om 23:30:
> > Hi Julien,
> >
> > A long thread on this list last march on this subject was concluded by
> > an answer from Frederik Gladhorn (copy below). For now (5.5), the best
> > is probably to postpone your
I get the value of 60.75 on iOS, on iPad Mini 2 (retina), which is way
too high.
With iPhone 4S I still get value of 1.0 for some reason.
This is with
qt-opensource-mac-x64-android-ios-5.5.0-rc_2015-06-17_20-46-57-98.dmg
snapshot.
I reopened https://bugreports.qt.io/browse/QTBUG-43368
Harri
__
Hi,
thanks all for your inputs, there's a few thing I was not aware of. For the
visualizer, I see little benefit in my use case in desktop, probably more
useful for embedded platform project which I think still have a real world
purpose.
As for GammaRay, it's slow down our application too much, we
On 25 Jun 2015, at 21:41, Jérôme Godbout wrote:
> There's GammaRay
> http://www.kdab.com/kdab-products/gammaray/
> https://github.com/KDAB/GammaRay
>
> It's not 100% efficient, but better then nothing. We end up doing our own
> debugger command line to search and inspect object along a TreeVie
> -Original Message-
> From: interest-bounces+kai.koehne=theqtcompany@qt-project.org
> [mailto:interest-bounces+kai.koehne=theqtcompany@qt-project.org]
> On Behalf Of Dmitry Volosnykh
> Sent: Thursday, June 25, 2015 10:38 PM
> To: Jason H
> Cc: interest@qt-project.org
> Subject: R
2015-06-26 9:55 GMT+02:00 André Somers :
> Feature freeze for 5.6 is in a bit over a month I think. So, that would
> be very little time to actually achieve that feature parity. I would not
> bet on it to be honest.
QtScript will still be in 5.6, so that means that the "promise" of a
smooth migrat
Ilya Diallo schreef op 25-6-2015 om 23:30:
> Hi Julien,
>
> A long thread on this list last march on this subject was concluded by
> an answer from Frederik Gladhorn (copy below). For now (5.5), the best
> is probably to postpone your migration if you want to avoid
> "unofficial" workarounds. QtScr
14 matches
Mail list logo
