Fix emscripten config

[ChristophStrehle]

Leaving the emscripten macros, returning a value, empty was leading to syntax errors

The pointer returned by EM_ASM_PTR must be freed by calling free see
https://emscripten.org/docs/api_reference/emscripten.h.html?highlight=em_asm_ptr#c.EM_ASM_PTR

[chrchr-github]

Maybe we should add include detection here:

cppcheck/tools/donate_cpu_lib.py

Line 680 in dc385f3

include_mappings = {'boost': ['<boost/'],

[chrchr-github]

@firewave Should we bump the CLIENT_VERSION in donate_cpu_lib.py?

[firewave]

@firewave Should we bump the CLIENT_VERSION in donate_cpu_lib.py?

Yes, absolutely.

[ChristophStrehle]

@firewave, @chrchr-github Sorry I missed the version number in this file. I incremented the patch version now

[chrchr-github]

Maybe we should add include detection here:

cppcheck/tools/donate_cpu_lib.py

Line 680 in dc385f3

include_mappings = {'boost': ['<boost/'],

According to the discussion in #6461, this needs to be commented out at least until the next release. Sorry for the confusion.

[ChristophStrehle]

According to the discussion in #6461, this needs to be commented out at least until the next release

I guess this case is slightly different from #6461 as the emscripten.cfg was there in the previous release. I just added a new test and an implementation instead of leaving the macros empty.

[firewave]

I guess this case is slightly different from #6461 as the emscripten.cfg was there in the previous release. I just added a new test and an implementation instead of leaving the macros empty.

Yes. In this case it does not need to be disabled. The file was added four years ago and never was fully integrated.