Yeah, that’s a good point. I’d probably add another feature to
libs/config which is CONFIG_SHELL, which allows you to turn off SHELL
for config, under the current system.
Right now, features are global variables set across the entire compile,
and recursively resolved. We could add a map, something like:
pkg.supress_features:
- “config”: “SHELL”
that would allow you to exclude certain features for specific packages,
and have this settable either in the target definition or the app. Does
that work?
Sterling
On 1 Aug 2016, at 11:53, Simon Ratner wrote:
Hi devs,
Is there a way for a project to exclude a feature provided by a
dependency?
For example, I want to include libs/shell to reuse its code, but do
not
want other packages (say, libs/config) compiling in shell-dependent
code.
I could always skip declaring it as a dep and supply the right
compiler
flags manually, but wondering if there is a better way.
Cheers,
Simon
