post build step : launch plugin

[killerbot]

Dear All,

What do you think about the following idea :

Would it be nice to be able to launch a plug-in as a post build step (or maybe pre build step) of a build of target/project.

A simple example. Suppose you want to have Cppcheck run on your project as a post build step.
Why : you want to ensure that stuff builds, and that CppCheck doesn't find any issues.

Another example :
When you have a unit test project, it might be very interesting to have it run at the end of it's build ($exe_output), but it might be evenly interesting to have it run by Valgrind.

How far away are we from achieving such behavior ?

Any further ideas ?

[MortenMacFly]

Would it be nice to be able to launch a plug-in as a post build step (or maybe pre build step) of a build of target/project.

How far away are we from achieving such behavior ?

IMHO it's already (at least partially) possible and in fact I am doing this.

What's needed is a batch file (in my case) which you provide with the information required via macros.
This way you can run an external (stand-alone) application with all the information needed. this worked fine for me for things like documentation update (doxygen), reporting and logging.

For the plugins we probably would need to declare events like:
- build succeeded for target/project/workspace
- pre-pre-processor, post-pre-processor for targets
- pre-post-processor, post-post-processor for targets

I'm open for it if a plugin makes more sense because it needs to access a lot of information (e.g. from other targets, compiler options and so on...).

[mandrav]

Correct me if I 'm wrong, but isn't it already possible to run script commands in pre/post build steps?
AFAIR, scripting exposes ToolPlugins' "Execute()" function already.

[MortenMacFly]

isn't it already possible to run script commands in pre/post build steps?

You tell - you did it. But yes: Scripting is surely possible. So that's another possibility.

[killerbot]

Hey Yiannis, good you give an example ?

[mandrav]

Hey Yiannis, good you give an example ?

In rev.6118, two new script commands were added: ExecuteToolPlugin() and ConfigureToolPlugin().
You can now put something like this in your post-build steps:

Code:

[[ ExecuteToolPlugin(_("CppCheck")) ]]

Enjoy

[killerbot]

gonna try them out tomorrow.
Hehe nice to have the boss back 

[oBFusCATed]

Another feature request for the "Post build step":

Is it possible to add option: "ReRun if Build/Post build failed last time"
This will be useful for unittest projects, where the resulting executable is run in the postbuild step.
At the moment I have to enable the option "Always run post build step", in order to get constant test failures

Example:

Code:

0. Load the project
1. Edit code/tests
2. Hit compile
3. The tests are run and fail
4. Hit compile again (no changes to code),
  Expected behavior: tests are run again and fail.
  If the "Always run post build step" is not enabled the build succeeds, which is wrong.

The current solution works, but is not optimal for large projects (many projects in a workspace, with lots of test projects),
because every time the user hits "Compile" all the test projects will be run, which costs time