The 16 January 2006 build is out.

[killerbot]

Get quick announcements through the RSS feed http://www.codeblocks.org/nightly/CodeBlock_RSS.xml
A link to the unicode windows wxWidget dll for Code::Blocks : http://download.berlios.de/codeblocks/wxmsw26u_gcc_cb.7z
For those who might need this one (when no MingW installed on your system) : the mingw10m.dll : http://download.berlios.de/codeblocks/mingwm10.7z

The 16 January 2006 build is out.
  - Windows : http://download.berlios.de/codeblocks/CB_16jan2006_rev1775_win32.7z
  - Linux : not supported yet


Resolved Fixed:

• Fixed bug with resource include dirs policy setting not remembered (bug #1405856)
• Debugger breakpoints are now kept in-sync with the editor at all times (except when the debuggee is running in which case the debugger is not under our control)
• Added support for backtick'd expressions under windows (e.g. `wx-config --libs`)
• Fixed crash when importing MSVC workspaces
• Implemented setting project dependencies when importing MSVC workspaces/solutions
• Fixed infinite loop when trying to replace a macro which doesn't exist
• Save file before compiling. Applies to single files not belonging to a project (bug #1403578)
• Fixed an error in debugger wxString parsing. Sometimes it would wrongly parse commas (,)
• Moved files not belonging to build out of trunk
• Updated script bindings

Regressions/Confirmed/Annoying/Common bugs:

• DDE bug : clicking in windows explorer on a CB registered file throws an error message box
• toolbar-images-not-changing-state (is a wx problem)

[killerbot]

As I am tomorrow morning (damn early) leaving for France for my job, and only return on thursday, I won't be able to provide nighlies tomorrow and wednesday. But look on the bright side, the thursday nightly will probably be jam packed with fixes, new features (hey maybe someone else might have implemented this one : http://forums.codeblocks.org/index.php?topic=2021.0   ;-)  )
And maybe the devs might have removed all warnings by then  :lol:
And who knows, maybe the code completion will be super fast by then ...

A jeudi,
Lieven

[jc]

killerbot, my hero! Thank you so much. Have a very safe trip. 

[Michael]

And maybe the devs might have removed all warnings by then  :lol:

wxAUI warnings, may be ?

A jeudi,
Lieven

Bon voyage.

Salutations,
Michael

[spoofer]

Added support for backtick'd expressions under windows (e.g. `wx-config --libs`)

How does this works exactly? Is some external program required (I have MSYS) or it works out of box?

[mandrav]

Added support for backtick'd expressions under windows (e.g. `wx-config --libs`)

How does this works exactly? Is some external program required (I have MSYS) or it works out of box?

Everything works out of the box
The only note is that for non-NT windows (95,98,etc) you have to use the extension of the filename too, e.g. `wx-config.bat --libs`.
And, ofcourse, you have to create 'wx-config.bat' (or whatever else) yourself

[spoofer]

Great! How about making C::B call sh.exe (if path is provided) to execute script. It's simple as:

Code

sh --login -i -c <script>

EDIT: Addition paths maybe?

[mandrav]

Great! How about making C::B call sh.exe (if path is provided) to execute script. It's simple as:

Code

sh --login -i -c <script>

EDIT: Addition paths maybe?

sh --login?

Remember, we 're talking about windows platforms only here. As the relevant comment in the sources say: "Real OSes support this natively"

[spoofer]

I meant that if someone has Windows and MSYS that he can use scripts. You can even build wxWidgets by passing --with-msw to configure. So on Windows C::B could search know paths for sh.exe and execute script if found.

P.S. I took that line from msys.bat (used to start-up MSYS) --login is needed.

[mandrav]

I have some strange bug, from 3-4 days.

1. Don't post bug reports here. This is an announcement thread. Respect the fact that it's not locked for posting.
2. A forum search would give you the solution.
3. "View->Layouts->Delete current".