Build no tests by default

[Sideboard]

Fixes #92

• Change default behavior of build to exclude tests (sources with FPM_SCOPE_TEST)
• Add command line option --test to force building tests
• Update help messages

[awvwgk]

Thanks for sharing. Works nicely for a couple of projects I tested so far.

I have one suggestion about the new logical value, though.

[awvwgk]

It would be beneficial to make the include_tests logical part of the fpm_model_t, this way it can be easily accessed here without requiring to change the signature of all procedures until we get to the target list builder.

[Sideboard]

I agree that it would be nicer to have it in the model. But it did not seem to fit with the existing, more fundamental components:

type :: fpm_model_t
    character(:), allocatable :: package_name
    type(package_t), allocatable :: packages(:)
    type(compiler_t) :: compiler
    type(archiver_t) :: archiver
    character(:), allocatable :: fortran_compile_flags
    character(:), allocatable :: output_directory
    type(string_t), allocatable :: include_dirs(:)
    type(string_t), allocatable :: link_libraries(:)
    type(string_t), allocatable :: external_modules(:)
    type(dependency_tree_t) :: deps

    logical :: include_tests
end type fpm_model_t

Is this ok?

[LKedward]

Thanks very much @Sideboard! This all looks good - I agree with Sebastian's comment regarding the logical value, I think it is fine to include it in the model.

[Sideboard]

I changed the structure and renamed the internal settings name from test to build_tests to avoid semantic clashes due to inheritance (the external build option is still --test).

Shall I …

1. … squash the commits?
2. … remove the leftover space changes in call targets_from_sources(targets, model, error)?

[awvwgk]

Looks good to me. I usually squash small PRs on merge, so no worries about polluting the history here. But feel free to rebase your branch if you like.

[Sideboard]

Merge-squash is fine with me and there is no need for a bare rebase as far as I see. The second commit message can be scrapped.

[LKedward]

Great stuff, many thanks Sascha @Sideboard 👍

[Sideboard]

I just realized that the cargo option is --tests instead of --test. Should change that before the merge.

--test name...
Build the specified integration test. This flag may be specified multiple times and supports common Unix glob patterns.
--tests
Build all targets in test mode that have the test = true manifest flag set. By default this includes the library and binaries built as unittests, and integration tests. Be aware that this will also build any required dependencies, so the lib target may be built twice (once as a unittest, and once as a dependency for binaries, integration tests, etc.). Targets may be enabled or disabled by setting the test flag in the manifest settings for the target.

[awvwgk]

Thanks, I'll go ahead and merge.

[certik]

Thank you @Sideboard for this contribution!