User forums > Nightly builds

The 17 June 2012 build (8059) is out.

<< < (5/11) > >>

Jenna:

--- Quote from: ollydbg on July 01, 2012, 11:53:55 am ---If so, which target can we put the "update.bat" in post-build step?

--- End quote ---

--- Quote from: jens on July 01, 2012, 10:29:37 am ---[...] call update[.bat] from the projects post-build step.

--- End quote ---

japplegame:
There is critical bug in C++ parser. If you insert "magic" code in any unit/header file (included in C++ project) then Code::Blocks will hangs up.
Magic code (copy exactly all quote):

--- Quote ---    typedef std::enable_if<N > 1, get_type_N<N-1, Tail...>> type;

--- End quote ---
Looks like parser gets stuck on "N > 1". If to surround it by parentheses, then all works fine.

MortenMacFly:

--- Quote from: jens on July 01, 2012, 10:29:37 am ---If I understand correctly, this patch was made to be able to run C::B from inside (or outside) without explicitely call update[.bat], to avoid crashes because of missing xrc-files.

--- End quote ---
True. We basically use two ways to update the resources in all plugins / projects: Either we call an update.bat or we zip the resources form inside the project's post-build steps (in that case these steps should always be executed - that is a common error).
So I see two solutions: Either we add a pre-build command which creates the required output folders OR we run update.bat as project's post-build step as Jens suggested. The latter has one drawback though: If you compile a specific target (like I do sometimes) this won't work probably. That's why I liked the idea of having the steps bound to the targets. So I tend to solution 1: Add the creation of that output folders either to the pre- or post-build steps.

Jenna:

--- Quote from: MortenMacFly on July 01, 2012, 02:58:24 pm ---[...]
The latter has one drawback though: If you compile a specific target (like I do sometimes) this won't work probably.
[...]

--- End quote ---
What does not work ?
A project postbuild step should be executed for single targets and for the whole project.
And normally it should be enough to execute it only if the target project was not uptodate.

stahta01:
Calling update.bat will mean that the output folder copy of Code::Blocks can not be used to build the devel copy of code::blocks.

Tim S.

Navigation

[0] Message Index

[#] Next page

[*] Previous page