I need to add some library includes to a plugin, outside the sources folder, so I'm using and the
Include=, I see a few improvements to make it much better.
We have to specify file by file, there's no way to include a complete folder. I have only 20 sources, but some libraries have dozens or hundreds of includes that should be listed one by one. Imagine if we need to upgrade the lib, having to check it all what's new and what's gone. It shouldn't be that painful.
The folder include option should be recursive or not recursive.
If I just use
Include=, it does not work. It has to be
Include.Win64=. Having the ability to add per platform is great, but in most cases the sources are common to all platforms. I'm adding around 20 sources, duplicating them all. This is unnecessary and prone to error.
In XCode, there's one group for each included folder files, would be much better if the groups were created hierarchically. Example, instead of having 2 groups like
/xxx/includegroup is much better. Edit: Ok, it seems to be hierarchical, but with the full path name in the group name, and file names in lowercase.
Those groups could be inside the
sourcesgroup, or everything into one
I can include everything I need right now, but instead of writing a few simple and clear lines, I'm writing 40, checking path by path, with duplicates...