so new that no one ever told me about Windows/Capitalization

General Discussion
1

So, I am trying currently to build with CCS and now, the hard drive version and not the cloud version, they use VS Code styles of IDE behaviors. Anyway…

  1. Capitalization from windows, not linux, is unheard of now
  2. It is almost like they did it on purpose

Anyway, in CCS, I am building files that used to get built with Keil/4/5/6.

But…Windows does not understand that I have to get my files, different upper/lower case, with how they are already situated.

They are situated in the way that Linux would understand. So, for instance:

# Ideas around Windows and Linux

systick.c is not the same as SysTick.c in Linux

systick.c and SysTick.c are the same in Windows

No wonder people from e2e think I am some void.

Seth

2

So,

I brought this up. I brought up the idea to complain in public I guess.

Now, not only do I have to rearrange about 100 files or more, I have to rename them. Hopefully, I can get it done without error. If not, AW!

Seth

3

Option in later versions of 10; https://learn.microsoft.com/en-us/windows/wsl/case-sensitivity

1 Like
4

While it is technically possible to enable through fsutil, it’s very painful.

and the fun doesn’t stop there; try to make a file called aux.c and see what happens.

Besides, Windows has always been, is and will continue to be case-insensitive OOTB.
Nothing new here…

1 Like
5

Forget about it. I am not too educated in Windows or Environment Variables for now.

I figured I could just put the arm-none-eabi- PATH in rotation and it would work. No so much these days for whatever reason.

Seth

P.S. I am going to call this post finalized. I will try on another system.