How to configure the Layerscape SDK v17.12 to only build the OpenSSL libraries

[kuta42]

I don't need the OpenSSL apps, tests, and man pages in my target image, only the libraries. Is there a way to configure the Layerscape SDK v17.12 not to build them?

[Pavel]

Look at attached file. It is Readme file from LSDK 1712. Use examples from this file.

For example use the following commands:

flex-builder -c linux -a arm32 -m ls1021atwr -B menuconfig

or

flex-builder -c linux -a arm64 -m ls1046ardb -B menuconfig

Have a great day,
Pavel Chubakov

-----------------------------------------------------------------------------------------------------------------------
Note: If this post answers your question, please click the Correct Answer button. Thank you!
-----------------------------------------------------------------------------------------------------------------------

[kuta42]

These commands modify the Linux kernel configuration. But OpenSSL isn't part of the the Linux kernel. Isn't build_lsdk.cfg the config file that needs to be modified so that OpenSSL is built manually?

[Pavel]

Find the "Manual build" in the Section 9.1.1.2 of LSDK 1712 documentation:

https://www.nxp.com/docs/en/supporting-information/LSDK-KC-REV0.pdf

Find the following: "After installation verify that the binary is linking with the correct share library from /usr/local/lib:"

See also the following page:

https://www.openssl.org/source/

Have a great day,
Pavel Chubakov

-----------------------------------------------------------------------------------------------------------------------
Note: If this post answers your question, please click the Correct Answer button. Thank you!
-----------------------------------------------------------------------------------------------------------------------

[kuta42]

The instructions in Section 9.1.1.2 are also missing the requirement to set CROSS_COMPILE in the environment.

[kuta42]

From Section 9.1.1.2 of the LSDK 17.12 documentation:

This chapter is optional since the root filesystem can be configured to include both OpenSSL and cryptodev automatically. For reference, use the command "menuconfig" of flexbuild tool to change the applications list:

$ flexbuild -h <...> $ flexbuild menuconfig

Follow flexbuild documentation to finalize the building of the root filesystem and kernel on the host system.

Is this out-of-date? There is no "flexbuild" command, but one called "flex-builder". However, "flex-builder" doesn't accept a "menuconfig" argument:

$ flex-builder menuconfig
invalid instruction!

$

[kuta42]

So there's no way to configure flex-builder to only build the OpenSSL libraries? Should I submit a tech support case to add this as an enhancement?