Author Topic: The 16 June 2006 build is out.  (Read 23074 times)

Offline killerbot

  • Administrator
  • Lives here!
  • *****
  • Posts: 5490
The 16 June 2006 build is out.
« on: June 16, 2006, 08:18:08 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_wx2.6.3p2.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

For support of ansi builds, a link to the ansi windows wxWidget dll (2.6.2) for Code::Blocks : http://download.berlios.de/codeblocks/wxmsw26_gcc_cb.7z

The 16 June 2006 build is out.
  - Windows : http://download.berlios.de/codeblocks/CB_20060616_rev2577_win32.7z
  - Linux :
         http://download.berlios.de/codeblocks/CB_20060616_rev2577_Ubuntu6.06.deb
         http://download.berlios.de/codeblocks/CB_20060616_rev2577_fc4+5.rpm


Resolved Fixed:

  • Added "BYOgames" entertainment plugin (windows only - linux files later today)
  • Added "back-to-work" timer class in byogames (people need to be reminded to get back to work!)
  • Added autotools and linux C::B build files for BYOgames plugin
  • Updated the plugin description so it names the right version of AStyle being used now

Regressions/Confirmed/Annoying/Common bugs:

  • toolbar-images-not-changing-state (is a wx problem/Win XP problem)
  • there are several issues with Code Completion (is being redesigned : work in progress)
  • menu items with icon not correctly aligned (since wx263)

« Last Edit: June 16, 2006, 10:12:22 pm by killerbot »

dllmain

  • Guest
Re: The 16 June 2006 build is out.
« Reply #1 on: June 16, 2006, 08:20:22 pm »
The windows download gives "File doesn't exist" here!?

Offline killerbot

  • Administrator
  • Lives here!
  • *****
  • Posts: 5490
Re: The 16 June 2006 build is out.
« Reply #2 on: June 16, 2006, 08:24:17 pm »
give me a little bit of time to upload  :P

dllmain

  • Guest
Re: The 16 June 2006 build is out.
« Reply #3 on: June 16, 2006, 08:26:29 pm »
Now it works...

Offline orefa

  • Multiple posting newcomer
  • *
  • Posts: 102
Re: The 16 June 2006 build is out.
« Reply #4 on: June 16, 2006, 09:01:04 pm »
Yesterday's menu problem remains (under Windows 2000). When selecting a shortcut letter, menu selection goes to any other option that does NOT have the shortcut instead of the one that has it. For example pressing 'C' in the file menu does not select "Close" as it should but rotates among the other 'C' menu options.

Offline lubos

  • Almost regular
  • **
  • Posts: 131
Re: The 16 June 2006 build is out.
« Reply #5 on: June 16, 2006, 09:10:02 pm »
when i run this c::b nightly i have message:access violation from adress blablabla
i click button(retry or cancel...) and Code blocks run normally  :? :? :? error in my computer?

Offline kkez

  • Almost regular
  • **
  • Posts: 153
    • WinapiZone
Re: The 16 June 2006 build is out.
« Reply #6 on: June 16, 2006, 09:27:05 pm »
Quote
when i run this c::b nightly i have message:access violation from adress blablabla
i click button(retry or cancel...) and Code blocks run normally :? :? :? error in my computer?
No, i've got the same behavior when trying to create a directory from the "save file" dialog. It's like GDB that always detect a sigsev when i'm using hooks, but when i try to continue everything works ok...

royalbox

  • Guest
Re: The 16 June 2006 build is out.
« Reply #7 on: June 16, 2006, 09:36:07 pm »
The last version of code::blocks that works on my xp-sp2 system are pre 2006/06/14. After this I get access violations.

I renamed my existing %ProgramFiles%\Code blocks and %UserProfile%\Application Data\codeblocks directories, and extracted tonight's build to %ProgramFiles%\Code blocks.

I added the latest  mingwm10.dll and wxmsw26u_gcc_cb.dll.

I open code::blocks, choose the compiler, and set it as default.

I click on the 'open' icon and get an access violation.

This happens on 2006/06/14 to 2006/06/16. I don't know what else to check. I know I'm the only one getting this. If anyone has any suggestions of anything to try please let me know.

Many thanks.

EDIT: Seems I'm not alone after all.
« Last Edit: June 16, 2006, 09:45:54 pm by royalbox »

Offline oz

  • Multiple posting newcomer
  • *
  • Posts: 47
Re: The 16 June 2006 build is out.
« Reply #8 on: June 17, 2006, 06:11:46 am »
Quote
The last version of code::blocks that works on my xp-sp2 system are pre 2006/06/14. After this I get access violations.

