fab
fab copied to clipboard
metomi
Flexible build system for scientific software
This pull request is related to Issue https://github.com/hiker/fab/issues/18 and the pull request on hiker fab: hiker#19. The purpose is to allow each x90 file to have its specific transformation script....
This is a small optimisation to save the amount of network traffic involved in setting up the workflow environment. It is offset by disc usage.
It is valid for Fortran source files to contain multiple program units. This is certainly done by the pFUnit processing script which generates source files with both program and module...
Some UM files contains OMP sentinels for use statements, e.g. control/grids/p_to_t_vol.F90: ``` !$ USE compute_chunk_size_mod, ONLY: compute_chunk_size ! Note OpenMP sentinel ``` Since fparser does not support this, FAB misses...
As well as setting a preprocessor macro `_OPENMP` which may be used in `#ifdef` lines the OpenMP standard also specifies a magic comment for including code only when compiling with...
There is all sorts of default magic built in but we might prefer simply to tell Fab what to use.
The way compiler properties are managed is rather hap-hazard at the moment. For each compiler we need to know things such as the argument used to specify where module files...
Currently we have to rely on a big pile of magic rather than simply specifying which one.
At the moment it looks like you have to add linker arguments by hand (or use the MPI compiler in the link stage) but that is going to be tricky...