Request/Idea: TouchGFX library built with Clang.

[JureL]

Hi @Romain DIELEMAN, @Osman SOYKURT, @LouisB 

We are using TouchGFX library, now for almost 5 years. We are very satisfied with the product and its's regular updates/improvments and new featuers. However we have one limitation: the current library does not officially support the Clang compiler. We are using SEGGER compiler - Clang for our projects so I needed to do some workarounds for current gcc library to got it working with it. Would it be possible to add support for Clang compiler in future releases? This way it would also be directly compatible with the SEGGER compiler and no other workarounds would be required. 

I am looking forward to your positive response and the continued evolution of the TouchGFX library.

[LouisB]

Hello @JureL ,

Thanks for suggestion, I will bring that idea to team.
Best regards,

[JureL]

Hi @Romain DIELEMAN, @Osman SOYKURT, @LouisB 

Did you bring that idea to the touchgfx team ?

Can we expect library built with clang in future release?

Thank you.

Best regards, Jure

[HRidd.2]

Or even better just provide sources for TouchGFX instead of a pre-built static library! I understand this is likely due to licensing issues leftover from acquiring Draupner Graphics (OG creater of TouchGFX) but TouchGFX is a bit of an albatross given all of ST's other HAL/framework code is readily available. Debugging is also ALWAYS easier if you can see source code (rather than assembly) so I feel like it would save ya'll a lot of inbound calls from confused customers as well. @LouisB is there any chance of that ever happening? We use it on our current product but sadly the hard requirement of using arm-none-eabi-gcc would prevent me from using it again :( 

On the original topic,@JureL as an experiment I've compiled one of my projects that uses TouchGFX with Clang (after a LOT of work to resolve all sorts of surprises) and while everything compiles + links, something definitely is wrong with how the TouchGFX library code is running as only garbage appears on screen (even though through logging I can see my firmware is running fine without hitting any asserts/etc.).