Re: Explicitly disabling a feature

Oops... I didn't mean to reply-all. Sorry for the spam... Chris On Tue, Aug 02, 2016 at 08:16:08PM -0700, Christopher Collins wrote: > Hi Sterling, > > Just a heads up - this commit breaks the "newt test" command. The > problem is that there is no app when a package is being tested. The fix

Re: Explicitly disabling a feature

OK - added: pkg.feature_blacklist: ".*": SHELL pkg.feature_whitelist: ".*newtmgr.*": SHELL these two can be enabled in any of the top-level packages (app, bsp and target.) where the key is the package name, and the value is the feature name. if something is in the blacklist, it is

Re: Explicitly disabling a feature

OK, I’m going to start this. One more thing I’ll be adding. It’s a common case for features to be used to create defines by setting cflags. so, you define a feature “ADC_NRF52” and then you have a directive like: pkg.cflags.ADC_NRF52: -DADC_NRF52 I’m going to look at all created

Re: Explicitly disabling a feature

On 2 August 2016 at 01:48, Sterling Hughes wrote: > >> >> I had lots more here about managing feature dependencies in general, but >> ended up snipping it because it is a complex beast and I would need to >> give >> it more thought. In the meantime, I think the most