More control for making or skipping make

When building with or without modules, it will be useful to selective suppress building of some components.

• compile all of OpenFOAM, but without any modules
• later compile a module indvidually

I'm thinking of places where we might want to have a module such as visualization, or adios added as an additional RPM or spack package on top of an existing OpenFOAM installation.

Ideas:

1. If a Allwmake.disabled exists at the same level as a Allwmake file, skip it.
2. Use a Allwmake.override instead of Allwmake file at the same level.
3. Rename Allwmake file to Allwmake.enabled and symlink back to Allwmake when it is enabled.
4. Add in a minor logic into the overridable Allwmake. For example,

   enabled=true
   if [ "$enabled" != true ]
   then
       echo "$0: is disabled"
       exit 0
   fi

@Development

changed the description

My current tendency is with Allwmake.override since it could be used for anything and looks a bit like debian/rules entries.

I'd go for a option of Allwmake. Especially to supress 'wmake all' of modules.

if the required dependencies are not available, the compilation would fail anyhow.

other options - no specific comment.

I'm coming around to the use of the Allwmake.override since you can choose to skip the build or provide some custom build process

From user perspective the simpler to understand what to do, the better.

I'd go for a option of Allwmake. And leave the modules apart for individual compilation

mentioned in commit 816e96e0

closed

reopened

Tag this one on here too - the current build system places wmake executables (lemon, wmkdepend) in a subdirectory. Eg, wmake/platforms/linux64Gcc/wmkdepend which makes it more difficult to create a pure sources-only or binaries-only set of packages.

One possibility would be to always place them in the project-directory. Eg, OpenFOAM-com/platforms/tools/linux64Gcc/.

mentioned in commit a8b6d01b

closed

mentioned in commit ba6479bf

mentioned in commit cc9db3ea