PelionIoT / mbed-cloud-client

Description of defect

Note: this is a duplicate of ARMmbed/mbed-os#13989 to track progress in mbed-cloud-client as well.

(cc @YannLocatelli)

This is the exact same issue as described in ARMmbed/mbed-os#10022.

The issue was fixed in ARMmbed/mbed-os#10042

But then the changes were reverted and the issue brought back with ARMmbed/mbed-os#13217 and ARMmbed/mbed-os@3e011a9

On the cloud client end, the PR mentioned by @adamelhakham (ARMmbed/mbed-os#10022 (comment)) is nowhere to be found.

Target(s) affected by this defect ?

Custom target with BLE and Pelion

Toolchain(s) (name and version) displaying this defect ?

arm-none-eabi-gcc --version
arm-none-eabi-gcc (GNU Arm Embedded Toolchain 9-2020-q2-update) 9.3.1 20200408 (release)

What version of Mbed-os are you using (tag or sha) ?

6.5.0

What version(s) of tools are you using. List all that apply (E.g. mbed-cli)

mbed --version
1.10.4

mbed-tools --version
3.5.1.dev36

How is this defect reproduced ?

Setup Pelion mbed-cloud-client using a target with BLE.

@ladislas could you provide the actual conflict you are seeing in the issue?

We have the error message while compiling:

mbed-cloud-client/mbed-client-pal/Source/PAL-Impl/Services-API/pal_Crypto.h

Lines 22 to 24 in f72a23e

    
           #ifndef _PAL_H 
        
               #error "Please do not include this file directly, use pal.h instead" 
        
           #endif

That is because both BLE and cloud-client have a file named pal_crypto.h

Internal ticket: https://armiot.atlassian.net/browse/IOTCLT-4603

will be fixed in 4.9.0 release.

@ladislas issue should be resolved now in https://github.com/PelionIoT/mbed-cloud-client/releases/tag/4.9.0

Thanks a lot!

	#ifndef _PAL_H
	#error "Please do not include this file directly, use pal.h instead"
	#endif