How to make a middleware not to be optional?

cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 

How to make a middleware not to be optional?

540 Views
PetrKraus
NXP Employee
NXP Employee

jann.

There is the AML middleware component in the SDK release 11. That component is optional now. We don't want it to be optional. We need that component to be included into an SDK package only when there is either Sigfox or LVHB optional middleware components selected for the package.

Please, advise how to remove the AML from a list of optional components, but to keep it as a dependency for the Signfox and LVHB components.

0 Kudos
2 Replies

523 Views
nxa13122
NXP Employee
NXP Employee

Since the AML is the shared layer for sigfox and LVHB, so we can remove the ui_control of it and set it required by the ui control of sigfox OR LVHB.

This issue has been fixed in https://jira.sw.nxp.com/browse/KPSDK-31047 .

0 Kudos

523 Views
nxa13122
NXP Employee
NXP Employee

Hi Jan,

This is something we need to approve in the sdk generator and kex deployment system.

sketchy way we have some attribute to tell that this middleware is not optional.

I have created JIRAs to track it:

https://jira.sw.nxp.com/browse/SDKGEN-1258

https://jira.sw.nxp.com/browse/KEX-6697

BR

Holt

0 Kudos