WICED Studio 4.0.1: All source code files have executable bit set

[AxLi_1746341]

mwf_mmfae​

All SDK source code files in Linux have executable bit set.

I'm sure I had reported this issue when you release 4.0.0.

I'm surprised it does not fix in 4.0.1.

[AxLi_1746341]

BTW, I had reported the installer creates 2 folders in SDK-4.0:

"WICED-Studio-4.0" and "WICED-Studio-4.0 "

~/WICED$ ls -l

total 8

drwxrwxr-x  2 axel axel 4096 Dec  1 13:36 WICED-Studio-4.0

drwxrwxr-x 10 axel axel 4096 Dec  1 13:37 WICED-Studio-4.0

The same issue on SDK-4.0.1.

PS. This time I install the SDK on a fresh new laptop.

[AxLi_1746341]

mifo​

The latest SDK still has executable bit set for all source files.

Will cypress team fix this in upcoming SDK release?

The linux users are very sensitive about the files with executable bit set.

[MichaelF_56]

I will ask someone to look into this and see why the permissions are set this way.

I'm pretty sure they are not changing when I upload them to the platform.

[MichaelF_56]

While investigating this issue, the SW team discovered that a bug had been introduced which changed all installed files to add the executable bit. 

I confirmed that it will be fixed in the next release.

[AxLi_1746341]

mifo wrote:

While investigating this issue, the SW team discovered that a bug had been introduced which changed all installed files to add the executable bit. 

I confirmed that it will be fixed in the next release.

mifo​

I have no idea what happen to the release process.

You said it was fixed, but obviously it's not.

All the source files in Wiced-studio-5.0 have executable bit set on Linux.

Can you redo the release for Linux?

[MichaelF_56]

I checked and this was not fixed in the current release because it caused some other undesired effects we could not introduce in this release.  We will look into adding it in the next.

[AxLi_1746341]

mifo wrote:

I checked and this was not fixed in the current release because it caused some other undesired effects we could not introduce in this release.  We will look into adding it in the next.

Still not fix in sdk-5.0.1.

[AxLi_1746341]

mifo wrote:

I checked and this was not fixed in the current release because it caused some other undesired effects we could not introduce in this release.  We will look into adding it in the next.

Still not fix in sdk-5.2.0.