Author Topic: The 15 January 2006 build is out.  (Read 25714 times)

Offline killerbot

  • Administrator
  • Lives here!
  • *****
  • Posts: 5234
The 15 January 2006 build is out.
« on: January 15, 2006, 11:07:42 pm »
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 15 January 2006 build is out.
  - Windows : http://download.berlios.de/codeblocks/CB_15jan2006_rev1763_win32.7z
  - Linux : not supported yet


Resolved Fixed:

  • Moved Manager::Yield() out of Message Manager, Added some calls to it in the compiler plugin, Replaced Manager::Yield() with Manager::ProcessPendingEvents() in some functions
  • Fixed a linux build error and Added some #includes to make the source compile with gcc 3.3.6
  • Fixed "open #include" function (patch #1406508 by killerbot)
  • Removed $Id and $Date SVN keywords from a couple of manager headers which caused a full rebuild after each commit
  • Debugger startup user commands are now passed as a block of commands instead of each one separately (fixes potential hang when defining gdb functions)
  • Fixed a priority issue for CXXFLAGS in autotools build system (patch #1406533)
  • Removed all "#pragma interface" and "#pragma implementation" from code. They are not useful nowadays and actually have caused linker errors for linux builds in the past
  • Fixed file associations settings to be set per-user instead of globally (patch #1393650)
  • Fixed math rounding errors in codestats plugin (patch #1383774)
  • Fixed a few annoying bugs in "find" dialog, mainly the non-focused text box in linux (patch #1382768)

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)


Offline jc

  • Multiple posting newcomer
  • *
  • Posts: 14
Re: The 15 January 2006 build is out.
« Reply #1 on: January 16, 2006, 09:55:34 am »
I can confirm kisolre's problem (.sln files crashing Code::Blocks when they're imported; seems right near the end of finishing the import), this happens for me with the 13.01.2006, 14.01.2006 and 15.01.2006 builds. :(

Offline jc

  • Multiple posting newcomer
  • *
  • Posts: 14
Re: The 15 January 2006 build is out.
« Reply #2 on: January 16, 2006, 04:23:49 pm »
Code: [Select]
-------------------

Error occured on Monday, January 16, 2006 at 07:21:11.

C:\Programs\codeblocks\codeblocks.exe caused an Access Violation at location 6197167b in module C:\Programs\codeblocks\codeblocks.dll Reading from location 00000130.

Registers:
eax=00000130 ebx=00c05cf8 ecx=00000001 edx=00000001 esi=004ada30 edi=0022f910
eip=6197167b esp=0022f288 ebp=0022f288 iopl=0         nv up ei pl nz na po nc
cs=001b  ss=0023  ds=0023  es=0023  fs=003b  gs=0000             efl=00010206

Call stack:
6197167B  C:\Programs\codeblocks\codeblocks.dll:6197167B  _ZN9cbProject14GetProjectNodeEv
6188C82F  C:\Programs\codeblocks\codeblocks.dll:6188C82F  _ZN14ProjectManager13LoadWorkspaceERK8wxString
00423C4E  C:\Programs\codeblocks\codeblocks.exe:00423C4E
00429802  C:\Programs\codeblocks\codeblocks.exe:00429802
00429B5A  C:\Programs\codeblocks\codeblocks.exe:00429B5A
100AA0E8  C:\Programs\codeblocks\wxmsw26u_gcc_cb.dll:100AA0E8  _ZN12wxEvtHandler21ProcessEventIfMatchesERK21wxEventTableEntryBasePS_R7wxEvent
100AA4AC  C:\Programs\codeblocks\wxmsw26u_gcc_cb.dll:100AA4AC  _ZN16wxEventHashTable11HandleEventER7wxEventP12wxEvtHandler
100AB489  C:\Programs\codeblocks\wxmsw26u_gcc_cb.dll:100AB489  _ZN12wxEvtHandler12ProcessEventER7wxEvent
100AB429  C:\Programs\codeblocks\wxmsw26u_gcc_cb.dll:100AB429  _ZN12wxEvtHandler12ProcessEventER7wxEvent
100AB429  C:\Programs\codeblocks\wxmsw26u_gcc_cb.dll:100AB429  _ZN12wxEvtHandler12ProcessEventER7wxEvent
100AB429  C:\Programs\codeblocks\wxmsw26u_gcc_cb.dll:100AB429  _ZN12wxEvtHandler12ProcessEventER7wxEvent
100AB429  C:\Programs\codeblocks\wxmsw26u_gcc_cb.dll:100AB429  _ZN12wxEvtHandler12ProcessEventER7wxEvent
100AB429  C:\Programs\codeblocks\wxmsw26u_gcc_cb.dll:100AB429  _ZN12wxEvtHandler12ProcessEventER7wxEvent
100AB429  C:\Programs\codeblocks\wxmsw26u_gcc_cb.dll:100AB429  _ZN12wxEvtHandler12ProcessEventER7wxEvent
100AB429  C:\Programs\codeblocks\wxmsw26u_gcc_cb.dll:100AB429  _ZN12wxEvtHandler12ProcessEventER7wxEvent
100AB429  C:\Programs\codeblocks\wxmsw26u_gcc_cb.dll:100AB429  _ZN12wxEvtHandler12ProcessEventER7wxEvent
100AB429  C:\Programs\codeblocks\wxmsw26u_gcc_cb.dll:100AB429  _ZN12wxEvtHandler12ProcessEventER7wxEvent
100AB429  C:\Programs\codeblocks\wxmsw26u_gcc_cb.dll:100AB429  _ZN12wxEvtHandler12ProcessEventER7wxEvent
100AB429  C:\Programs\codeblocks\wxmsw26u_gcc_cb.dll:100AB429  _ZN12wxEvtHandler12ProcessEventER7wxEvent
100AB429  C:\Programs\codeblocks\wxmsw26u_gcc_cb.dll:100AB429  _ZN12wxEvtHandler12ProcessEventER7wxEvent
100AB429  C:\Programs\codeblocks\wxmsw26u_gcc_cb.dll:100AB429  _ZN12wxEvtHandler12ProcessEventER7wxEvent
100AB429  C:\Programs\codeblocks\wxmsw26u_gcc_cb.dll:100AB429  _ZN12wxEvtHandler12ProcessEventER7wxEvent
100AB429  C:\Programs\codeblocks\wxmsw26u_gcc_cb.dll:100AB429  _ZN12wxEvtHandler12ProcessEventER7wxEvent
100AB429  C:\Programs\codeblocks\wxmsw26u_gcc_cb.dll:100AB429  _ZN12wxEvtHandler12ProcessEventER7wxEvent
100AB429  C:\Programs\codeblocks\wxmsw26u_gcc_cb.dll:100AB429  _ZN12wxEvtHandler12ProcessEventER7wxEvent
100AB429  C:\Programs\codeblocks\wxmsw26u_gcc_cb.dll:100AB429  _ZN12wxEvtHandler12ProcessEventER7wxEvent
100AB429  C:\Programs\codeblocks\wxmsw26u_gcc_cb.dll:100AB429  _ZN12wxEvtHandler12ProcessEventER7wxEvent
100AB429  C:\Programs\codeblocks\wxmsw26u_gcc_cb.dll:100AB429  _ZN12wxEvtHandler12ProcessEventER7wxEvent
100AB429  C:\Programs\codeblocks\wxmsw26u_gcc_cb.dll:100AB429  _ZN12wxEvtHandler12ProcessEventER7wxEvent
100AB429  C:\Programs\codeblocks\wxmsw26u_gcc_cb.dll:100AB429  _ZN12wxEvtHandler12ProcessEventER7wxEvent
100AB429  C:\Programs\codeblocks\wxmsw26u_gcc_cb.dll:100AB429  _ZN12wxEvtHandler12ProcessEventER7wxEvent
101B06C3  C:\Programs\codeblocks\wxmsw26u_gcc_cb.dll:101B06C3  _ZN11wxFrameBase14ProcessCommandEi
10138AAF  C:\Programs\codeblocks\wxmsw26u_gcc_cb.dll:10138AAF  _ZN7wxFrame13HandleCommandEttPv
101391D6  C:\Programs\codeblocks\wxmsw26u_gcc_cb.dll:101391D6  _ZN7wxFrame13MSWWindowProcEjjl
1010C750  C:\Programs\codeblocks\wxmsw26u_gcc_cb.dll:1010C750  [email protected]
77D43A50  C:\WINDOWS\system32\USER32.dll:77D43A50
77D43B1F  C:\WINDOWS\system32\USER32.dll:77D43B1F
77D43D79  C:\WINDOWS\system32\USER32.dll:77D43D79  GetMessageW
77D43DDF  C:\WINDOWS\system32\USER32.dll:77D43DDF  DispatchMessageW
100EC7F4  C:\Programs\codeblocks\wxmsw26u_gcc_cb.dll:100EC7F4  _ZN11wxEventLoop8DispatchEv
100EC590  C:\Programs\codeblocks\wxmsw26u_gcc_cb.dll:100EC590  _ZN11wxEventLoop3RunEv
1018492E  C:\Programs\codeblocks\wxmsw26u_gcc_cb.dll:1018492E  _ZN9wxAppBase8MainLoopEv
00404CDA  C:\Programs\codeblocks\codeblocks.exe:00404CDA
10043817  C:\Programs\codeblocks\wxmsw26u_gcc_cb.dll:10043817  _Z14wxUninitializev
100B33BA  C:\Programs\codeblocks\wxmsw26u_gcc_cb.dll:100B33BA  _Z7wxEntryP11HINSTANCE__S0_Pci
004014DA  C:\Programs\codeblocks\codeblocks.exe:004014DA
0045A2EA  C:\Programs\codeblocks\codeblocks.exe:0045A2EA
00401237  C:\Programs\codeblocks\codeblocks.exe:00401237
00401288  C:\Programs\codeblocks\codeblocks.exe:00401288
77E814C7  C:\WINDOWS\system32\kernel32.dll:77E814C7  GetCurrentDirectoryW



Offline killerbot

  • Administrator
  • Lives here!
  • *****
  • Posts: 5234
Re: The 15 January 2006 build is out.
« Reply #3 on: January 16, 2006, 04:25:44 pm »
Yiannis has fixed this. Wait till tonight's nightly build.


Or you can always build it yourself ;-)
Haha, imagine you have to rebuild Visual Studio  :lol:

Offline jc

  • Multiple posting newcomer
  • *
  • Posts: 14
Re: The 15 January 2006 build is out.
« Reply #4 on: January 16, 2006, 04:31:56 pm »
Mawh, thanks killerbot, I really didn't see that other thread saying it was fixed, sorry for bugging you guys about it (I'll check that other forum from now on before posting a bug)! :)

Looking forward to tonights revision (if I try to set up a compile environment I bet it would take me all day, until tonight, to set it up!). :)

