Personal tools

Mohid Makefile

From MohidWiki

Jump to: navigation, search

Following the makefile cross-platform, cross-compiler project methodology, we finally developped a sound makefile project for MOHID.

MOHID makefile project DAG tree:Orange ellipsoids are makefiles; orange rectangles are makefile code snippets; Diamond arrows are inclusions; Quiver arrows are recursive makes; Large rectangles are project folders; purple octagons are junction nodes. Sketch made using yED


Global environment variables

There is one thing that allow this project to be easily cross-platformed:

  1. The use of global environment variables. They are all defined in the respective platform makefile:,, etc... Every new addition of a module, of a fortran file, or of an action must be followed by an update of all the respective platform makefiles (,, etc...)

Platform/Compiler expandible

The project makefile's DAG meta-tree shows currently 4 platforms/compilers available: windows, linux, linux with Portland Group Fortran and macintosh

  • To add a new compiler and/or a new architecture, one needs to change the main Makefile and create a new file.

Action extensible

An action is one given process to apply to the whole project: it could be to build the project, to clean the project, to install the binaries of the project to a safe place, to Get the files of the project from SourceOffSite etc ... The makefile code for the actions of the MOHID project is located in the files contained by the makefiles folder (at the bottom of the image).

  • To add a new action, one needs to edit the Makefiles/ file and the Makefiles/

Module extensible

The MOHID project has a modular nature. In this makefile project, each module is subject to the same overall actions and each module is contained in a light-blue folder in the image (MohidWater, Mohid_Base_1, Mohid_Base_2 and ...).

  • To add a new file to an existing module: one must edit the Makefile file within the module's folder.
  • To add a new module: one must create a new folder, name it after the module, copy the module's files, create the corresponding Makefile file. Finally, one must edit the file from the root folder.

Makefile project tree

mohid/Solutions/Linux> tree
|-- Makefile
|-- Makefiles
|   |-- Makefile
|   |--
|   `--
|-- MohidWater
|   `-- Makefile
|-- Mohid_Base_1
|   `-- Makefile
|-- Mohid_Base_2
|   `-- Makefile

User's guide

Get the latest version of the code at


  • Build
>make Nix

Please edit the first and save it as

  • Clean
>make Nix.clean

Please edit the ../makefiles/ file first and save it as ../makefiles/

  • Install
>make Nix.install

This will copy the binaries to a specific location on the harddisk. You can change the location by editing the file.


Use GNUmake! Attention: Rename gmake.exe to make.exe.

  • Build
>make win
  • Clean
>make win.clean

Administrator's guide

How do I add a new module file in MohidWater?

Suppose your new module filename is MohidWater/ModuleNew.F90, and it depends only on ModuleGlobalData, ModuleWaterproperties.mod and ModuleHydrodynamic.F90. Edit the Makefile file in the Linux/MohidWater folder and...

  • ... look for the FILES variables section:
> vim Solutions/Linux/MohidWater/Makefile
      ModuleNew.$(S) \
      ModuleAssimilation.$(S) \
      ModuleConsolidation.$(S) \
      ModuleFreeVerticalMovement.$(S) \
      ModuleJet.$(S) \
  • ... look for the Dependencies section at the end:
 ModuleNew.${O} : ModuleWaterProperties.${O} \
ModuleGauge.${O} : ModuleToga.${O}
ModuleSand.${O} : ModuleWaves.${O}

NOTE: Only the local dependencies of MohidWater are required. The external dependencies of MohidBase1 or MohidBase2 are not required.

  • That's it! You can now build the Linux solution!

How do I add a new module folder?

  1. Create a new folder (ex: MohidLand),
  2. Copy a regular folder Makefile into the new folder,
  3. Edit the Makefile:
    1. Edit the FILES variable
    2. Edit the dependencies
    3. Assign to variables TARGET and SRCDIR appropriate global variables names
  4. Edit the file:
    1. Create the global variables to be assigned to TARGET and SRCDIR (make sure the variable to be assigned as TARGET ends in $(SUFFPROG) if it's an executable or $(SUFFLIB) if it's a library).
    2. Edit the MODULES variable
    3. Add the module dependency


  1. The makefile methodology.
  2. The GNU make manual.
  3. The graph editor yED.