Regularly there is a thematic directory, e.g. sas for spectral
analysis with a subdirectory p (subroutines) and several p/m* for
main programs according to different needs (libraries, options, ...)
In each main-prog directory there is a sh script fcmd
that sets parameters and call ~/bin/fcmb for compilation
In each sub-prog directory there are one or more libraries (static,
libshort.a). Compilation is most often done with sh script
~/bin/fcs If there are specific needs, local scripts must be
So far this is true on linux.
On Cygwin, the gfortran compiler is used. Occasionally that compiler
is useful also on Linux since it's less tolerant, more strict on
coding, and more widely used.
Therefore the scripts have different names,
~/bin/gfmb for mains
~/bin/gfs for sub-programs
local script fcmd can be controlled from the environment as to the
use of fcmb or gfmb. You can create a local gfmd if you like.
That's many words instead of an outright: I don't use make (the
dependencies are a jungle).
If dependencies remain unresolved at the linker stage, you're told
by the linker's output what's missing.
At the end of this page you will see a list of all libraries I have
generated within the tide context.
Pgplot has a directory /usr/local/pgplot/