Offline Michael

  • Lives here!
  • ****
  • Posts: 1608
Re: The 15 January 2006 build is out.
« Reply #5 on: January 16, 2006, 05:14:40 pm »
(if I try to set up a compile environment I bet it would take me all day, until tonight, to set it up!). :)

Not really. It is VERY EASY to compile C::B yourself :D. You just have to:

  • Download and install TortoiseSVN
  • Download C::B source with TortoiseSVN
  • With the latest nightly build open the CodeBlocks-NewBuild.cbp
  • Define the global variable wx for wxWidgets
  • Build
  • Run update.bat

Finish...and it has taken more time to write it than you will need for doing it :D.

You can compile wxWidgets by yourself (in UNICODE) or download it from: http://paginas.terra.com.br/informatica/mauricio/codeblocks/

Do not forget zip.exe and to have installed MinGW (you can also use the one that come with RC2).

Michael

Offline boaz

  • Multiple posting newcomer
  • *
  • Posts: 18
Re: The 15 January 2006 build is out.
« Reply #6 on: January 16, 2006, 07:08:45 pm »
thanks!

I had a boot strap problem.

- Downloaded binarry release of C::B
- compiled wxWidgets
- tortoiseSVN the latest trunk. Opened up CodeBlocks-wx2.6.0.cbp with Instalation C::B
- Well the project is to old and does not mach the new code. Files have moved, added, and so on.
- open up CodeBlocks-NewBuild.cbp but the binnary release does not have all this $(#xxx) stuff so it does not compile.

I manually edited all the $(#WX...) but it still does not compile some undefins I'll have a look tommorow.

Do you think the old CodeBlocks-wx2.6.0.cbp should be updated to the new files? I did do somework on it it should be almost linking now

Free Life
Boaz

Offline killerbot

  • Administrator
  • Lives here!
  • *****
  • Posts: 5234
Re: The 15 January 2006 build is out.
« Reply #7 on: January 16, 2006, 07:42:47 pm »
CodeBlocks-NewBuild.cbp should be all you need, you need to fill in the global variable for wx (and you must have wx build yourself (very easy). I will create a description, or better, a cookbook on how the nightlies are created.
Lieven

Offline Michael

  • Lives here!
  • ****
  • Posts: 1608
Re: The 15 January 2006 build is out.
« Reply #8 on: January 16, 2006, 07:48:58 pm »
I will create a description, or better, a cookbook on how the nightlies are created.

That would be a very good idea :D. Very useful, especially for beginners.

Michael

PS.: You are really fast in replying posts. I was replying to boaz too, but when selecting preview.... :D

Offline boaz

  • Multiple posting newcomer
  • *
  • Posts: 18
Re: The 15 January 2006 build is out.
« Reply #9 on: January 18, 2006, 10:30:06 am »
Quote
CodeBlocks-NewBuild.cbp should be all you need, you need to fill in the global variable for wx

It's what I did. I got it to compile. But I got stuck with resources. Where are the resource files when you svn the code tree. Where is the share Directory and what should be the --prefix when running in-tree. OK you don't need to answer that. I'll go read the manual now (RTFM boaz).

But one last thing. Is there a command line switch you can stick at the "Programs arguments" setting, that tells the debugged C::B to load a second Instance. It is annoying to have to "allow multiple instances" than exit, than come back in, so you can debug your compilation. And please put it in the CodeBlocks.cbp by default.

Thanks guys you Rock this stuff is grate!!!
Free Life
Boaz

Offline Michael

  • Lives here!
  • ****
  • Posts: 1608
Re: The 15 January 2006 build is out.
« Reply #10 on: January 18, 2006, 12:11:41 pm »
Quote
CodeBlocks-NewBuild.cbp should be all you need, you need to fill in the global variable for wx

It's what I did. I got it to compile. But I got stuck with resources. Where are the resource files when you svn the code tree. Where is the share Directory and what should be the --prefix when running in-tree. OK you don't need to answer that. I'll go read the manual now (RTFM boaz).

I am not sure to understand. After compiling C::B, did you run update.bat?

Michael

Offline boaz

  • Multiple posting newcomer
  • *
  • Posts: 18
Re: The 15 January 2006 build is out.
« Reply #11 on: January 18, 2006, 03:45:26 pm »
Quote
I am not sure to understand. After compiling C::B, did you run update.bat?

You Just saved me the reading of the Manual.
No I did not. is that what I have to do? :wink:

Why don't we put that in the "post build" of the application. So there is no Manual to read?

Free Life
Boaz

Offline Urxae

  • Regular
  • ***
  • Posts: 376
Re: The 15 January 2006 build is out.
« Reply #12 on: January 18, 2006, 04:11:35 pm »
Why don't we put that in the "post build" of the application. So there is no Manual to read?

Because it doesn't work while C::B is running from the output/ directory: update.bat tries to overwrite it. So if you're running C::B from there (which you might want to do after you go through the trouble to compile it ;)) you have to close it before running update.bat

Offline 280Z28

  • Regular
  • ***
  • Posts: 397
  • *insert unicode here*
Re: The 15 January 2006 build is out.
« Reply #13 on: January 18, 2006, 04:36:42 pm »
Why don't we put that in the "post build" of the application. So there is no Manual to read?

Because it doesn't work while C::B is running from the output/ directory: update.bat tries to overwrite it. So if you're running C::B from there (which you might want to do after you go through the trouble to compile it ;)) you have to close it before running update.bat

If you copy the files in the devel directory somewhere else and run that copy instead, you get much more information if it crashes on you afterwards. Then you could run update.bat while C::B is running too.
78 280Z, "a few bolt-ons" - [email protected]
99 Trans Am, "Daily Driver" - 525rwhp/475rwtq
 Check out The Sam Zone :cool:

Offline Michael

  • Lives here!
  • ****
  • Posts: 1608
Re: The 15 January 2006 build is out.
« Reply #14 on: January 18, 2006, 05:08:09 pm »
Quote
I am not sure to understand. After compiling C::B, did you run update.bat?

You Just saved me the reading of the Manual.
No I did not. is that what I have to do? :wink:

And also do not forget to have zip.exe (update.bat needs it).

Michael

Offline boaz

  • Multiple posting newcomer
  • *
  • Posts: 18
Re: The 15 January 2006 build is out.
« Reply #15 on: January 18, 2006, 06:14:34 pm »
Quote
If you copy the files in the devel directory somewhere else and run that copy instead, you get much more information if it crashes on you afterwards. Then you could run update.bat while C::B is running too.

It's what I thought.
- You have your working C::B which is in Program\ Files or /usr/local or what ever. (Hopefully the night builds see above).
- You grab the SVN trunk of C::B open CodeBlocks.cbp up. and compile. It will compile to your source directory since it cannot overwrite the Instance which is currently running. Lets call this one C::B2
- Update.bat prepare every thing in the source tree. (For C::B2)
- I debug my new stuff on C::B2 (with the command line switch that lets it run a second instance), I change resources, code the lot. Compile and debug and so on... (Debugger is in Original C::B)
- I like my new version better. So I make a release version which also builds the installer.
- Exit C::B And Install it to program\ files. Now I load the new One. (I'm My own beta tester)

Is there any other way? So I guess Update.bat could be inside the .cbp, or at least we can make an intree-update.bat.

Free Life
Boaz