The GNU ARM Eclipse plugins from Liviu already offer several built-in actions which can be performed at the end of a build: creating flash image, create listing file and printing the code and data size:
GNU ARM Eclipse Extra Post Build Steps
But what if I need different things, or even more things?
Post-Build Steps
For this there is the ‘Post-build steps’ settings I can use: that command is executed at the end of the build:
💡 Be aware that by default pre-build scripts might not wait until finished before starting the build. Disabling parallel build avoids the problem — see https://community.nxp.com/message/1058714
Print Size Post-Build Step
❗ The post build step is only executed if sources files have been compiled and linked. If you want to enforce that there is always a ‘true’ post build, then you need to delete some files in the Pre-build step to enforce a compilation and a link phase.
Multiple Post-Build Steps
But what I need more than one action in the post-build step? I could call a batch or script file, but this is probably an overkill in too many cases, and adds a dependency to that script file. A better approach is to directly execute multiple commands as post-build step.
Unfortunately, the documentation found about the post-build step with a web-search is misleading (e.g. in the Eclipse Luna documentation):
“Command: Specifies one or more commands to execute immediately after the execution of the build. Use semicolons to separate multiple commands.”
Unfortunately, semicolons is plain wrong (at least did not work for me) :-(. The solution is to use ‘&‘ (ampersand) to separate multiple commands on Windows:
💡 On Linux, use the ‘;’ to separate commands as noted in the documentation/help, and use ‘&’ on Windows. Unfortunately, this makes project not cross-platform.
Multiple Post-Build Commands
And this works for me, at least under Windows 7 :-).
Links related to that topic:
- GNU Additional Tools: Create Flash Image, Print Size and Extended Listing Options
- S-Record Manipulation with GNU objcopy and Burner Utility
- S-Record Generation with gcc for ARM/Kinetis
- Converting S19 Files into Binary Files with GNU objcopy
Happy Post-Stepping 🙂
The “&” (ampersand) symbol is the windows command line equivalent of the linux “;” (semicolon) command line to continue to the next command in the list.
So in Windows we have:
cmd1 & cmd2 & … cmdN
In most Linux (BASH / DASH) the equivalent is:
cmd1; cmd2; … cmdN
The “pre-build” and “post-build” steps are just echo’d to a CLI.
You’re absolutely correct Eric, the documentation is too centric on the *inx world for those build options.
LikeLike
Hi Jonathan,
I had no time to try it on Linux, but I already expected something like this. Thanks for the confirmation, I will add a note to the article about that it indeed works with “;” on Linux. Thanks!
LikeLike
Pingback: CRC Checksum Generation with ‘SRecord’ Tools for GNU and Eclipse | MCU on Eclipse
Pingback: GNU Static Stack Usage Analysis | MCU on Eclipse
Pingback: Aligning S19 Records to 64-bit Boundaries | MCU on Eclipse
Pingback: Merging S19 Files | MCU on Eclipse
I use winxp. The & doesn’t help when I want to run multiple post-build commands. Only the last command after & runs, the previous commands are reported as wrong argument. Any suggestion on how to fix this problem?
LikeLike
Hi Carol,
I don’t have Windows XP any more, so I cannot try this out. I suspect that maybe as on Linux a different separator is needed between the commands?
LikeLike
Pingback: Automatically Refresh Eclipse Projects before Build | MCU on Eclipse
Just to add to the confusion, in *nux systems you can use ‘&&’ to join multiple commands, as in:
cmd1 && cmd2
This has the (generally) beneficial effect of only running cmd2 if cmd1 completes without an error.
LikeLike
By changing the selected builder type in the Project Properties: C/C++ Build/Builder Settings
to Internal Builder “;” is working for me (I use Win7)
to External Builder “;” does not work for me
The reason for this seems to be that the line containing the postbuild steps is copied to the Makefile (using the external Builder) but for any reason “make” does not recognize “;” as command separator.
So I see two workarounds for this:
Change “;” to “&” if the external builder is used or use “;” and the internal builder
LikeLike
By the way, there’s something to watchout for with pre-build scripts: using default Eclipse settings, the build will happily proceed before the pre-build steps complete. Disabling parallel build avoids the problem — see https://community.nxp.com/message/1058714 for full details.
LikeLike
Hi Robert,
good point! I’ll have that added to the text.
Thanks!
Erich
LikeLike