Support for dependency path relative to the fpm.toml it’s written in #719
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
To close #605 .
Description
The previous dependency
path
was always quite the same as the top-level project, which made it difficult to make such anfpm
package called by a higher-level project.Rust-cargo
seems to take a more reasonable approach: dependency paths are relative to theCargo.toml
it’s written in.This PR attempts to support such improvements, which will allow us to publish
fpm
packages with component libraries.What this PR does
dependency.f90::new_dependecy
anddependency.f90::new_dependecies
, adding theroot
optional argument.join_path("", "fpm.toml")
: