Good morning Torsten, As a followup on yesterdays meeting I verified that one can use #include in a preinclude file with the IAR compiler, and that works fine, so a workaround for the limit of only on

I still see the old calendar entry and not the new one. Thomas Den 2020-06-11 kl. 15:45, skrev Danny Ørndrup (DAOR) via lists.zephyrproject.org:

Today is a semi-holiday in Sweden and I will not be attending the call this afternoon. Progress on building a Hello World project with the IAR toolchain is slowly moving ahead, but I run into gcc rela

Thanks Carles, That was indeed the issue. --- thomasto@thomasto-VirtualBox:~/zephyrproject/zephyr$ cat `which west` | grep '#!' #!/usr/bin/python3 --- and python3 was symlinked to python3.6 while "pyt

I'm just starting up my IAR porting effort again and thought I would just build a simple out of the box project with the standard tools, but I'm immediately running into issues. I'm on Ubuntu 18.04.4

Den 2019-01-16 kl. 18:31, skrev Andy Ross: By "broadly-used industry extensions" you mean "gcc extensions" I guess? I did a quick test using some other C compilers I have, SunStudio 11/12, Keil uVisio

Den 2019-01-15 kl. 17:45, skrev Andy Ross: Would there be a problem adding a single anonymous member to this to make it standards compliant? After all, in C++ empty structs take up space while they do

While on the subject of language compliance, what about the frequent usage of non-standard gcc extensions that limits portability? I've started looking at making IAR Embedded Workbench a supported too