CB project: integrated 'update'

[LETARTARE]

Hello,
to compile a last version of 'Code :: Blocks', I use as IDE a previous version.
After compiling 'Code :: Blocks', it is tedious to open a console to launch 'update (.bat)'.

I tested the following solution with VISTA and OpenSuse :
1- create a real target 'Update' , 'Command only' type,  'Pos-built steps' with a call to 'update.bat' or './update'
2- in the virtual target 'All': add in last this target 'Update'

This makes it possible to integrate the update into the construction process.

I may have forgotten some things ?

[ollydbg]

This is a good idea, great!
My question is: When will the target named "Update" to be "built"? I mean You just manually click the "build" button to "build" the "Update" target?

[LETARTARE]

Here is the kind of interesting question.
I just did a test on 'svn11176' that I cleaned up, then I compiled the 'Update' target under VISTA.
The result is in image ...

[BlueHazzard]

You could also add the update target it to the "All" target at the end. So it will always be running after rebuilding codeblocks.

One problem i see here is, that if you build the codeblocks workspace with all plugins you have to run this update script at the end of the build process of all plugins.

[LETARTARE]

Thank you for the information :

You say :

You could also add the update target it to the "All" target at the end.

Of course, as indicated -> 'last'

2- in the virtual target 'All': add in  last  this target 'Update'

You also indicate :

you have to run this update script at the end of the build process of all plugins

This is a good question, but I have not tested it yet.

Is it a problem ?

[LETARTARE]

@BlueHazzard say :

you have to run this update script at the end of the build process of all plugins

I note that many plugins call 'update' including the latest 'Tools Plus Plugin'.
It is then possible in the project to remove the call of 'update' in the virtual target 'All'.

If we add another plugin in the end it should be expected while he calls 'update' !!

[stahta01]

@BlueHazzard say :

you have to run this update script at the end of the build process of all plugins

I note that many plugins call 'update' including the latest 'Tools Plus Plugin'.
It is then possible in the project to remove the call of 'update' in the virtual target 'All'.

If we add another plugin in the end it should be expected while he calls 'update' !!

There is more than a single update scripts/batch files

Some plugins have there own, instead of, or in addition to the main update script.

NOTE: Calling the  update script in the virtual target 'All' would not work for my normal build process.
Edit: This is on Windows; because in use file replacement is not supported by the OS.
I use output codeblocks to build devel codeblocks; exit codeblocks, then run main update script

Tim S.

[LETARTARE]

@stahta01
thank you for the clarification.

This is on Windows; because in use file replacement is not supported by the OS.

If you are using a previous version of 'Code::Block' for compilation, you can use the main 'update.bat' call in 'All' virtual target.
Ex :I used 'cb-11286' to build 'cb-11304' without difficulty ( for 'CodeBlocks.cbp'  and 'CodeBlocks-unix.cbp' )

I use output codeblocks to build devel codeblocks; exit codeblocks, then run main update script

I thought we'd first build devel codeblocks, then leaving codeblocks we launched the main update to build the output codeblocks ?

So, it sounds more complicated than I thought. But I find it sad to have to leave 'Code::Blocks' to finish building.