I renamed my existing %ProgramFiles%\Code blocks and %UserProfile%\Application Data\codeblocks directories, and extracted tonight's build to %ProgramFiles%\Code blocks.

I added the latest  mingwm10.dll and wxmsw26u_gcc_cb.dll.

I open code::blocks, choose the compiler, and set it as default.

I click on the 'open' icon and get an access violation.

This happens on 2006/06/14 to 2006/06/16. I don't know what else to check. I know I'm the only one getting this. If anyone has any suggestions of anything to try please let me know.

Many thanks.

EDIT: Seems I'm not alone after all.

Me too, I compiled myself with MinGW 3.4.5 and wx 2.3.6 patch 2 on WinXP SP2. but the official build definitely works well for me, not sure why. are you using the self-build version or the official nightly build?

by the way, the linux builds were came out much quicker than before. if you could keep this on, that is should be greate  :o

[edit]
NO, the last official nightly build not works well now, same problem  :(. In linux both OK, is the Linux version will be built by GCC 4.1.1 and wx263 later? because I found that works well.
[/edit]
« Last Edit: June 17, 2006, 06:45:22 am by oz »

Offline Pecan

  • Plugin developer
  • Lives here!
  • ****
  • Posts: 2750
Re: The 16 June 2006 build is out.
« Reply #9 on: June 17, 2006, 01:52:48 pm »
The last version of code::blocks that works on my xp-sp2 system are pre 2006/06/14. After this I get access violations.

This happens on 2006/06/14 to 2006/06/16. I don't know what else to check. I know I'm the only one getting this. If anyone has any suggestions of anything to try please let me know.


This happened to me when I had accidently stowed an old wxmsw26<x>_gcc_cb.dll up the PATH chain.

I deleted all wxWidgets and mingw dll's from the path, re-installed, the all went well.


Offline oz

  • Multiple posting newcomer
  • *
  • Posts: 47
Re: The 16 June 2006 build is out.
« Reply #10 on: June 17, 2006, 03:01:17 pm »
This happened to me when I had accidently stowed an old wxmsw26<x>_gcc_cb.dll up the PATH chain.

I deleted all wxWidgets and mingw dll's from the path, re-installed, the all went well.

sorry, I did not follow you. could you explain more? because if I make a clean install on school's computer, the problem still there. e.g. I choose 'open' or 'project->open', also when I choose the directory.
so, please give a detailed info. thanks veeeeeeeery much. :?

Offline lubos

  • Almost regular
  • **
  • Posts: 131
Re: The 16 June 2006 build is out.
« Reply #11 on: June 17, 2006, 03:29:24 pm »
my last working nightly is rev2565,since that are violations.why?please repair it back!i dont want go to vs2005.

Offline Code Medic

  • Multiple posting newcomer
  • *
  • Posts: 14
cpu usage in curent build
« Reply #12 on: June 17, 2006, 03:49:11 pm »
hav a look at the attachment... byo games... it eats up the processor alive.!  :(
otherwise the processor usage pattern is same as the previous build..!

[attachment deleted by admin]

Offline MortenMacFly

  • Administrator
  • Lives here!
  • *****
  • Posts: 9694
Re: cpu usage in curent build
« Reply #13 on: June 17, 2006, 04:34:59 pm »
hav a look at the attachment... byo games... it eats up the processor alive.!  :(
What do you want to say by this? If you play byoGames you naturally cannot do anything else, so why do you care about the CPU usage then? If you want to work just close byoGames and have "normal" CPU usage... maybe I didn't get the reason for this post...?!
With regards, Morten.
Compiler logging: Settings->Compiler & Debugger->tab "Other"->Compiler logging="Full command line"
C::B Manual: https://www.codeblocks.org/docs/main_codeblocks_en.html
C::B FAQ: https://wiki.codeblocks.org/index.php?title=FAQ

Offline Code Medic

  • Multiple posting newcomer
  • *
  • Posts: 14
Re: cpu usage in curent build
« Reply #14 on: June 17, 2006, 04:44:31 pm »
hav a look at the attachment... byo games... it eats up the processor alive.!  :(
What do you want to say by this? If you play byoGames you naturally cannot do anything else, so why do you care about the CPU usage then? If you want to work just close byoGames and have "normal" CPU usage... maybe I didn't get the reason for this post...?!
With regards, Morten.

cant i have my game paused and resumed later???!!! do i hav to start it all over again?
why sud a plugin be so busy when its doing nothing??? when playing ... i can understand..!!!!

when i was testing the cpu usage... i included the new plug in as well... thats all... sorry if i offended someone
« Last Edit: June 17, 2006, 07:02:50 pm by Code Medic »