[Paraview] [Paraview-developers] [paraview-developers] A kind of building errors of paraview development version under Visual Studio 2010 on Windows 7 64bits
Bruno Santos
bruno.santos at bluecape.com.pt
Mon Jan 9 03:40:47 EST 2012
Hi,
I had a webmail problem so the answer below didn't go out to the mailing
list:
On 19:59, Bruno Santos wrote:
> Hi,
>
> Mingcheng Chen, you'll need the 32bit version of MPICH2 as well. Otherwise
> it doesn't make any sense!
>
> As stated on the ParaView Developers mailing list, MS-MPI is a variant of
> MPICH2. Additionally, the version of MS-MPI that is installed in Windows
> x64 has libraries (DLLs) for 32 and 64bits. But with MPICH2, 32 and 64bit
> are completely separate and independent installations.
>
> Best regards,
> Bruno
>
>
> Date: Thu, 5 Jan 2012 15:58:08 -0500
> From: David E DeMarle<dave.demarle at kitware.com>
> Subject: Re: [Paraview] [Paraview-developers] [paraview-developers] A
> kind of building errors of paraview development version under Visual
> Studio 2010 on Windows 7 64bits
>
> Please keep the discussion on the mailing list so that everyone can
> contribute and benefit. Also this discussion probably should have stayed on
> the paraview users list so I'm cross-posting there.
>
> I'm not certain if the 64 bit-ness of the MPI lib matters. It's certainly
> safer to stick with a 32 bit version if you are compiling 32 bit code (and
> 64 bit for 64 bit libs), but it might not be required. Someone else on the
> list may clarify.
>
> In any case, the CMake FindMPI module we have has a rich and sordid history
> behind it. It could just be buggy on your system. Try moving the cxx.lib to
> the MPI_EXTRA_LIBRARY variable. I suspect it will build for you then.
>
> David E DeMarle
> Kitware, Inc.
> R&D Engineer
> 21 Corporate Drive
> Clifton Park, NY 12065-8662
> Phone: 518-881-4909
>
>
> On Thu, Jan 5, 2012 at 3:46 PM, Mingcheng Chen<linyufly at gmail.com> wrote:
>
>> Thanks David!
>>
>> Before turning off PARAVIEW_USE_MPI, I still want to have a try.
>>
>> I have installed MPICH2(64bit) on my machine. Is the 64bit version OK? And
>> I have set MPI_INCLUDE_PATH (According to online tutorial, it is not
>> MPI_INCLUDE, right?) and MPI_LIBRARY.
>>
>> There is a small problem that CMake automatically sets MPI_LIBRARY to be
>> "C:\Program Files\MPICH2\lib\mpi.lib C:\Program Files\MPICH2\lib\cxx.lib".
>> So I have to manually split it into two separate lines for some projects in
>> the ParaView solution. Otherwise there will be several errors from those
>> projects, called "cannot open file 'C:\Program
>> Files\MPICH2\lib\mpi.lib C:\Program Files\MPICH2\lib\cxx.lib'."
>>
>> Currently I am finding all the projects which needs such split by
>> compiling the whole solution again and again.
>>
>> On Fri, Jan 6, 2012 at 4:30 AM, David E DeMarle
> <dave.demarle at kitware.com>wrote:
>>> Turn off PARAVIEW_USE_MPI in CMake and recompile. If that doesn't work
>>> (because of stale dependent build option settings) you will have to clear
>>> out the build directory and recompile.
>>>
>>> Alternatively you could install MPICH2 or OpenMPI for Windows and then
>>> rebuild. When you turn on PARAVIEW_USE_MPI the first time, CMake should
>>> find MPI in your path and and determine what the correct settings for
>>> MPI_INLCUDE, MPI_LIBRARY and MPI_EXTRA_LIBRARY accordingly. The VTK and
>>> ParaView dashboards have a few examples, but it appears the Kitware hosted
>>> machines (see http://www.cdash.org/CDash/viewNotes.php?buildid=1886001for
> example) all use Microsoft's MPI.
>>> David E DeMarle
>>> Kitware, Inc.
>>> R&D Engineer
>>> 21 Corporate Drive
>>> Clifton Park, NY 12065-8662
>>> Phone: 518-881-4909
>>>
>>>
>>> On Thu, Jan 5, 2012 at 2:58 PM, Mingcheng Chen<linyufly at gmail.com>wrote:
>>>
>>>> Hi everybody,
>>>>
>>>> These days I was puzzled by different kinds of errors when I tried to
>>>> build paraview from open source code.
>>>>
>>>> My machine is AMD64 and my OS is Windows 7 64bits.
>>>>
>>>> My IDE is Visual Studio 2010.
>>>>
>>>> My CMake is 2.8.
>>>>
>>>> I choose to build a 32bit version.
>>>>
>>>> A kind of errors is as follows.
>>>>
>>>> "Error 31 error LNK1120: 12 unresolved externals
>>>> D:\LCSWorkSpace\ParaViewTest\ParaViewDev\bin\Release\Cosmo.dll Cosmo"
>>>>
>>>> "Cosmo" is a project in ParaView.sln generated by CMake.
>>>> "D:\LCSWorkSpace\ParaViewTest\ParaViewDev" is my output directory of
>>>> CMake (where ParaView.sln is).
>>>>
>>>> I do not know what the 12 unresolved externals are. Moreover, there is
>>>> another kind of errors such as follows.
>>>>
>>>> "Error 29 error LNK2019: unresolved external symbol _MPI_Recv
>>>> referenced in function "public: void __thiscall
> Message::receive(int,int)"
>>>> (?receive at Message@@QAEXHH at Z)
>>>> D:\LCSWorkSpace\ParaViewTest\ParaViewDev\VTK\Utilities\Cosmo\Message.obj
>>>> Cosmo"
>>>>
>>>> Is it one of the 12 unresolved externals? What is the meaning of this
>>>> error and how can I get rid of it?
>>>>
>>>> Thanks!
>>>>
>>>> I am very interested in whether there are people who have successfully
>>>> built 32bit paraview using Visual Studio 2010 on 64bit machine.
>>>>
>>>> Thanks again!
>>>>
>>>> Best regards,
>>>> Mingcheng Chen
>>>> January 5th, 2012
>>>>
>>>>
>>>> _______________________________________________
>>>> Paraview-developers mailing list
>>>> Paraview-developers at paraview.org
>>>> http://public.kitware.com/mailman/listinfo/paraview-developers
>>>>
>>>>
>>
>> --
>> Mingcheng Chen
>>
>> Research Assistant in Graphics Group
>> University of Illinois at Urbana-Champaign
>>
>> ---------------------------------------------------------
>> Below is my undergraduate information.
>> ---------------------------------------------------------
>> Personal Page: http://epcc.sjtu.edu.cn/~mingchengchen
>> Embedded and Pervasive Computing Center
>> Shanghai Jiao Tong University
>> No.800 Dongchuan Road, Minhang District, Shanghai, PRC
>>
>>
--
http://www.bluecape.com.pt
blueCAPE Lda - CAE solutions
Rua Fonte dos Corvos, n.29
Casais da Serra
2665-305 Milharado
PORTUGAL
(+351) 219 755 345 Tel.
(+351) 219 755 345 Fax
(+351) 963 440 984 Mob.
More information about the ParaView
mailing list