User forums > Embedded development

Looking for example of "Post-build steps"

<< < (7/8) > >>

Pavel_47:

--- Quote from: christobal on December 05, 2016, 05:06:47 pm ---Open the project file (.cbp) with a text editor and search for "main1". I guess there are some "remnants" of your tests in the post-build step configuration.

--- End quote ---

Yes, it was exactly the case. It was a strange <ExtraCommands> section that obfuscated the execution of the post-build command.
Once it's commented the post-build works. Is it a bug of Code::Blocks ?

--- Code: --- <Build>
<Target title="default">
<Option output="default/proj1.elf" prefix_auto="0" extension_auto="0" />
<Option object_output="default" />
<Option type="1" />
<Option compiler="arm-elf-gcc" />
<Compiler>
<Add option="-g" />
</Compiler>
<Linker>
<Add directory="C:/Program Files (x86)/GNU Tools ARM Embedded/5.4 2016q3/lib/gcc/arm-none-eabi/5.4.1" />
</Linker>
<!-- <ExtraCommands>
<Add after="arm-none-eabi-objdump -d main1.o &gt; main1.asm" />
</ExtraCommands> -->
</Target>
</Build>
--- End code ---

christobal:

--- Quote from: Pavel_47 on December 05, 2016, 07:31:29 pm ---
Yes, it was exactly the case. It was a strange <ExtraCommands> section that obfuscated the execution of the post-build command.
Once it's commented the post-build works. Is it a bug of Code::Blocks ?

--- End quote ---

The <ExtraCommands> IS the post-build command. You can set it project-global or target specific. If both have a build command set, you can choose whether the target commands shell be appended to the project commands, or if they shall overwrite the project commands.

Pavel_47:

--- Quote from: christobal on December 05, 2016, 07:55:26 pm ---The <ExtraCommands> IS the post-build command. You can set it project-global or target specific. If both have a build command set, you can choose whether the target commands shell be appended to the project commands, or if they shall overwrite the project commands.

--- End quote ---

... project-global or target specific. They both can be set via user interface ?
I see only project post-build.

christobal:
According to one of your screenshots, if you select "proj1" in the "Project build options", you can select the project-global build options. These apply usually to all build targets. In your case "default" is the build target. If you select it you can set the target build options. You can also choose how the target options are combined with the project options: They can be appended, prepended, they can replace the project options or they can be ignored (project options only).

Pavel_47:

--- Quote ---According to one of your screenshots, if you select "proj1" in the "Project build options", you can select the project-global build options. These apply usually to all build targets. In your case "default" is the build target. If you select it you can set the target build options. You can also choose how the target options are combined with the project options: They can be appended, prepended, they can replace the project options or they can be ignored (project options only).
--- End quote ---

Can you confirm (from the screenshot which follows), that project-global build options and target build options are specified in these locations (blue arrows show how these options can be called).
If this is the case, how to explain why main1.o file suffocated the "project-global" post-build processing if the post-build field in the "target" options is empty.

Navigation

[0] Message Index

[#] Next page

[*] Previous page