Difference between revisions of "TestWyldckat"
| Line 2: | Line 2: | ||
This is a step by step guide on how to cross-compile OpenFOAM in Linux for Windows, for both 32 and 64 bits architectures (to and from), using the patches available [[File:PatchesNBatches.tar.gz|here]]. | This is a step by step guide on how to cross-compile OpenFOAM in Linux for Windows, for both 32 and 64 bits architectures (to and from), using the patches available [[File:PatchesNBatches.tar.gz|here]]. | ||
| − | These patches were based on Symscape's "v3" patch for OpenFOAM available [http://www.symscape.com/openfoam-1-5-x-on-windows | + | These patches were based on Symscape's "v3" patch for OpenFOAM available [http://www.symscape.com/openfoam-1-5-x-on-windows here]. They differ substantially from that patch, as well as the more recent one available [http://www.symscape.com/openfoam-1-6-x-on-windows here]. The build scripts for [http://www.mingw.org mingw] were also based on the build-script available on the 1.5.x link. |
| − | With this guide and available patches, you should be able to cross-compile the whole OpenFOAM library and applications, using MPICH2 instead of Open MPI for parallel computing. You can cross-compile using [http://www.mingw.org | + | With this guide and available patches, you should be able to cross-compile the whole OpenFOAM library and applications, using MPICH2 instead of Open MPI for parallel computing. You can cross-compile using [http://www.mingw.org mingw32] and/or [http://www.cadforte.com mingw-w64]. These enable you to build OpenFOAM 1.6 for Windows 32 and 64 bit versions, from Linux 32 and 64bit architectures. |
== Get OpenFOAM packages == | == Get OpenFOAM packages == | ||
#In your Linux machine, open a terminal window and create the folder '''$HOME/OpenFOAM'''. | #In your Linux machine, open a terminal window and create the folder '''$HOME/OpenFOAM'''. | ||
| − | #Get '''OpenFOAM-1.6.General.gtgz''' and '''ThirdParty-1.6.General.gtgz''' from the [http://www.opencfd.co.uk/openfoam/linux.html | + | #Get '''OpenFOAM-1.6.General.gtgz''' and '''ThirdParty-1.6.General.gtgz''' from the [http://www.opencfd.co.uk/openfoam/linux.html OpenCFD's website] and move them to the folder '''$HOME/OpenFOAM'''. |
#Extract both files, by running in a terminal: | #Extract both files, by running in a terminal: | ||
<cpp>cd $HOME/OpenFOAM | <cpp>cd $HOME/OpenFOAM | ||
| Line 15: | Line 15: | ||
tar xzf ThirdParty-1.6.General.gtgz | tar xzf ThirdParty-1.6.General.gtgz | ||
</cpp> | </cpp> | ||
| + | |||
| + | == Optional: Using a specific gcc version for building the wmake binaries == | ||
| + | This is optional, because the current patch will use the system's gcc for building them (more specifically '''gcc''' as compiler name). | ||
| + | |||
| + | == == | ||
Revision as of 15:54, 10 November 2009
Contents
1 Introduction
This is a step by step guide on how to cross-compile OpenFOAM in Linux for Windows, for both 32 and 64 bits architectures (to and from), using the patches available File:PatchesNBatches.tar.gz.
These patches were based on Symscape's "v3" patch for OpenFOAM available here. They differ substantially from that patch, as well as the more recent one available here. The build scripts for mingw were also based on the build-script available on the 1.5.x link.
With this guide and available patches, you should be able to cross-compile the whole OpenFOAM library and applications, using MPICH2 instead of Open MPI for parallel computing. You can cross-compile using mingw32 and/or mingw-w64. These enable you to build OpenFOAM 1.6 for Windows 32 and 64 bit versions, from Linux 32 and 64bit architectures.
2 Get OpenFOAM packages
- In your Linux machine, open a terminal window and create the folder $HOME/OpenFOAM.
- Get OpenFOAM-1.6.General.gtgz and ThirdParty-1.6.General.gtgz from the OpenCFD's website and move them to the folder $HOME/OpenFOAM.
- Extract both files, by running in a terminal:
cd $HOME/OpenFOAM tar xzf OpenFOAM-1.6.General.gtgz tar xzf ThirdParty-1.6.General.gtgz
3 Optional: Using a specific gcc version for building the wmake binaries
This is optional, because the current patch will use the system's gcc for building them (more specifically gcc as compiler name).
