For a more practical but less complete guide on creating fpm projects see the packaging guide.
The details of the TOML parsing are implemented with using the tomlf module. -Generally, the interface to all TOML related functions for fpm is found in the proxy module fpm_toml.
-All the manifest types are bundled in fpm_manifest.
-While the specific subtables for the package configuration are found in the src/fpm/manifest directory, they should be reexported in the fpm_manifest module if they should be elsewhere in fpm.
All the manifest types are bundled in fpm_manifest.
+While the specific subtables for the package configuration are found in the src/fpm/manifest directory, they should be reexported in the fpm_manifest module if they should be elsewhere in fpm.
fpm is mainly used as a command line tool. To work with an fpm project as a user you can completely rely on the command line.
-The command line interface is build with the M_CLI2 module and can be found in fpm_command_line.
+The command line interface is build with the M_CLI2 module and can be found in fpm_command_line.
Once front-end inputs have been received from the package manifest and command line interface, fpm will construct an internal representation of the package and its dependencies. This internal representation is known as the package model. The model and its associated data types should encapsulate all the information required to correctly build a package and should be independent of the intended backend build system. Information stored in the model includes: build targets and their inter-dependencies; compiler and compiler flags; library linking information.
-For more information on the contents of the package model and the process for constructing it, please see fpm_model.
+For more information on the contents of the package model and the process for constructing it, please see fpm_model.
Once a complete package model has been constructed, it can be passed to a backend for either performing the compilation and linking of targets, or for generating configuration files for a third-party build system. -Currently, only a native backend is implemented in fpm. See fpm_backend for more information.
+Currently, only a native backend is implemented in fpm. See fpm_backend for more information.This documentation is generated by FORD. For more details on the project file and the comment markup in the source code visit the FORD documentation.
@@ -146,7 +147,7 @@