- Jul 01, 2016
-
-
Henry Weller authored
-
- Jun 08, 2016
-
-
Henry Weller authored
Patch contributed by Bruno Santos Resolves patch request http://bugs.openfoam.org/view.php?id=2112
-
- Jun 06, 2016
-
-
Henry Weller authored
FOAM_INST_DIR is the location of the OpenFOAM installation which defaults to the directory containing the etc/bashrc,cshrc file. If this default is not appropriate FOAM_INST_DIR can be set explicitly.
-
- May 05, 2016
-
-
Henry Weller authored
Patch contributed by Bruno Santos Resolves bug-report http://bugs.openfoam.org/view.php?id=2031
-
Henry Weller authored
Additionally filter $ParaView_DIR from paths in config.sh/paraview and config.csh/paraview Resolves bug-report http://bugs.openfoam.org/view.php?id=2031
-
- May 02, 2016
-
-
Henry Weller authored
Set the environment variable "FOAMY_HEX_MESH" to build foamyHexMesh, e.g. in ~/.OpenFOAM/dev/prefs.sh FOAMY_HEX_MESH=yes
-
- Mar 09, 2016
-
-
Henry Weller authored
1. "foamCompiler" was changed to a more permanent "WM_COMPILER_TYPE" environment variable, so that it can be used by 3rd party installation scripts, such as "makeGcc", "makeLLVM" and so on. More on this will be provided in issue #1215. 2. The script functions such as "_foamSource()" and "_foamAddPath()" were moved to a new file "etc/config.sh/functions". It has the ability to set or unset, depending on whether "WM_BASH_FUNCTIONS" is defined or not. This allows for these functions to be reused by other scripts, such as "makeGcc". 3. The script "etc/config.sh/CGAL" relies on whether a local environment variable "SOURCE_CGAL_VERSIONS_ONLY" is defined or not, so that it will load only the version settings if it's defined. This is to make it easier to call this script from "makeCGAL". Although it still feels a bit of a clunky hack, but I didn't manage to deduce any other way we could do this :( I didn't add indentation within the if-block, to make it easier to read the changes. In addition, the local variable "common_path" is used to shorten the length of the lines and use slightly less repeated code. 4. Added another new script "etc/config.sh/compiler", which has only the version numbers for the compilers taken out from the "settings" file. It currently depends on "WM_COMPILER_TYPE" for setting the variables, the same way it did with "foamCompiler". This script is now always sourced from the "settings" file, for the following reasons: - "makeGCC" and "makeLLVM" can now take advantage of this script file. - The example "compiler" script (detailed next) can rely on this script file and then override parameters on-demand, as well as allowing for system compilers to have dedicated settings, such as setting "WM_CC". This is similar to how the example environment script for "paraview" works. 5. To the script "etc/config.sh/example/compiler" were added a few more examples: - It now starts with a block where it first loads the default "compiler" script. - Has a "WM_COMPILER=Gcc48u" case example for when we try to use GCC 4.8 in Ubuntu 15.10. This is just to give the idea that in a particular system, we might have several system-wide compiler versions. For example, in Ubuntu 15.10, there is GCC 4.7, 4.8 and 5.2, which could be used for testing performances or compatibility with some other 3rd party library. - Has the "WM_COMPILER=Icc" case example, related to the original bug report, where "WM_CC=icc" and "WM_CXX=icpc", so that the user then simply copies this file to their own local preferences folder. 6. Small bug fix in "etc/config.sh/mpi", where unsetting "minBufferSize" was missing at the end of the script. 7. Small change in "etc/config.sh/paraview", where "CMAKE_ROOT" is set along with "CMAKE_HOME". This is due to a rare issue that occurs on people's systems where they have a custom system-wide CMake version installed and which is used by having "CMAKE_ROOT" set on that environment. This can mess up OpenFOAM's custom ParaView builds, given that conflicting CMake versions can lead to not building ParaView at all. - For more details about "CMAKE_ROOT": https://cmake.org/Wiki/CMake_Useful_Variables [^] 8. The scripts "_foamAddPath _foamAddLib _foamAddMan" were not being unset at the end of "settings". They are now unset at the end of "bashrc", through a call to the new double-use "functions" script. Additionally all references to "foamCompiler" have been changed to "WM_COMPILER_TYPE". See also http://www.openfoam.org/mantisbt/view.php?id=1232
-
- Feb 15, 2016
-
-
Henry Weller authored
-
- Feb 10, 2016
-
-
Henry Weller authored
-
Henry Weller authored
etc/config.sh and etc/config.csh This structure is more convenient to add support for other shells, e.g. zsh, fish etc. Resolves feature request to simplify support for other shells in http://www.openfoam.org/mantisbt/view.php?id=1232
-
- May 17, 2015
-
-
Henry authored
-
- May 14, 2015
-
-
Henry authored
-
- Mar 08, 2015
-
-
Henry authored
-
Henry authored
Provided by Bruno Santos Also some general cleaning and update of comment. Resolves bug-report http://www.openfoam.org/mantisbt/view.php?id=1167
-
- Dec 31, 2014
-
-
Henry authored
To compile with 64bit labels set WM_LABEL_SIZE=64 in ~/OpenFOAM/dev/prefs.sh source ~/.bashrc then Allwmake in OpenFOAM-dev. This will build into for example OpenFOAM-dev/platforms/linux64ClangDPInt64Opt If WM_LABEL_SIZE is unset or set to 32: WM_LABEL_SIZE=32 the build would be placed into OpenFOAM-dev/platforms/linux64ClangDPInt32Opt Thus both 32bit and 64bit label builds can coexist without problem.
-
- Dec 16, 2014
-
-
Henry authored
-
- Dec 11, 2014
-
-
OpenFOAM-admin authored
-
Henry authored
-
- Dec 10, 2014
-
-
Henry authored
-
- Feb 17, 2014
-
-
OpenFOAM-admin authored
-
- Jan 28, 2014
- Jan 10, 2014
- Nov 05, 2013
-
-
andy authored
-
- Jun 04, 2013
-
-
andy authored
-
- May 31, 2013
-
-
laurence authored
-
- Feb 04, 2013
-
-
mattijs authored
-
- Jan 28, 2013
-
-
laurence authored
-
- Dec 17, 2012
-
-
Henry authored
-
- Dec 11, 2012
-
-
laurence authored
-
- Jun 29, 2012
-
-
andy authored
-
- Mar 12, 2012
-
-
mattijs authored
-
- Aug 14, 2011
-
-
Henry authored
-
- Jul 21, 2011
-
-
mattijs authored
-
- Jun 17, 2011
-
-
OpenFOAM-admin authored
-
- Jun 08, 2011
-
-
andy authored
-
- Jun 07, 2011
-
-
andy authored
-
- May 19, 2011
-
-
Mark Olesen authored
- otherwise there is actually no means of placing a site-site prefs.sh in the $WM_PROJECT_SITE/ directory
-