According to the comments in the fpm.toml generated with the --full option, in the [library] section we can use a list of directories:
# this can be a list:
#source-dir=["src", "src2"]
I tried in a new project. I have simply created a src2/ directory and add it in my fpm.toml:
[library]
source-dir=["src", "src2"]
but fpm 0.11.0 complains:
$ fpm build
<ERROR> *cmd_build* Package error: Manifest key [library.source-dir] does not allow list input
STOP 1
Am I doing something wrong? Or is this feature not yet implemented? Or is it a bug?
Thanks @ivanpribec !
So the bug is in the documentation.
I wanted to use this feature to convert a project which can be built with or without GTK GUI. I will try to tinker a solution with symbolic links that could be switched depending on which type of build I want.
The help text for the new subcommand and the web page for the manifest file should be changed. The web page is more an omission. It explicitly says multiple include directories are allowed but leaves the src directory undefined.
Multiple subdirectories are allowed so moving everything into src/ works without having to flatten everything into a single directory.
The work-arounds I have seen are to set the directory to “.”. Using a dot works but probably accidentally so I would not recommend that.
The other is to leave the files where they are and make links to them in src. Links are not particularly portable across different OS and it can be unclear
so that has drawbacks.
The other work-around seems to be to make each directory into it’s own package and use them as local dependencies. This is sometimes appropriate
but usually means moving files around as much as moving everything to src/,
and can complicate using git or other packages.
The main reason I have seen for wanting multiples is when the package already exists and is built with Cmake or Make or other products already and moving everything into a single file would break the existing methods.
Personally, other than not being able to do something the way I have done it before I cannot think of a reason to not start a newly created fpm project in src/.
As mentioned in the above thread it is probable other factors are not expecting more than one directory (such as a registry) so making a new package with multiple directories is swimming upstream at this point. So maybe stricter checking is in order but not allowing a dot means you cannot create a single-directory package, for better or for worse.
1 Like