My old PC has a 64bit CPU (Intel Core 2 Duo P8400) and a 32bit Win7.
My new PC has a 64bit CPU (Intel Core 2 Duo T6600) and a 64bit Win7.
Qt4dotnet *does* work fine in a virtual machine running 32bit WinXP
(on the new PC).
My example project uses (contains) the 64bit version of
ikvm-native.dll, as it should.
When run, it outputs the attached stacktrace.
Any ideas?
Stefan
Thanks,
David.
> --
> You received this message because you are subscribed to the Google Groups "qt4dotnet" group.
> To post to this group, send email to qt4d...@googlegroups.com.
> To unsubscribe from this group, send email to qt4dotnet+...@googlegroups.com.
> For more options, visit this group at http://groups.google.com/group/qt4dotnet?hl=en.
>
>
It turns out the Qt Jambi devs have stopped doing win64 releases from
Qt Jambi 4.5.2 on. The reasons are described here:
http://redmine.smar.fi/issues/63
So, one I thing I tried was to get the 4.5.2 Qt Jambi release and use
it with qt4dotnet 4.6.3. Worked fine, but I didn't want to be limited
to an old Qt version. More precisely, what worked was to take:
- com_*.dll, Qt*4.dll and qtjambi.dll from Qt Jambi 4.5.2, *and*
- ikvm-native.dll (the version from the 64-bit subfolder) and
qtjambi-4.6.3.dll from qt4dotnet 4.6.3.
Another thing I found was this:
http://code.google.com/p/qt-msvc-installer/downloads/list
It seems to be a separate project that provides, among other things,
win64 binaries of recent Qt versions, built for VS2008. I think the
DLLs in those releases would.have worked with qt4dotnet 4.6.3 on my
win64 system, but I didn't try them out.
After that, finally, I found a simple solution. I had to go to my
project's Properties -> Build in VS, and change Platform target from
Any CPU to x86. After doing that, my app works on win64 with the
normal 32-bit DLLs provided by qt4dotnet.