How behaves Build and Run F9 when making cross-compiling

[comsytec]

How behaves Build and Run F9 when making cross-compiling ?
Normally it runs the EXE but what it will do when e.g. want to compile ELF for embedded system ?

[comsytec]

Log from run:

Checking for existence: C:\Work\IDEalCodeStudio\TestProjects\stm32f4-1\default\stm32f4-1.elf
Executing: "C:\Work\IDEalCodeStudio\TestProjects\stm32f4-1\default\stm32f4-1.elf"  (in C:\Work\IDEalCodeStudio\TestProjects\stm32f4-1\.)
Execution of '"C:\Work\IDEalCodeStudio\TestProjects\stm32f4-1\default\stm32f4-1.elf" ' in 'C:\Work\IDEalCodeStudio\TestProjects\stm32f4-1' failed.
Nothing to be done.

I think if not building for native system or in any other case the running request should be passed first to event handler and then try run as on native system
if not vetoed.

[comsytec]

I have an idea to solving this via dynamic event handlers but this does not seem to be system wide consistent way

[oBFusCATed]

I don't have any idea what are you talking about...

[comsytec]

Simply I'm using ARM toolchain. Building can be achieved via Build and RUN menu item also.  But what does the RUN in this case. Using CB on Windows so surely cannot run obtained binary as native EXE.

[MortenMacFly]

Simply I'm using ARM toolchain. Building can be achieved via Build and RUN menu item also.  But what does the RUN in this case. Using CB on Windows so surely cannot run obtained binary as native EXE.

Build and run assumes you have a runnable target. If thats not the case, use just "Build". You can still do whatever you like (including move it to another target, run commands etc.) in the post-build steps.