You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When the code analizer runs when the target folder (Release) does not exist the code analizer returns an error and fall back to defaults making the indexer mis lots of knowledge.
The root cause is the opt file that is copied to Release/sketch/opt during the pre build step. Therefore the file is not guaranteed to exists and the code analizer may fail.
As there is no easy way to start the code analizer this is pretty annoying.
This issue is found as part of #1491
The text was updated successfully, but these errors were encountered:
If you do not use the opt file (a file to allow for additional compile options) you can try following workaround
Modify platform.txt
replace compiler.extra_flags=-mcpu=${build.mcu} ${build.fpu} ${build.float-abi} -DUSE_FULL_LL_DRIVER -mthumb "@${build.opt.path}"
with compiler.extra_flags=-mcpu=${build.mcu} ${build.fpu} ${build.float-abi} -DUSE_FULL_LL_DRIVER -mthumb
and
replace recipe.hooks.prebuild.1.pattern="${runtime.tools.STM32Tools.path}/win/busybox.exe" sh "${extras.path}/prebuild.sh" "${build.path}" "${build.source.path}" "${runtime.platform.path}"
with #recipe.hooks.prebuild.1.pattern="${runtime.tools.STM32Tools.path}/win/busybox.exe" sh "${extras.path}/prebuild.sh" "${build.path}" "${build.source.path}" "${runtime.platform.path}"
after modification do the steps to propagate the change through the caches described here #1533
When the code analizer runs when the target folder (Release) does not exist the code analizer returns an error and fall back to defaults making the indexer mis lots of knowledge.
The root cause is the opt file that is copied to Release/sketch/opt during the pre build step. Therefore the file is not guaranteed to exists and the code analizer may fail.
As there is no easy way to start the code analizer this is pretty annoying.
This issue is found as part of #1491
The text was updated successfully, but these errors were encountered: