[Paraview] ParaView-3.12.0-Win64-x86.exe for Win32?

Tue Nov 15 15:58:55 EST 2011

Hi All,

Yumin, thanks for the input. you are right. its something else.

I only have VS2010 installed. Just to see if it will be different, I
installed the service pack 1 for VS2010 and recompiled qt and ParaView with
MS MPI and Python support. The problem went away. ParaView 64bit I compiled
is working. So, this combination worked:

1. ParaView-3.12.0 source release
2. Windows 7 64bit.
3. VS2010 SP1
4. QT 4.7.4
So either VS2010 SP1 fixed qt 64 compilation, or something else... your
guess is as good as mine... if not better....

thanks for all your help.

best
-simon

On Mon, Nov 14, 2011 at 5:44 PM, Yumin Yuan <yumin.yuan at kitware.com> wrote:

> The win32*- in mkspecs deosn't mean you have 32bit build necessarily.
> You can try to find out whether your Qt build is 32 or 64 bit by
> adding this in your projects.pro
>
> win32-msvc*:contains(QMAKE_TARGET.arch, x86_64):{
> message( "Building for 64 bit")
> }
>
> or just start "<my-Qt-build>/bin/designer.exe, and open up the process
> view in Task manager to see if designer.exe is 64bit.
>
> I think your build could be 64 bit, and the crashing may be caused by
> something else.
>
> Yumin
>
> On Mon, Nov 14, 2011 at 4:24 PM, Simon Su <newsgroup4ssu at gmail.com> wrote:
> >
> > I think I am missing something. I followed it through, but still getting
> > win32-msvc2010 in the configuration output. My guess is, in the mkspecs
> > directory, I can only find win32-*  and not a single win64-*
> >
> > so the question is, for the 64bit binary, what qt was used? can I get a
> copy
> > of it? I don't care about compiling qt too much.
> >
> > thanks
> > -simon
> >
> > On Mon, Nov 14, 2011 at 4:15 PM, Aashish Chaudhary
> > <aashish.chaudhary at kitware.com> wrote:
> >>
> >> is this helpful?
> >> http://developer.qt.nokia.com/wiki/How_to_build_64bit_Qt_for_windows
> >>
> >> On Mon, Nov 14, 2011 at 4:09 PM, Simon Su <newsgroup4ssu at gmail.com>
> wrote:
> >> > Utkarsh,
> >> >
> >> > a none ParaView related question, how did you all get a 64 bit qt to
> >> > compile? When I used 64bit cmd of vs2010, I still get
> >> >
> >> > win32-msvc2010
> >> >
> >> > in the configure. And I cannot find a win64-* anywhere in the
> >> > distribution
> >> > source tree of qt.
> >> >
> >> > thanks
> >> > -simon
> >> >
> >> >
> >> > On Mon, Nov 14, 2011 at 3:59 PM, Utkarsh Ayachit
> >> > <utkarsh.ayachit at kitware.com> wrote:
> >> >>
> >> >> Nope, it will not.
> >> >>
> >> >> Utkarsh
> >> >>
> >> >> On Mon, Nov 14, 2011 at 3:55 PM, Simon Su <newsgroup4ssu at gmail.com>
> >> >> wrote:
> >> >> > Utkarsh,
> >> >> >
> >> >> > If the qt is 32bit, will it work if I use it to compile a 64bit
> >> >> > version
> >> >> > of
> >> >> > ParaView?
> >> >> >
> >> >> > thanks
> >> >> > -simon
> >> >> >
> >> >> > On Mon, Nov 14, 2011 at 1:49 PM, Utkarsh Ayachit
> >> >> > <utkarsh.ayachit at kitware.com> wrote:
> >> >> >>
> >> >> >> Try using dependency walker (http://www.dependencywalker.com/) to
> >> >> >> ensure the correct DLLs are being loaded.
> >> >> >>
> >> >> >> Utkarsh
> >> >> >>
> >> >> >> On Mon, Nov 14, 2011 at 12:13 PM, Simon Su <
> newsgroup4ssu at gmail.com>
> >> >> >> wrote:
> >> >> >> > Hi All,
> >> >> >> >
> >> >> >> > along the same 64bit topic, I was trying to compile the 64bit
> >> >> >> > version
> >> >> >> > on
> >> >> >> > window7 with vs2010 but unsuccessful. I compiled qt using VS x86
> >> >> >> > Win64
> >> >> >> > command prompt on machine with 64bit windows 7 installed. Not
> sure
> >> >> >> > if
> >> >> >> > I
> >> >> >> > got
> >> >> >> > the 64 bit version out of it. Then I use it to compile ParaView
> 64
> >> >> >> > bit
> >> >> >> > version. It compiled but when I run it, it crashed most of the
> >> >> >> > time
> >> >> >> > (not
> >> >> >> > all the time). When I debug it, from what I can gather, it is qt
> >> >> >> > related.
> >> >> >> > Any help is much appreciated.
> >> >> >> >
> >> >> >> > best
> >> >> >> > -simon
> >> >> >> >
> >> >> >> > On Thu, Nov 10, 2011 at 11:45 PM, David Partyka
> >> >> >> > <david.partyka at kitware.com>
> >> >> >> > wrote:
> >> >> >> >>
> >> >> >> >> Hi All, I have replaced the Windows 64bit binary with one that
> >> >> >> >> really
> >> >> >> >> is
> >> >> >> >> 64bit. Please redownload and try again and thank you for your
> >> >> >> >> patience.
> >> >> >> >>
> >> >> >> >> On Thu, Nov 10, 2011 at 10:28 PM, Utkarsh Ayachit
> >> >> >> >> <utkarsh.ayachit at kitware.com> wrote:
> >> >> >> >>>
> >> >> >> >>> I've verified that that's indeed the case. We'll update new
> >> >> >> >>> binaries
> >> >> >> >>> soon.
> >> >> >> >>>
> >> >> >> >>> Thanks for reporting.
> >> >> >> >>>
> >> >> >> >>> Utkarsh
> >> >> >> >>>
> >> >> >> >>> On Thu, Nov 10, 2011 at 7:19 PM, kenichiro yoshimi
> >> >> >> >>> <rccm.kyoshimi at gmail.com> wrote:
> >> >> >> >>> > Hi,
> >> >> >> >>> >
> >> >> >> >>> > I tried to install the 3.12 for Win64 using
> >> >> >> >>> > ParaView-3.12.0-Win64-x86.exe, but it says "Version 3.12.0
> >> >> >> >>> > 32-bit".
> >> >> >> >>> >
> >> >> >> >>> > Is there a Win64-bit executable for the Windows 64 bit
> >> >> >> >>> > machine?
> >> >> >> >>> >
> >> >> >> >>> > Thanks,
> >> >> >> >>> > yoshimi
> >> >> >> >>> > _______________________________________________
> >> >> >> >>> > Powered by www.kitware.com
> >> >> >> >>> >
> >> >> >> >>> > Visit other Kitware open-source projects at
> >> >> >> >>> > http://www.kitware.com/opensource/opensource.html
> >> >> >> >>> >
> >> >> >> >>> > Please keep messages on-topic and check the ParaView Wiki
> at:
> >> >> >> >>> > http://paraview.org/Wiki/ParaView
> >> >> >> >>> >
> >> >> >> >>> > Follow this link to subscribe/unsubscribe:
> >> >> >> >>> > http://www.paraview.org/mailman/listinfo/paraview
> >> >> >> >>> >
> >> >> >> >>
> >> >> >> >>
> >> >> >> >> _______________________________________________
> >> >> >> >> Powered by www.kitware.com
> >> >> >> >>
> >> >> >> >> Visit other Kitware open-source projects at
> >> >> >> >> http://www.kitware.com/opensource/opensource.html
> >> >> >> >>
> >> >> >> >> Please keep messages on-topic and check the ParaView Wiki at:
> >> >> >> >> http://paraview.org/Wiki/ParaView
> >> >> >> >>
> >> >> >> >> Follow this link to subscribe/unsubscribe:
> >> >> >> >> http://www.paraview.org/mailman/listinfo/paraview
> >> >> >> >>
> >> >> >> >
> >> >> >> >
> >> >> >
> >> >> >
> >> >
> >> >
> >> > _______________________________________________
> >> > Powered by www.kitware.com
> >> >
> >> > Visit other Kitware open-source projects at
> >> > http://www.kitware.com/opensource/opensource.html
> >> >
> >> > Please keep messages on-topic and check the ParaView Wiki at:
> >> > http://paraview.org/Wiki/ParaView
> >> >
> >> > Follow this link to subscribe/unsubscribe:
> >> > http://www.paraview.org/mailman/listinfo/paraview
> >> >
> >> >
> >>
> >>
> >>
> >> --
> >> | Aashish Chaudhary
> >> | R&D Engineer
> >> | Kitware Inc.
> >> | www.kitware.com
> >
> >
> > _______________________________________________
> > Powered by www.kitware.com
> >
> > Visit other Kitware open-source projects at
> > http://www.kitware.com/opensource/opensource.html
> >
> > Please keep messages on-topic and check the ParaView Wiki at:
> > http://paraview.org/Wiki/ParaView
> >
> > Follow this link to subscribe/unsubscribe:
> > http://www.paraview.org/mailman/listinfo/paraview
> >
> >
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.paraview.org/pipermail/paraview/attachments/20111115/790de95c/attachment-0001.htm>