/usr/share/doc/fcm/user_guide/annex_bld_cfg.html is in fcm 2016.12.0-1.
This file is owned by root:root, with mode 0o644.
The actual contents of the file can be viewed below.
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 101 102 103 104 105 106 107 108 109 110 111 112 113 114 115 116 117 118 119 120 121 122 123 124 125 126 127 128 129 130 131 132 133 134 135 136 137 138 139 140 141 142 143 144 145 146 147 148 149 150 151 152 153 154 155 156 157 158 159 160 161 162 163 164 165 166 167 168 169 170 171 172 173 174 175 176 177 178 179 180 181 182 183 184 185 186 187 188 189 190 191 192 193 194 195 196 197 198 199 200 201 202 203 204 205 206 207 208 209 210 211 212 213 214 215 216 217 218 219 220 221 222 223 224 225 226 227 228 229 230 231 232 233 234 235 236 237 238 239 240 241 242 243 244 245 246 247 248 249 250 251 252 253 254 255 256 257 258 259 260 261 262 263 264 265 266 267 268 269 270 271 272 273 274 275 276 277 278 279 280 281 282 283 284 285 286 287 288 289 290 291 292 293 294 295 296 297 298 299 300 301 302 303 304 305 306 307 308 309 310 311 312 313 314 315 316 317 318 319 320 321 322 323 324 325 326 327 328 329 330 331 332 333 334 335 336 337 338 339 340 341 342 343 344 345 346 347 348 349 350 351 352 353 354 355 356 357 358 359 360 361 362 363 364 365 366 367 368 369 370 371 372 373 374 375 376 377 378 379 380 381 382 383 384 385 386 387 388 389 390 391 392 393 394 395 396 397 398 399 400 401 402 403 404 405 406 407 408 409 410 411 412 413 414 415 416 417 418 419 420 421 422 423 424 425 426 427 428 429 430 431 432 433 434 435 436 437 438 439 440 441 442 443 444 445 446 447 448 449 450 451 452 453 454 455 456 457 458 459 460 461 462 463 464 465 466 467 468 469 470 471 472 473 474 475 476 477 478 479 480 481 482 483 484 485 486 487 488 489 490 491 492 493 494 495 496 497 498 499 500 501 502 503 504 505 506 507 508 509 510 511 512 513 514 515 516 517 518 519 520 521 522 523 524 525 526 527 528 529 530 531 532 533 534 535 536 537 538 539 540 541 542 543 544 545 546 547 548 549 550 551 552 553 554 555 556 557 558 559 560 561 562 563 564 565 566 567 568 569 570 571 572 573 574 575 576 577 578 579 580 581 582 583 584 585 586 587 588 589 590 591 592 593 594 595 596 597 598 599 600 601 602 603 604 605 606 607 608 609 610 611 612 613 614 615 616 617 618 619 620 621 622 623 624 625 626 627 628 629 630 631 632 633 634 635 636 637 638 639 640 641 642 643 644 645 646 647 648 649 650 651 652 653 654 655 656 657 658 659 660 661 662 663 664 665 666 667 668 669 670 671 672 673 674 675 676 677 678 679 680 681 682 683 684 685 686 687 688 689 690 691 692 693 694 695 696 697 698 699 700 701 702 703 704 705 706 707 708 709 710 711 712 713 714 715 716 717 718 719 720 721 722 723 724 725 726 727 728 729 730 731 732 733 734 735 736 737 738 739 740 741 742 743 744 745 746 747 748 749 750 751 752 753 754 755 756 757 758 759 760 761 762 763 764 765 766 767 768 769 770 771 772 773 774 775 776 777 778 779 780 781 782 783 784 785 786 787 788 789 790 791 792 793 794 795 796 797 798 799 800 801 802 803 804 805 806 807 808 809 810 811 812 813 814 815 816 817 818 819 820 821 822 823 824 825 826 827 828 829 830 831 832 833 834 835 836 837 838 839 840 841 842 843 844 845 846 847 848 849 850 851 852 853 854 855 856 857 858 859 860 861 862 863 864 865 866 867 868 869 870 871 872 873 874 875 876 877 878 879 880 881 882 883 884 885 886 887 888 889 890 891 892 893 894 895 896 897 898 899 900 901 902 903 904 905 906 907 908 909 910 911 912 913 914 915 916 917 918 919 920 921 922 923 924 925 926 927 928 929 930 931 932 933 934 935 | <!DOCTYPE html>
<html>
<head>
<title>FCM: User Guide: Annex: Declarations in FCM 1 build configuration
file</title>
<meta name="author" content="FCM team" />
<meta name="viewport" content="width=device-width, initial-scale=1.0" />
<link rel="icon" href="../etc/fcm-icon.png" type="image/png" />
<link rel="shortcut icon" href="../etc/fcm-icon.png" type="image/png" />
<link href="../etc/bootstrap/css/bootstrap.min.css" rel="stylesheet" media="screen" />
<link href="../etc/fcm.css" rel="stylesheet" media="screen" />
</head>
<body>
<div class="navbar navbar-inverse">
<div class="container-fluid">
<div class="navbar-header">
<a class="navbar-brand" href=".."><span class="fcm-version">FCM</span></a>
</div>
<div class="collapse navbar-collapse">
<ul class="nav navbar-nav">
<li><a href="../installation/">Installation</a></li>
<li><a class="active" href="#">User Guide</a></li>
</ul>
</div>
</div>
</div>
<div class="page-header">
<div class="fcm-page-content pull-right well well-sm"></div>
<h1>FCM: User Guide: Annex: Declarations in FCM 1 build configuration
file</h1>
</div>
<div class="container">
<div class="row">
<div class="col-md-12">
<p><em>The FCM 1 build system is deprecated. The documentation for the current
build system can be found at <a href="make.html">FCM Make</a>.</em></p>
<p>The following is a list of supported declarations for the configuration
file used by the FCM build system. Unless otherwise stated, the fields in all
declaration labels are not case sensitive. Build declarations can be made
either in a build configuration file or in an extract configuration file. In
the latter case, the prefix <code>BLD::</code> must be added at the beginning
of each label to inform the extract system that the declaration is a build
system declaration. (In a build configuration file, the prefix
<code>BLD::</code> is optional.)</p>
<dl>
<dt>CFG::TYPE</dt>
<dd>
<p>The configuration file type, the value should always be
<samp>bld</samp> for a build configuration file. This declaration is
compulsory for all build configuration files. (This declaration is
automatic when the extract system creates a build configuration
file.)</p>
<p>Example:</p>
<pre>
cfg::type bld
</pre>
</dd>
<dt>CFG::VERSION</dt>
<dd>
<p>The file format version, currently <samp>1.0</samp> - a version is
included so that we shall be able to read the configuration file
correctly should we decide to change its format in the future. (This
declaration is automatic when the extract system creates a build
configuration file.)</p>
<p>Example:</p>
<pre>
cfg::version 1.0
</pre>
</dd>
<dt>%<name></dt>
<dd>
<p><code>%<name></code> declares an internal variable
<var><name></var> that can later be re-used.</p>
<p>Example:</p>
<pre>
%my_variable -foo -bar
tool::fflags %my_variable
tool::cflags %my_variable
</pre>
</dd>
<dt>INC</dt>
<dd>
<p>This declares the name of a file containing build configuration. The
lines in the declared file will be included inline to the current
configuration file.</p>
<p>Example:</p>
<pre>
inc ~frva/var_stable_22.0/cfg/bld.cfg
# ... and then your changes ...
</pre>
</dd>
<dt>
DEST[::ROOTDIR]<br />
<del>DIR::ROOT</del>
</dt>
<dd>
<p>The destination of the build. It must be declared for each build.
(This declaration is automatic when the extract system creates a build
configuration file. The value is normally the path of the extract
destination.)</p>
<p>Example:</p>
<pre>
dest $HOME/my_build
</pre>
</dd>
<dt>USE</dt>
<dd>
<p>This inherits settings from a previous build. The value must be must
be either the configuration file or the root directory of a successful
build. Output of the build, the tools, the exclude dependency
declarations, the file type registers declarations are automatically
inherited from the declared build. Source directories and build targets
declarations may be inherited depending on the INHERIT declarations. (If
you have a USE declaration in an extract, the resulting build
configuration file will contain an automatic USE declaration, which
expects an inherited build at the extract destination.)</p>
<p>Example:</p>
<pre>
# Use VAR build 22.0
USE ~frva/var_22.0
</pre>
</dd>
<dt>INHERIT::<name>[::<pcks>]</dt>
<dd>
<p>This declares whether build targets (<name> =
<samp>target</samp>) or source directories (<name> =
<samp>src</samp>) can be inherited using the USE statement. By default,
source directories are inherited, while build targets are not. Use the
value <samp>true</samp> to switch on inheritance, or <samp>false</samp>
to switch off. For source directories declarations, the name of a
sub-package <pcks> can be specified. If a sub-package pcks is
specified, the declaration applies only to the files and directories
under the sub-package. Otherwise, the declaration applies globally.</p>
<p>Example:</p>
<pre>
inherit::target true
inherit::src false
</pre>
</dd>
<dt>SRC[::<pcks>]</dt>
<dd>
<p>This declares a source file/directory. You must specify the
sub-package <pcks> if the source file/directory is located outside
of the <samp>src/</samp> sub-directory of the build destination or if you
want to redefine the sub-package name of the source file/directory. The
name of the sub-package <pcks> must be unique. Package names are
delimited by double colons <code>::</code> or double underscores
<code>__</code>. If you declare a relative path, it is assumed to be
relative to the <samp>src/</samp> sub-directory of the build destination.
(This declaration is automatic when the extract system creates the build
configuration file. The list of declared source directories will be the
list of extracted source directories.)</p>
<p>Example:</p>
<pre>
src::var/code/VarMod_PF $HOME/var/src/code/VarMod_PF
</pre>
</dd>
<dt>SEARCH_SRC</dt>
<dd>
<p>This declares a flag to determine whether the build system should
search the <samp>src/</samp> sub-directory of the build root for a list
of source files. The automatic search is useful if the build system is
invoked standalone and the <samp>src/</samp> sub-directory contains the
full source tree of the build. The default is to search
(<samp>true</samp>). Set the flag to <samp>false</samp> to switch off the
behaviour. (When the extract system creates a build configuration file,
it declares all source files. Searching of the source sub-directory
should not be required, and so this flag is automatically set to
<samp>false</samp>.)</p>
<p>Example:</p>
<pre>
search_src false
</pre>
</dd>
<dt>TARGET</dt>
<dd>
<p>Specify the targets for the build. Multiple targets can be declared in
one or more declarations. These targets become the dependencies of the
default <samp>all</samp> target in the <em>Makefile</em>. It is worth
noting that <code>TARGET</code> declarations are cumulative. A later
declaration does not override an earlier one - it simply adds more targets
to the list.</p>
<p>Example:</p>
<pre>
target VarScr_AnalysePF VarScr_CovAccStats
target VarScr_CovPFstats
</pre>
</dd>
<dt>TOOL::<label>[::<pcks>]</dt>
<dd>
<p>This declaration is used to specify a build tool such as the Fortran
compiler or its flags. The <label> determines the tool you are
declaring. A TOOL declaration normally applies globally. However, where
it is sensible to do so, a sub-package <pcks> can be specified. In
which case, the declaration applies only to the files and directories
under the sub-package. A list of <label> fields is available
<a href="#tools-list">later in this annex</a>.</p>
<p>Example:</p>
<pre>
tool::fc sxmpif90
tool::fflags -Chopt -Pstack
tool::cc sxmpic++
tool::cflags -O nomsg -pvctl nomsg
tool::ar sxar
</pre>
</dd>
<dt>EXE_DEP[::<target>]</dt>
<dd>
<p>This declares an extra dependency for either all main program targets
or only <target> if it is specified. If <target> is
specified, it must be the name of a main program target. The value of the
declaration is a space delimited list. Each item in the list can either
be a valid name of a sub-package or the name of a valid object target. If
a sub-package name is used, the <em>make</em> rule for the main program
will be set to depend on all (non-program) object files within the
sub-package.</p>
<p>Example:</p>
<pre>
# Only foo.exe to depend on the package foo::bar and egg.o
exe_dep::foo.exe foo::bar egg.o
# All executables to depend on the package foo::bar and egg.o
exe_dep foo::bar egg.o
# Only foo.exe to depend on all objects
exe_dep::foo.exe
# All executables to depend on all objects
exe_dep
</pre>
</dd>
<dt>BLOCKDATA[::<target>]</dt>
<dd>
<p>This declares a BLOCKDATA dependency for either all main program
targets or only <target> if it is specified. If <target> is
specified, it must be the name of a main program target. The value of the
declaration is a space delimited list. Each item in the list must be the
name of a valid object target containing a Fortran BLOCKDATA program
unit.</p>
<p>Example:</p>
<pre>
# Only foo.exe to depend on blkdata.o
blockdata::foo.exe blkdata.o
# All executables to depend on fbd.o
blockdata fbd.o
</pre>
</dd>
<dt>EXCL_DEP[::<pcks>]</dt>
<dd>
<p>This declaration is used to specify whether a particular dependency
should be ignored during the automatic dependency scan. If a sub-package
<pcks> is specified, the declaration applies only to the files and
directories under the sub-package. Otherwise, the declaration applies
globally. The value of this declaration must contain one or two fields
(separated by the double colon <code>::</code>). The first field denotes
the dependency type, and the second field is the dependency target. If
the second field is specified, it will only exclude the dependency to the
specified target. Otherwise, it will exclude all dependency to the
specified type. The following dependency types are supported:</p>
<dl id="dependency-types">
<dt>USE</dt>
<dd>The dependency target is a Fortran module.</dd>
<dt>INTERFACE</dt>
<dd>The dependency target is a Fortran 9X interface block file.</dd>
<dt>INC</dt>
<dd>The dependency target is a Fortran INCLUDE file.</dd>
<dt>H</dt>
<dd>The dependency target is a pre-processor #include header file.</dd>
<dt>OBJ</dt>
<dd>The dependency target is a compiled binary object file.</dd>
<dt>EXE</dt>
<dd>The dependency target is an executable binary or script.</dd>
</dl>
<p>N.B. The following dependency targets are in the default list of
excluded dependencies:</p>
<dl>
<dt>Intrinsic Fortran modules:</dt>
<dd>
<ul>
<li>USE::ISO_C_BINDING</li>
<li>USE::IEEE_EXCEPTIONS</li>
<li>USE::IEEE_ARITHMETIC</li>
<li>USE::IEEE_FEATURES</li>
</ul>
</dd>
<dt>Intrinsic Fortran subroutines:</dt>
<dd>
<ul>
<li>OBJ::CPU_TIME</li>
<li>OBJ::GET_COMMAND</li>
<li>OBJ::GET_COMMAND_ARGUMENT</li>
<li>OBJ::GET_ENVIRONMENT_VARIABLE</li>
<li>OBJ::MOVE_ALLOC</li>
<li>OBJ::MVBITS</li>
<li>OBJ::RANDOM_NUMBER</li>
<li>OBJ::RANDOM_SEED</li>
<li>OBJ::SYSTEM_CLOCK</li>
</ul>
</dd>
<dt>Dummy declarations:</dt>
<dd>
<ul>
<li>OBJ::NONE</li>
<li>EXE::NONE</li>
</ul>
</dd>
</dl>
<p>Example:</p>
<pre>
excl_dep USE::YourFortranMod
excl_dep INTERFACE::HerFortran.interface
excl_dep INC::HisFortranInc.inc
excl_dep H::TheirHeader.h
excl_dep OBJ
excl_dep EXE
</pre>
</dd>
<dt>DEP::<pcks></dt>
<dd>
<p>This declaration is used to specify a dependency for a source file in
<pcks>. The value of this declaration must contain two fields
(separated by the double colon <code>::</code>). The first field denotes
the dependency type, and the second field is the dependency target. The
dependency types are the same as those for EXCL_DEP described <a href=
"#dependency-types">above</a>.</p>
<p>Example:</p>
<pre>
dep::foo/bar.f USE::your_fortran_mod
dep::foo/bar.f INTERFACE::her_fortran.interface
dep::foo/bar.f INC::his_fortran_inc.inc
dep::foo/bar.f H::their_header.h
dep::foo/bar.f OBJ::its_object.o
dep::foo/egg EXE::ham
</pre>
</dd>
<dt>NO_DEP::<pcks></dt>
<dd>
<p>This declaration is used to switch off/on dependency checking. If
<pcks> is specified in the label, the declaration applies to the
specified sub-package only.</p>
<p>Example:</p>
<pre>
# Switch on dependency checking only for "foo"
no_dep true
no_dep::foo false
</pre>
</dd>
<dt>EXE_NAME::<name></dt>
<dd>
<p>This renames the executable target of a main program source file
<name> to the specified value.</p>
<p>Example:</p>
<pre>
# Rename executable target of foo.f90 from "foo.exe" to "bar"
exe_name::foo bar
</pre>
</dd>
<dt>LIB[::<pcks>]</dt>
<dd>
<p>This declares the name of a library archive target. If <pcks> is
specified in the label, the declaration applies to the library archive
target for that sub-package only. If set, the name of the library archive
target will be named <samp>lib<value>.a</samp>, where <value>
is the value of the declaration. If not specified, the default is to name
the global library <samp>libfcm_default.a</samp>. For a library archive
of a sub-package, the default is to name its library after the name of
the sub-package.</p>
<p>Example:</p>
<pre>
# Rename the top level library "libfoo.a"
lib foo
# Rename the library for the sub-package "egg::ham"
# from "libegg__ham.a" to "libegg-ham.a"
lib::egg/ham egg-ham
</pre>
</dd>
<dt>PP[::<pcks>]</dt>
<dd>
<p>This declares whether a pre-processing stage is required. To switch on
pre-processing, set the value to <samp>true</samp>. If <pcks> is
specified in the label, the flag applies to the files within that
sub-package only. Otherwise, the flag affects source directories in all
packages. The pre-processing stage is useful if the pre-processor changes
the dependency and/or the argument list of the source files. The default
behaviour is skip the pre-processing stage for all source.</p>
<p>Example:</p>
<pre>
pp::gen true # switch on pre-processing for "gen" only
pp true # switch on pre-processing globally
</pre>
</dd>
<dt>SRC_TYPE::<pcks></dt>
<dd>
<p>This declaration is used to (re-)register the file type of the
sub-package <pcks> to associate with different file types. The
value of the declaration is a list of type flags delimited by the double
colon <code>::</code>. Each type flag is used internally to describe the
nature of the file. For example, a Fortran free source form containing a
main program is registered as
<code>FORTRAN::FORTRAN9X::SOURCE::PROGRAM</code>. A list of type flags is
available <a href="#infile-ext-types">later in this annex</a>.</p>
<p>Example:</p>
<pre>
src_type::foo/bar.f FORTRAN::FORTRAN9X::SOURCE::PROGRAM
</pre>
</dd>
<dt>INFILE_EXT::<ext></dt>
<dd>
<p>This declaration is used to re-register particular file name
extensions <ext> to associate with different file types. The value
of the declaration has a similar format to that of SRC_TYPE declaration
described above. A list of type flags is available <a href=
"#infile-ext-types">later in this annex</a>.</p>
<p>Example:</p>
<pre>
infile_ext::h90 CPP::INCLUDE
infile_ext::inc FORTRAN::FORTRAN9X::INCLUDE
</pre>
</dd>
<dt>OUTFILE_EXT::<type></dt>
<dd>
<p>This declaration is used to re-register the output file extension for
a particular <type> of output files. The value must be a valid file
extension. The following is a list of output file types in-use by the
build system:</p>
<dl id="outfile-ext-types">
<dt>OBJ</dt>
<dd>compiled object files<br />
[default = .o]</dd>
<dt>MOD</dt>
<dd>compiled Fortran module information files<br />
[default = .mod]</dd>
<dt>EXE</dt>
<dd>binary executables<br />
[default = .exe]</dd>
<dt>DONE</dt>
<dd><em>done</em> files for compiled source<br />
[default = .done]</dd>
<dt>IDONE</dt>
<dd><em>done</em> files for included source<br />
[default = .idone]</dd>
<dt>FLAGS</dt>
<dd><em>flags</em> files, compiler flags config<br />
[default = .flags]</dd>
<dt>INTERFACE</dt>
<dd>interface files for F9X standalone subroutines/functions<br />
[default = .interface]</dd>
<dt>LIB</dt>
<dd>archive object library<br />
[default = .a]</dd>
<dt>TAR</dt>
<dd>TAR archive<br />
[default = .tar]</dd>
</dl>
<p>Example:</p>
<pre>
# Output F9X interface files will now have ".foo" extension
outfile_ext::interface .foo
</pre>
</dd>
</dl>
<p id="tools-list">The following is a list of <label> fields that can
be used with a <code>TOOL</code> declaration. Those marked with an asterisk
(*) accept declarations at sub-package levels.</p>
<dl>
<dt>FC</dt>
<dd>The Fortran compiler.<br />
[default = <samp>f90</samp>]</dd>
<dt>FFLAGS *</dt>
<dd>Options used by the Fortran compiler.<br />
[default = ""]</dd>
<dt>FC_COMPILE</dt>
<dd>The option used by the Fortran compiler to suppress the linking
stage.<br />
[default = <samp>-c</samp>]</dd>
<dt>FC_INCLUDE</dt>
<dd>The option used by the Fortran compiler to specify the include search
path.<br />
[default = <samp>-I</samp>]</dd>
<dt>FC_MODSEARCH</dt>
<dd>The option used by the Fortran compiler to specify the search
path for the compiled module definition files. This option is often
unnecessary as it is normally covered by the include search path.<br />
[default = ""]</dd>
<dt>FC_DEFINE</dt>
<dd>The option used by the Fortran compiler to define a pre-processor
definition macro.<br />
[default = <samp>-D</samp>]</dd>
<dt>FC_OUTPUT</dt>
<dd>The option used by the Fortran compiler to specify the output file
name.<br />
[default = <samp>-o</samp>]</dd>
<dt>CC</dt>
<dd>The C compiler.<br />
[default = <samp>cc</samp>]</dd>
<dt>CFLAGS *</dt>
<dd>Options used by the C compiler.<br />
[default = ""]</dd>
<dt>CC_COMPILE</dt>
<dd>The option used by the C compiler to suppress the linking stage.<br />
[default = <samp>-c</samp>]</dd>
<dt>CC_INCLUDE</dt>
<dd>The option used by the C compiler to specify the include search
path.<br />
[default = <samp>-I</samp>]</dd>
<dt>CC_DEFINE</dt>
<dd>The option used by the C compiler to define a pre-processor definition
macro.<br />
[default = <samp>-D</samp>]</dd>
<dt>CC_OUTPUT</dt>
<dd>The option used by the C compiler to specify the output file
name.<br />
[default = <samp>-o</samp>]</dd>
<dt>LD *</dt>
<dd>Name of the linker or loader for linking object files into an
executable. If not set, use the compiler of the source file containing the
main program.<br />
[default = ""]</dd>
<dt>LDFLAGS *</dt>
<dd>The flags used by the linker or loader.<br />
[default = ""]</dd>
<dt>LD_OUTPUT</dt>
<dd>The option used by the linker or loader for the output file name (other
than the default <samp>a.out</samp>).<br />
[default = <samp>-o</samp>]</dd>
<dt>LD_LIBSEARCH</dt>
<dd>The option used by the linker or loader for specifying the search path
for link libraries.<br />
[default = <samp>-L</samp>]</dd>
<dt>LD_LIBLINK</dt>
<dd>The option used by the linker or loader command for linking with a
library.<br />
[default = <samp>-l</samp>]</dd>
<dt>AR</dt>
<dd>The archive command.<br />
[default = <samp>ar</samp>]</dd>
<dt>ARFLAGS</dt>
<dd>The options used for the archive command to create a library.<br />
[default = <samp>rs</samp>]</dd>
<dt>FPP</dt>
<dd>The Fortran pre-processor command.<br />
[default = <samp>cpp</samp>]</dd>
<dt>FPPKEYS *</dt>
<dd>The Fortran pre-processor will pre-define each word in this setting as
a macro.<br />
[default = ""]</dd>
<dt>FPPFLAGS *</dt>
<dd>The options used by the Fortran pre-processor.<br />
[default = <samp>-P -traditional</samp>]</dd>
<dt>FPP_DEFINE</dt>
<dd>The option used by the Fortran pre-processor to define a macro.<br />
[default = <samp>-D</samp>]</dd>
<dt>FPP_INCLUDE</dt>
<dd>The option used by the Fortran pre-processor to specify the include
search path.<br />
[default = <samp>-I</samp>]</dd>
<dt>CPP</dt>
<dd>The C pre-processor command.<br />
[default = <samp>cpp</samp>]</dd>
<dt>CPPKEYS *</dt>
<dd>The C pre-processor will pre-define each word in this setting as a
macro.<br />
[default = ""]</dd>
<dt>CPPFLAGS *</dt>
<dd>The options used by the C pre-processor.<br />
[default = <samp>-C</samp>]</dd>
<dt>CPP_DEFINE</dt>
<dd>The option used by the C pre-processor to define a macro.<br />
[default = <samp>-D</samp>]</dd>
<dt>CPP_INCLUDE</dt>
<dd>The option used by the C pre-processor to specify the include search
path.<br />
[default = <samp>-I</samp>]</dd>
<dt>MAKE</dt>
<dd>The <code>make</code> command.<br />
[default = <samp>make</samp>]</dd>
<dt>MAKEFLAGS</dt>
<dd>The options used by the <code>make</code> command.<br />
[default = ""]</dd>
<dt>MAKE_SILENT</dt>
<dd>The option used by the <code>make</code> command to specify silent
operation.<br />
[default = <samp>-s</samp>]</dd>
<dt>MAKE_JOB</dt>
<dd>The option used by the <code>make</code> command to specify the number
jobs to run simultaneously.<br />
[default = <samp>-j</samp>]</dd>
<dt>GENINTERFACE *</dt>
<dd>The command/method to extract the calling interfaces of top level
subroutines and functions in a Fortran 9X source. Supported values are
<samp>f90aib</samp> and <samp>none</samp> (to switch off interface
generation). If not specified, the system will use its own internal logic.
<br />
[default = (not specified)]</dd>
<dt>INTERFACE *</dt>
<dd>Generate Fortran 9X interface files with root names according to either
the root name of the source <samp>file</samp> or the name of the
<samp>program</samp> unit.<br />
[default = <samp>file</samp>]</dd>
</dl>
<p id="infile-ext-types">The following is a list of type flags that are
currently in-use (or <dfn>* reserved</dfn>) by the build system for TYPE and
INFILE_EXT declarations:</p>
<dl>
<dt>SOURCE</dt>
<dd>a source file containing program code of a supported language
(currently Fortran, FPP, C and CPP).</dd>
<dt>INCLUDE</dt>
<dd>an include file containing program code of a supported language
(currently Fortran, FPP, C and CPP).</dd>
<dt>FORTRAN</dt>
<dd>a file containing Fortran code.</dd>
<dt>FORTRAN9X</dt>
<dd>a file containing the Fortran free source form. This word must be used
in conjunction with the word <code>FORTRAN</code>.</dd>
<dt>FPP</dt>
<dd>a file containing Fortran code requiring pre-processing.</dd>
<dt>FPP9X</dt>
<dd>a file containing Fortran free source form requiring pre-processing.
This word must be used in conjunction with the word <code>FPP</code>.</dd>
<dt>C</dt>
<dd>a file containing C code.</dd>
<dt>CPP</dt>
<dd>a file containing CPP include header.</dd>
<dt>INTERFACE</dt>
<dd>a file containing a Fortran 9X interface block.</dd>
<dt>PROGRAM</dt>
<dd>a file containing a main program.</dd>
<dt>MODULE</dt>
<dd>a file containing a Fortran 9X module.</dd>
<dt>BINARY</dt>
<dd>a binary file.</dd>
<dt>EXE</dt>
<dd>an executable file. This word must be used in conjunction with the word
<code>BINARY</code>.</dd>
<dt>LIB</dt>
<dd>an archive library. This word must be used in conjunction with the word
<code>BINARY</code>.</dd>
<dt>SCRIPT</dt>
<dd>a file containing source code of a scripting language.</dd>
<dt>PVWAVE</dt>
<dd>a file containing executable PVWAVE scripts. This word must be used in
conjunction with the word <code>SCRIPT</code>.</dd>
<dt>SQL</dt>
<dd>a file containing SQL scripts. This word must be used in conjunction
with the word <code>SCRIPT</code>.</dd>
<dt>GENLIST</dt>
<dd>a GEN List file.</dd>
<dt>OBJ</dt>
<dd><dfn>(* reserved)</dfn> an object file. This word must be used in
conjunction with the word <code>BINARY</code>.</dd>
<dt>SHELL</dt>
<dd><dfn>(* reserved)</dfn> a file containing executable shell scripts.
This word must be used in conjunction with the word
<code>SCRIPT</code>.</dd>
<dt>PERL</dt>
<dd><dfn>(* reserved)</dfn> a file containing executable Perl scripts. This
word must be used in conjunction with the word <code>SCRIPT</code>.</dd>
<dt>PYTHON</dt>
<dd><dfn>(* reserved)</dfn> a file containing executable Python scripts.
This word must be used in conjunction with the word
<code>SCRIPT</code>.</dd>
<dt>TCL</dt>
<dd><dfn>(* reserved)</dfn> a file containing executable TCL scripts. This
word must be used in conjunction with the word <code>SCRIPT</code>.</dd>
</dl>
</div>
</div>
</div>
<hr/>
<div class="container-fluid text-center">
<div class="row"><div class="col-md-12">
<address><small>
© British Crown Copyright 2006-16
<a href="http://www.metoffice.gov.uk">Met Office</a>.
See <a href="../etc/fcm-terms-of-use.html">Terms of Use</a>.<br />
This document is released under the British <a href=
"http://www.nationalarchives.gov.uk/doc/open-government-licence/" rel=
"license">Open Government Licence</a>.<br />
</small></address>
</div></div>
</div>
<script type="text/javascript" src="../etc/jquery.min.js"></script>
<script type="text/javascript" src="../etc/bootstrap/js/bootstrap.min.js"></script>
<script type="text/javascript" src="../etc/fcm.js"></script>
<script type="text/javascript" src="../etc/fcm-version.js"></script>
</body>
</html>
|