Qt-interest Archive, April 2008
Install Qt on Windows XP x64
Message 1 in thread
Hi guys,
I have bought commercial Qt 4.3.4 and want to install it on Windows XP x64.
I have read that the shipped binaries are compiled for the 32-bit, so i used
the source code
in order to compile qt.
In order to compile it in 64-bit mode, i opened "Visual Studio 2006 x64
command prompt" and
from there i compiled the Qt.
Everything went ok, and i tried to compile my Qt application from Visual
Studio: I created a new Release Configuration for x64 platform and compiled
my application.
But, when i check my .exe with the "depends" tool, i see that has a lot of
32-bit dependencies.
How can i check that my executable is a native x64 exe?
Has anyone used Qt under Windows x64?
Thanks in Regards,
Panos
Message 2 in thread
I have completely 64-bit version of Qt 4 Open Source Edition on my system
compiled using my special "win64-msvc2005" mkspec, which is obviously
based on "win32-msvc2005" one (I used patches from Qt/Win project before
Visual Studio support became available out of the box).
I can provide my mkspecs but I don't know 2 things:
1) if it's good to mix files from open source and commercial Qt;
2) if it's possible to attach files (particularly zip archives) to
messages on this mailing list.
If there're no problems with (1), I can send the files to you directly.
If (2) is OK, I can give them to everybody here, I'm not greedy. :)
On Mon, 07 Apr 2008 10:49:47 +0400, Panagiotis Antonellis
<adonel@xxxxxxxxx> wrote:
> Hi guys,
>
> I have bought commercial Qt 4.3.4 and want to install it on Windows XP
> x64.
> I have read that the shipped binaries are compiled for the 32-bit, so i
> used
> the source code
> in order to compile qt.
> In order to compile it in 64-bit mode, i opened "Visual Studio 2006 x64
> command prompt" and
> from there i compiled the Qt.
> Everything went ok, and i tried to compile my Qt application from Visual
> Studio: I created a new Release Configuration for x64 platform and
> compiled
> my application.
> But, when i check my .exe with the "depends" tool, i see that has a lot
> of
> 32-bit dependencies.
> How can i check that my executable is a native x64 exe?
>
> Has anyone used Qt under Windows x64?
>
> Thanks in Regards,
> Panos
--
[ signature omitted ]
Message 3 in thread
Hi,
> I have completely 64-bit version of Qt 4 Open Source Edition on my
> system compiled using my special "win64-msvc2005" mkspec, which is
> obviously based on "win32-msvc2005" one (I used patches from Qt/Win
> project before Visual Studio support became available out of the box).
Using the standard 'win32-msvc2005' mkspec with Visual Syudio's 64-bit command
prompt should work as well. There's no need for a specific mkspec - although
there's nothing inherently wrong with it either.
--
[ signature omitted ]
Message 4 in thread
My "win32-msvc2005" mkspec isn't standard -- I tuned compiler and linker
options and some other parameters. "win64-msvc2005" is only slightly
different.
I don't say that separate mkspecs are really neccessary, just I did what I
like more. Both 32-bit and 64-bit versions of Qt lie in the same root
directory and can be used simultaneously (by different applications, of
course) without any problems.
On Tue, 08 Apr 2008 00:02:22 +0400, Dimitri <dimitri@xxxxxxxxxxxxx> wrote:
> Hi,
>
>> I have completely 64-bit version of Qt 4 Open Source Edition on my
>> system compiled using my special "win64-msvc2005" mkspec, which is
>> obviously based on "win32-msvc2005" one (I used patches from Qt/Win
>> project before Visual Studio support became available out of the box).
>
> Using the standard 'win32-msvc2005' mkspec with Visual Syudio's 64-bit
> command prompt should work as well. There's no need for a specific
> mkspec - although there's nothing inherently wrong with it either.
--
[ signature omitted ]
Message 5 in thread
Thanks Dimitri,
But is there any standard way to check for sure that Qt has been built in
64bits?
Thanks
Panos
On Mon, Apr 7, 2008 at 11:02 PM, Dimitri <dimitri@xxxxxxxxxxxxx> wrote:
> Hi,
>
> I have completely 64-bit version of Qt 4 Open Source Edition on my system
> > compiled using my special "win64-msvc2005" mkspec, which is obviously based
> > on "win32-msvc2005" one (I used patches from Qt/Win project before Visual
> > Studio support became available out of the box).
> >
>
> Using the standard 'win32-msvc2005' mkspec with Visual Syudio's 64-bit
> command prompt should work as well. There's no need for a specific mkspec -
> although there's nothing inherently wrong with it either.
>
> --
> Dimitri
>
>
> --
> To unsubscribe - send a mail to qt-interest-request@xxxxxxxxxxxxx with
> "unsubscribe" in the subject or the body.
> List archive and information: http://lists.trolltech.com/qt-interest/
>
>
Message 6 in thread
There's a field in Windows PE format header which specifies machine type.
So you can write a small program which will read that field and show the
results in human-readable form.
Also there's a plug-in for Total Commander called "FileInfo". It can show
many things about executables and libraries.
On Tue, 08 Apr 2008 10:35:45 +0400, Panagiotis Antonellis
<adonel@xxxxxxxxx> wrote:
> Thanks Dimitri,
> But is there any standard way to check for sure that Qt has been built in
> 64bits?
> Thanks
> Panos
>
> On Mon, Apr 7, 2008 at 11:02 PM, Dimitri <dimitri@xxxxxxxxxxxxx> wrote:
>
>> Hi,
>>
>> I have completely 64-bit version of Qt 4 Open Source Edition on my
>> system
>> > compiled using my special "win64-msvc2005" mkspec, which is obviously
>> based
>> > on "win32-msvc2005" one (I used patches from Qt/Win project before
>> Visual
>> > Studio support became available out of the box).
>> >
>>
>> Using the standard 'win32-msvc2005' mkspec with Visual Syudio's 64-bit
>> command prompt should work as well. There's no need for a specific
>> mkspec -
>> although there's nothing inherently wrong with it either.
>>
>> --
>> Dimitri
>>
>>
>> --
>> To unsubscribe - send a mail to qt-interest-request@xxxxxxxxxxxxx with
>> "unsubscribe" in the subject or the body.
>> List archive and information: http://lists.trolltech.com/qt-interest/
--
[ signature omitted ]
