When adding fpm to a project that already has one or more non-fpm build system(s) (e.g., ones based on make or cmake), not being able to tell fpm to ignore certain subdirectories and/or files means the involved files must be moved out of the locations where fpm attempts to build every file found. Any such directory/file moves are likely to necessitate changes to the other build system(s). Also, there's the social issue associated with having to ask for what sometimes feels like a big change to a project.
Possible Solution
Add a feature that gives users the ability to specify in the manifest that a certain subdirectory or file should be ignored. Being able to insert something like the following in a fpm.toml file might suffice:
beddalumia
commented
1 year ago
Description
When adding
fpmto a project that already has one or more non-fpmbuild system(s) (e.g., ones based onmakeorcmake), not being able to tellfpmto ignore certain subdirectories and/or files means the involved files must be moved out of the locations wherefpmattempts to build every file found. Any such directory/file moves are likely to necessitate changes to the other build system(s). Also, there's the social issue associated with having to ask for what sometimes feels like a big change to a project.Possible Solution
Add a feature that gives users the ability to specify in the manifest that a certain subdirectory or file should be ignored. Being able to insert something like the following in a
fpm.tomlfile might suffice:Additional Information
No response