how to install ESyS-Particle on the win x64 computer

Hi, Ray Mong:

Although I do not have windows 8, I believe windows 8 should be able to run 32 bit programs as well as windows 7? If you are able to install those 32 bit pre-requisites (e.g. boost, visual studio, etc. ), there should be no problem build and run the 32 bit ESyS-Particle on windows 8. My test environment is a 64 bit windows 7, with no compatibility issues at all.

Let me know if you have any problems while following the build instructions, thank you!

Feng

Hi, Feng
I installed esys-particle following esys-particle-win-(v2.1)-build-instructions.pdf, when I went to ‘2.1 Generate CMake Makefiles’, run "mkvs9.bat" in the folder of "C:/esys-particle-win/trunk/buildvs2008", I got these error information:

C:\esys-particle-win\trunk\buildvs2008>mkvs9.bat

C:\esys-particle-win\trunk\buildvs2008>cmake .. -G "Visual Studio 9 2008" -G "NM
ake Makefiles"
CMake Warning at CMakeLists.txt:3 (project):
  To use the NMake generator, cmake must be run from a shell that can use the
  compiler cl from the command line. This environment does not contain
  INCLUDE, LIB, or LIBPATH, and these must be set for the cl compiler to
  work.

-- The C compiler identification is unknown
-- The CXX compiler identification is unknown
-- Check for working C compiler: cl
CMake Warning at CMakeLists.txt:2 (PROJECT):
  To use the NMake generator, cmake must be run from a shell that can use the
  compiler cl from the command line. This environment does not contain
  INCLUDE, LIB, or LIBPATH, and these must be set for the cl compiler to
  work.

CMake Error: your C compiler: "cl" was not found. Please set CMAKE_C_COMPILER
to a valid compiler path or name.
CMake Error: Internal CMake error, TryCompile configure of cmake failed
-- Check for working C compiler: cl -- broken
CMake Error at D:/Program Files (x86)/CMake 2.8/share/cmake-2.8/Modules/CMakeTes
tCCompiler.cmake:61 (message):
  The C compiler "cl" is not able to compile a simple test program.

  It fails with the following output:

  CMake will not be able to correctly generate this project.
Call Stack (most recent call first):
  CMakeLists.txt:3 (project)

CMake Error: your C compiler: "cl" was not found. Please set CMAKE_C_COMPILER
to a valid compiler path or name.
CMake Error: your CXX compiler: "cl" was not found. Please set CMAKE_CXX_COMPI
LER to a valid compiler path or name.
-- Configuring incomplete, errors occurred!

It sounds like my computer had no C compiler, but I can run C++ code in the software of 'Microsoft visual studio 2008'.
and CMakeLists.txt was modified, which all of new path is relate to my software directory.

set(OMPI_INCLUDES "D:/Program Files (x86)/OpenMPI_v1.5.5-x64/include")
set(OMPI_LIB_PATH "D:/Program Files (x86)/OpenMPI_v1.5.5-x64/lib")
set(OMPI_CORE_LIBS "libmpi.lib" "libmpi_cxx.lib" "libopen-pal.lib" "libopen-rte.lib")

# set(PYTHON_INCLUDES "C:/Python27/include")
# set(PYTHON_LIB_PATH "C:/Python27/libs")

set(PYTHON_INCLUDES "D:/Program Files (x86)/Python27/include")
set(PYTHON_LIB_PATH "D:/Program Files (x86)/Python27/libs")

set(BOOST_INCLUDES "D:/Program Files (x86)/boost/boost_1_47")
set(BOOST_LIB_PATH "D:/Program Files (x86)/boost/boost_1_47/lib")

waitting for your reply.
Thank you!

Huajun Ming

Hi, Huajun:

Please see build instruction Section 2.3.1 Generate CMake Makefiles, you will need to "Open a Visual Studio command prompt" to type the cmake command, the visual studio command prompt will set necessary environment variables for C/C++ compilers.

