User forums > Using Code::Blocks

Custom command build and waiting file generation command

<< < (2/2)

sodev:
This is from my memory, i might got some details wrong and maybe the system got changed since then. Some years ago i fixed the problem that files with different processing weigths got processed in parallel which only happened when doing parallel builds. I think i injected that WAIT command after each priority change but i need to search the history first to be sure.

However i am sure it works in the custom compile command as well, because before i switched to using the feature to support non-c-files i used it there to compile wxrc-files into c-files which i then compile normally.

sodev:
Apparently "some years" is almost 8 now, patch #3342 fixed the compile priorities, that must have been before the Sourceforge days.

I cannot dig through the whole code to figure out the details, but the interesting parts are both in the compiler plugin. directcommands.cpp does the generation of the compiler command lines and splits them up at newlines into individual commands for the command processor, this is why multiple commands as custom command do work. In that file the symbol COMPILER_WAIT is defined that does empty the queue. The actually processing of the commands happens inside compilergcc.cpp, search for COMPILER_WAIT and move up the call tree to figure out the processing logic.

Navigation

[0] Message Index

[*] Previous page