it's difficult to find the root cause without having the entire system on the table...
First of all, the provided Build Envrionment is prepared and tested with the GCC compiler in combination with the provided makefiles, startup code,... The Evaluatioin Edition of the STM32 Platform Package contains only libraries, that are compiled with GCC and the corresponding runtime libraries. Although it might be possible to link these libraries with other toolchains - the behaviour might be unpredictable...
The main idea of the Evaluation Edition is the familiarization with Embedded Wizard and its workflow. When you are using the Profdessional Edtion of Embedded Wizard Studio, you will get the source code of the Runtime Environment and the Graphics Engine, so it will be easy to compile and link everything with the toolchain of your choice. As long as you are working with the Evaluation Edition, we recommend to use the provided setting as it is.
See also 'using stm32 build environment with third party toolchain'.
yes, the libewgfx-eval.a and the libewrte-eval.a are the right choice. (-mu means 'memory usage' that have to be used when compiling with the flag EW_PRINT_MEMORY_USAGE and the -r90 / -r180 / -r270 are used when the project is created with a different ScreenOrientation).
Nevertheless, GCC compiler is one thing, the different compiler flags, the used libraries and the used startup-code is another issue that might have an impact to the resulting binary.
Ask Embedded Wizard
Welcome to the question and answer site for Embedded Wizard users and UI developers.
Ask your question and receive answers from the Embedded Wizard support team or from other members of the community!