The visual studio command prompt should be activated from: "Microsoft Visual Studio 2008->Visual Studio Tools->Visual Studio 2008 Command prompt", please do NOT set the "Visual Studio 2008 x64 Win64 Command Prompt".

Feng

Hi, Huajun:

After I took another look at your CMakeList.txt file, you should NOT install the 64 bit version of OpenMPI and should use 32-bit OpenMPI instead, make sure you uninstall the 64-bit OpenMPI before install the 32-bit version, which has been emphasized in the build instructions.pdf.

All pre-requisites should be 32-bit version, if you want to try compiling a complete 64-bit version ESyS-Particle (which was never tried), make sure all pre-requisites are 64-bit version before building.

Feng

Hi, Feng
I intalled esys-particle following esys-particle-win-(v2.1)-build-instructions.pdf on other computer which used winXP, but it always had the same error information like above.
2.3.1 part in the instruction, open a visual studio command prompt firstly, and go to the root of my folder which put "mkvs9.bat" file.
Now I have a question. run the file of "mkvs9.bat" by click this file in the directory, or from visual studio command prompt?
if it from visual studio command prompt, how to do?
Thank you!

Huajun Ming

Hi, Huajun:

If I am understanding your question correctly, running "mkvs9.bat" from a pure command prompt is different from running the "mkvs9.bat" in a VISUAL STUDIO command prompt, when you run "mkvs9.bat" from VISUAL STUDIO command prompt, the VS command prompt will first set the environment variables for C/C++ compiler configurations, which is essential for your CMake to generate Makefile or VS project files, otherwise you will get the error from CMake complaining that it cannot find C/C++ compilers.

Therefore you MUST run the cmake command from a VISUAL STUDIO command prompt. When you click the VS command prompt, it automatically executes the command "%comspec% /k ""c:\Program Files (x86)\Microsoft Visual Studio 9.0\VC\vcvarsall.bat"" x86", the vcvarsall.bat had the following contents which will set your important environmental variables

------------------------------------------------------------------------------------------------------------
@echo off
if "%1" == "" goto x86
if not "%2" == "" goto usage

if /i %1 == x86 goto x86
if /i %1 == amd64 goto amd64
if /i %1 == x64 goto amd64
if /i %1 == ia64 goto ia64
if /i %1 == x86_amd64 goto x86_amd64
if /i %1 == x86_ia64 goto x86_ia64
goto usage

:x86
if not exist "%~dp0bin\vcvars32.bat" goto missing
call "%~dp0bin\vcvars32.bat"
goto :eof

:amd64
if not exist "%~dp0bin\amd64\vcvarsamd64.bat" goto missing
call "%~dp0bin\amd64\vcvarsamd64.bat"
goto :eof

:ia64
if not exist "%~dp0bin\ia64\vcvarsia64.bat" goto missing
call "%~dp0bin\ia64\vcvarsia64.bat"
goto :eof

:x86_amd64
if not exist "%~dp0bin\x86_amd64\vcvarsx86_amd64.bat" goto missing
call "%~dp0bin\x86_amd64\vcvarsx86_amd64.bat"
goto :eof

:x86_ia64
if not exist "%~dp0bin\x86_ia64\vcvarsx86_ia64.bat" goto missing
call "%~dp0bin\x86_ia64\vcvarsx86_ia64.bat"
goto :eof

:usage
echo Error in script usage. The correct usage is:
echo %0 [option]
echo where [option] is: x86 ^| ia64 ^| amd64 ^| x86_amd64 ^| x86_ia64
echo:
echo For example:
echo %0 x86_ia64
goto :eof

:missing
echo The specified configuration type is missing. The tools for the
echo configuration might not be installed.
goto :eof

------------------------------------------------------------------------------------------------------------

Best Regards,

Feng

For those who are unfamiliar with visual studio command line operations, I have updated the build instructions section 2.3.1 with screenshots for opening the visual studio command prompt.

Feng

Below is also a good tutorial about how to use command line operations under windows:

http://www.7tutorials.com/command-prompt-how-use-basic-commands

Feng