I found a regression towards 7789. If I use some C::B variables in "Other linker options" pane of "Linker settings" tab in "Compiler and debugger..."->"Global compiler settings" they are not processed. For example, I add option "--list $exe_dir\$exe_name.txt" in that pane. It works with 7789, it does not with 7917.
fubo
In last nightly build CB (7917), the macros $file_name (and other $file.. and etc.) is not replaced in compiler command line...
When are placed in Compiler Settings-> Other Options.
To reproduced:
1. Open Compiler Settings-> Other Options.
2. Type any options contains macros $file_name,
for example
-Wa,-adhlns=$file_name.lst
3. Set Compiler logging full command line
4. Build
and see that macro $file_name is empty string (not replaced by current file name)
In previous nightly build CB all works fine.
Thanks.
As far as I can see these three are not meant to be used by users in the user's UI.
The purpose of these three is to be used, when some one is defining compiler/linker commands in the advanced settings of the compiler.
And I guess this was a bug that they worked before.
Where have you learnt about them?
Here is some documentation about user's variables ->
http://wiki.codeblocks.org/index.php?title=Variable_expansion@dev: Am I correct in my discoveries?