[Bug]: NOOPT Builds Broken For Consumers

[os-d]

Is there an existing issue for this?

• I have searched existing issues

Current Behavior

mu_crypto_release (in the shared crypto, not one crypto case) only publishes DEBUG and RELEASE binaries, but the dsc.inc files select which file to build by using $TARGET. This breaks the NOOPT build because the path doesn't exist.

Also, the fdf.inc files only include the binaries if the TARGET is DEBUG or RELEASE. For NOOPT builds this doesn't include any crypto binary.

Expected Behavior

NOOPT builds and boots should work. NOOPT builds from here are not very useful, so the dsc.inc and fdf.inc files should be updated to default to DEBUG unless the TARGET is RELEASE.

OneCrypto should also confirm it doesn't have the same issue.

Steps To Reproduce

Build a platform with TARGET=NOOPT.

Build Environment

- OS(s):
- Tool Chain(s):
- Targets Impacted:

Version Information

old_main

Urgency

Medium

Are you going to fix this?

Someone else needs to fix it

Do you need maintainer feedback?

No maintainer feedback needed

Anything else?

No response

[Flickdm]

Closing as not planned -- if this is incorrect lets reopen