User forums > Nightly builds

The 04 April 2012 build (7917) is out.

<< < (4/5) > >>

ollydbg:

--- Quote from: scarphin on April 08, 2012, 12:58:59 pm ---All the issues I previously mentioned here http://forums.codeblocks.org/index.php/topic,16024.0.html exist in this nightly. To summarize them:

1- CC doesn't work on function arguments NOT declared in the function declaration.
2- CC doesn't kick in for the standard libraries, like when a dot '.' is typed after 'cout' like 'cout.' CC won't kick in.
3- The red opening parenthesis issue.


--- End quote ---
I see those issues. but post them in the forum will make them lost. Can you file them in the bug reports in our berliOS site?

I have many of bugs CC signed, but many of them need more time to test.

Thank you.

scarphin:
I was once headed to file them as bugs but then forgot. ;) Will do asap.

oBFusCATed:

--- Quote from: fubo on April 06, 2012, 01:14:03 pm ---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

--- End quote ---


--- Quote from: Oleg_Sam on April 06, 2012, 03:18:06 pm ---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.  

--- End quote ---

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?

Oleg_Sam:
May be You right..
may be it was a bug...

But it was a very comfortable for embedded controllers project for generate asm listing files..
this is no necessary for x86 projects.

I no see  reason to removing this future.. ;)

oBFusCATed:
Oleg_Sam:
If you need some variable that is not currently implemented you should request a feature and you should explain the use case for it.
Then we can try to implement it.
Why do you need the $file_name variable?
Are you sure there isn't a variable available that you can use instead of it?

Navigation

[0] Message Index

[#] Next page

[*] Previous page