topic How to make a middleware not to be optional? in MCUX SDK Generator

How to make a middleware not to be optional?

PetrKraus — Thu, 24 Oct 2019 08:30:00 GMT

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.

Re: How to make a middleware not to be optional?

nxa13122 — Fri, 25 Oct 2019 07:35:57 GMT

Hi Jan,

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

A 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

Holt

Re: How to make a middleware not to be optional?

nxa13122 — Thu, 07 Nov 2019 01:49:42 GMT

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 .