User forums > Using Code::Blocks

Make commands

<< < (3/4) > >>

sorinev:
I see what you mean about the backtick expression being cached. The output outside of codeblocks changes, but the expression is still the old value in codeblocks. You mentioned this was fixable in an earlier post; how would I go about that? I'm googling, but not finding much.

I don't want to have to restart C::B each time I add a new commit to git (so that the expression gets updated). Is that the only way?

oBFusCATed:
At the moment this is the only way.
The code must be changed to fix this problem.

sorinev:
Maybe I'll add a per-project mechanism somewhere to my local build of C::B (checkbox, or box with list of expressions not to cache, etc). When I was googling the backtick caching thing a little while ago, I did come across a post of yours from a few years back saying it was best to cache it for situations like generating the wxconfig flags/libs, etc.

BlueHazzard:
You can also try to use scripting: http://wiki.codeblocks.org/index.php?title=Scripting_commands
the "ExecuteAndGetOutput" command should help.
For more reading:
http://wiki.codeblocks.org/index.php/Variable_expansion#Script_expansion

greetings

oBFusCATed:
In fact, I'm planning to fix this problem.
I have an idea, I just need to test it a bit more, because this part of C::B is a bit fragile.

Navigation

[0] Message Index

[#] Next page

[*] Previous page

Go to full version