因为要使用rtt+emwin，在emwin532版本里，GUI_X_OS.c是和os的接口，在rtconfig.h里打开#define RT_USING_CMSIS_OS后，编译出了几条错误，如下
cmsis_rtthread.c
Error[Pe167]: argument of type "os_pthread" is incompatible with parameter of type "void (*)(void *)" \RTThread\rt-thread-v2.1.x\components\CMSIS\RTOS\cmsis_rtthread.c 33
Warning[Pe188]: enumerated type mixed with another type \RTThread\rt-thread-v2.1.x\components\CMSIS\RTOS\cm

Solutions

1. Convert INO files to CPP

2. Manual prototype declaration

#ifdef DO_NOT_USE
typedef int32_t delaytype;
void thisShouldNotAppearInTheBinary(delaytype timer); // aded manually
void thisShouldNotAppearInTheBinary(delaytype timer) {
  delay(timer);
}
#endif

Implement Python 3 bindings, so wasm3 can be easily used from Python.

Just like clicking on a function takes you to its definition, clicking on a struct reference like STR_4231 * pStruct = NULL; should take you to the definition of STR_4321

There are a number of items that need to be done to the code base to prepare it for the legal review. Some of these items may be deferred until after legal review

• Update to EPLv2
• Naming Conventions followed
• Provider information is set to the project’s formal name:
• Create CQs for dependencies aka third-party content
• All source files include a copyright and licen

For instance, if a user tries to write jalr x0 0(x1) the tooltip should also state that jalr has the format
jalr [rd] [rs] [imm].

Adding background to list of syntax styling of editor would allow to use dark syntax themes (like Solarized Dark)

Currently we specify the Verible configuration in the .core files. Now that Verible has support for config files, we should read the config from a config file instead.

google/verible#229

I was trying to build the Renode from scratch on empty machines just to see what exact steps are needed.

I used this document:
https://renode.readthedocs.io/en/latest/advanced/building_from_sources.html

And followed the command line approach to build whole renode packages and including the Robot framework (it was the build.sh -p and not the MonoDevelop/VisualStudio aproach).

Fo

Impact: documentation

Description
We should show an example MDF JSON in addition to defining the fields for people who like to pattern match.

Need documentation for developers and contributors