Hello embitz,
I found out some more things:
Thanks a lot for your effort!
I found out some more things:
- the picture of the context menu with the grayed out entries is also regularly like that during the build process
- in my project it just doesn't change back, so some entries are still not selectable
- surprisingly: if I start "build" again after the error (NOT "rebuild" all files), then of course nothing is compiled and linked anymore, but the context menu is then correct again! -> that would be an acceptable workaround for me -> I think that the source of the error is rather the codebocks substructure than your own Embitz code
- in my project there is a part (subdirectory), in which old firmware sources are located, which were originally written for a C166 Infineon MCU and were rewritten by me for ARM compatibility -> if I now comment out the jump into this firmware, then the error does not occur any more! Since there are no errors when compiling, it must indeed be the linker, because the prebuild and postbuild steps are proven not to generate the error -> this shows that by some property of the old C166 code the linker gets messed up.... I can see from the output that the build process is finished (and went through without errors and created a correct binary) but this is apparently not quite true, because the restricted context menu shows that the build process is not finished yet... only by running "build" again Embitz recognizes that now everything is done and releases the blocked context menu
- we have to stop investigating this at this point, because I can't release the code of the old firmware (I'm still adapting it to the ARM peripherals, so hopefully later the bug won't be there anymore).
Thanks a lot for your effort!