Clarify WOLFSSL_ROOT location for ESP8266 make builds

[gojimmypi]

Description

Applies only to ESP8266 make builds.

Adds clarification in wolfssl_client example for Espressif ESP8266 builds on how the WOLFSSL_ROOT value should be used (relative, not absolute), in both the README and component.mk file comments.

Replaces spaces with tabs in project Makefile

Also updates .gitignore to explicitly:

• always include Makefile and component.mk files in the /IDE/Espressif path.
• always exclude sdkconfig.debug and sdkconfig.release files, also in the /IDE/Espressif path.

To aid in identification of path used, addition details are printed at build time. For example:

***********  wolfssl component ************
WOLFSSL_ROOT defined: ../../../../workspace/wolfssl-master
WOLFSSL_ROOT actual:  /mnt/c/workspace/wolfssl-master
********** end wolfssl component **********

Edit:

I've added 20e0e12 as a separate commit to exclude ESP8266 binaries from source files generated by autogen & build process. This allows a freshly cloned wolfssl to be used during RTOS SDK make without these files:

# COMPONENT_OBJS += $(WOLFSSL_ROOT)/wolfcrypt/src/async.o
# COMPONENT_OBJS += $(WOLFSSL_ROOT)/wolfcrypt/src/selftest.o
# COMPONENT_OBJS += $(WOLFSSL_ROOT)/wolfcrypt/src/wolfcrypt_first.o
# COMPONENT_OBJS += $(WOLFSSL_ROOT)/wolfcrypt/src/wolfcrypt_last.o

Once this PR approved, I will create a separate PR for the other examples.

Fixes zd# 18102

Testing

How did you test?

Tested only for the ESP8266, and only manually for in-place, and relocated wolfssl_client build with RTOS SDK make builds.

Checklist

• [ ] added tests
• [ ] updated/added doxygen
• [ ] updated appropriate READMEs
• [ ] Updated manual and documentation

[gojimmypi]

jenkins retest this please

[gojimmypi]

jenkins retest this please