Code::Blocks Forums

User forums => Nightly builds => Topic started by: killerbot on November 17, 2006, 09:07:44 pm

Title: The 17 november 2006 build is out.
Post by: killerbot on November 17, 2006, 09:07:44 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://prdownload.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://prdownload.berlios.de/codeblocks/mingwm10.7z

For support of ansi builds, a link to the ansi windows wxWidget dll for Code::Blocks : http://prdownload.berlios.de/codeblocks/wxmsw26_gcc_cb_wx2.6.3p2.7z

The 17 November 2006 build is out.
  - Windows : http://prdownload.berlios.de/codeblocks/CB_20061117_rev3230_win32.7z
  - Linux :
         http://prdownload.berlios.de/codeblocks/CB_20061117_rev3230_Ubuntu6.06.deb
         http://prdownload.berlios.de/codeblocks/CB_20061117_rev3230_suse100+101.rpm (not yet)
         http://prdownload.berlios.de/codeblocks/CB_20061117_rev3230_fc4+5.rpm (not yet)


Resolved Fixed:


Regressions/Confirmed/Annoying/Common bugs:


Title: Re: The 17 november 2006 build is out.
Post by: cstudent on November 17, 2006, 10:13:47 pm
Ubuntu 6.10 (Edgy) build here (http://www.savefile.com/projects/1037211).
Title: Re: The 17 november 2006 build is out.
Post by: godcode on November 18, 2006, 05:56:27 am
dudes i get this error:

Can not enumerate files in directory 'c:\Documents and Settings\mon\Application Data\codeblocks/share/codeblocks/plugins' (error 3: the system cannot find the path specified.)

usually happens when codeblocks is run for the very first time on computers without any previous codeblocks installation
Title: Re: The 17 november 2006 build is out.
Post by: discoverer on November 18, 2006, 09:10:46 am
Quote from: godcode on November 18, 2006, 05:56:27 am
dudes i get this error:

Can not enumerate files in directory 'c:\Documents and Settings\mon\Application Data\codeblocks/share/codeblocks/plugins' (error 3: the system cannot find the path specified.)

usually happens when codeblocks is run for the very first time on computers without any previous codeblocks installation

I encounter the same problem, and not only the first time but always ...
Title: Re: The 17 november 2006 build is out.
Post by: MortenMacFly on November 18, 2006, 11:06:38 am
Quote from: discoverer on November 18, 2006, 09:10:46 am
I encounter the same problem, and not only the first time but always ...
I encountered this myself when I installed C::B fresh on a "clean" PC. I solved it by just creating that folder - but this *should* be done automatically for you. Please file a bug report (keep in mind that there maybe already one like that).
Still unclear: Is it better to just create that folder (thus guiding the user that there is another option to place e.g. private plugins) or don't show this error (as this directory isn't really required if it's empty)???
With regards, Morten.
Title: Re: The 17 november 2006 build is out.
Post by: sebsheep on November 18, 2006, 02:36:47 pm
Hi,

i'm a noob with linux and I tried to install C::B thank the post of cstudent on Ubuntu 6.06.
When I try to launch the installation, i've got the error : "Dependency is not satisfiable : libatk1.0-0", but this lib is correctly installed according Synaptic.

What is the problem?
Title: Re: The 17 november 2006 build is out.
Post by: rjmyst3 on November 18, 2006, 04:33:37 pm
The post of cstudent is for Ubuntu Edgy (6.10).

If you want a package for Ubuntu Dapper (6.06) it is always in killerbot's starting post.

My guess is that the edgy package depends on newer versions of the same libraries, versions which are not available to dapper. So, Synaptic says you have the latest version available to you, but it still is not as new as the version of the library in the latest version of Ubuntu.
Title: Re: The 17 november 2006 build is out.
Post by: marfi on November 19, 2006, 02:09:47 pm
hello,
i'd like to alert to two bugs:

1) "Profiler settings" panel (Settings->Compiler and debugger settings) is displayed twice

2) CDB debugger (more exactly working paths settings) seems to work wrong. I tried to debug basic Irrlicht project (created by Code::Blocks generic application wizard for Irrlicht library) with CBD debugger and the result (the debugger log) is shown bellow:

Code
Building to ensure sources are up-to-date
Build succeeded
Selecting target: VS2005 Debug
[color=yellow]Adding source dir: C:\MyWork\Source\VC++\CBIrrHello\
Adding source dir: C:\MyWork\Source\VC++\CBIrrHello\
Changing directory to: bin/Debug2005
Adding file: bin\Debug2005\CBIrrHello.exe[/color]
Starting debugger: done
Setting breakpoints
quit:
Microsoft (R) Windows Debugger  Version 6.6.0007.5
Copyright (c) Microsoft Corporation. All rights reserved.
CommandLine: bin/Debug2005/CBIrrHello.exe
[color=yellow]Symbol search path is: C:/MyWork/Source/VC++/CBIrrHello/
Executable search path is: [/color]
ModLoad: 00400000 00436000   CBIrrHello.exe
ModLoad: 7c900000 7c9b0000   ntdll.dll
ModLoad: 7c800000 7c8f4000   C:\WINDOWS\system32\kernel32.dll
ModLoad: 10000000 10130000   C:\MyWork\Source\VC++\CBIrrHello\bin\Debug2005\Irrlicht.dll
ModLoad: 77d40000 77dd0000   C:\WINDOWS\system32\USER32.dll
ModLoad: 77f10000 77f57000   C:\WINDOWS\system32\GDI32.dll
ModLoad: 77dd0000 77e6b000   C:\WINDOWS\system32\ADVAPI32.dll
ModLoad: 77e70000 77f01000   C:\WINDOWS\system32\RPCRT4.dll
ModLoad: 5ed00000 5edcc000   C:\WINDOWS\system32\OPENGL32.dll
ModLoad: 77c10000 77c68000   C:\WINDOWS\system32\msvcrt.dll
ModLoad: 68b20000 68b40000   C:\WINDOWS\system32\GLU32.dll
ModLoad: 73760000 737a9000   C:\WINDOWS\system32\DDRAW.dll
ModLoad: 73bc0000 73bc6000   C:\WINDOWS\system32\DCIMAN32.dll
(a30.65c): Break instruction exception - code 80000003 (first chance)
eax=00251eb4 ebx=7ffd9000 ecx=00000003 edx=00000008 esi=00251f48 edi=00251eb4
eip=7c901230 esp=0013fb20 ebp=0013fc94 iopl=0         nv up ei pl nz na po nc
cs=001b  ss=0023  ds=0023  es=0023  fs=003b  gs=0000             efl=00000202
*** ERROR: Symbol file could not be found.  Defaulted to export symbols for ntdll.dll - 
ntdll!DbgBreakPoint:
7c901230 cc              int     3
*** WARNING: Unable to verify checksum for CBIrrHello.exe
*** WARNING: Unable to verify checksum for C:\MyWork\Source\VC++\CBIrrHello\bin\Debug2005\Irrlicht.dll
*** ERROR: Symbol file could not be found.  Defaulted to export symbols for C:\MyWork\Source\VC++\CBIrrHello\bin\Debug2005\Irrlicht.dll -
*** ERROR: Symbol file could not be found.  Defaulted to export symbols for C:\WINDOWS\system32\OPENGL32.dll -
*** ERROR: Symbol file could not be found.  Defaulted to export symbols for C:\WINDOWS\system32\GLU32.dll -
*** ERROR: Symbol file could not be found.  Defaulted to export symbols for C:\WINDOWS\system32\DDRAW.dll -
*** ERROR: Symbol file could not be found.  Defaulted to export symbols for C:\WINDOWS\system32\DCIMAN32.dll -
*** ERROR: Symbol file could not be found.  Defaulted to export symbols for C:\WINDOWS\system32\msvcrt.dll -
*** ERROR: Symbol file could not be found.  Defaulted to export symbols for C:\WINDOWS\system32\USER32.dll -
*** ERROR: Symbol file could not be found.  Defaulted to export symbols for C:\WINDOWS\system32\ADVAPI32.dll -
*** ERROR: Symbol file could not be found.  Defaulted to export symbols for C:\WINDOWS\system32\RPCRT4.dll -
*** ERROR: Symbol file could not be found.  Defaulted to export symbols for C:\WINDOWS\system32\GDI32.dll -
*** ERROR: Symbol file could not be found.  Defaulted to export symbols for C:\WINDOWS\system32\kernel32.dll -
Debugger finished with status 0

CDB changes the execution working dir to "C:/MyWork/Source/VC++/CBIrrHello/" despite my project settings ("C:/MyWork/Source/VC++/CBIrrHello/bin/Debug2005"), moreover, it seem that the debugger symbol file is generated into execution working directory set in the project settings, but CDB symbols search path is the main project directory. This i probably the reason for debugger errors displayed above.

Is there any way how to specify (examine) the command line for CDB debugger?
Title: Re: The 17 november 2006 build is out.
Post by: MortenMacFly on November 19, 2006, 02:14:09 pm
Quote from: marfi on November 19, 2006, 02:09:47 pm
1) "Profiler settings" panel (Settings->Compiler and debugger settings) is displayed twice
Check out your C::B\share\CodeBlocks\plugins folder. There are two profiler DLL's: One is called profiler.dll (the right one) and one is called cbprofiler.dll (a very old version). If people blindly overinstalling new builds such things happen.
With regards, Morten.
Title: Re: The 17 november 2006 build is out.
Post by: marfi on November 19, 2006, 02:48:24 pm
to MortenMacFly:

thanx to your advice I have only one instance of code profiler settings panel in CB now ( :wink: ), but your undelined note about using of Full command line log option haven't helped me because it affects compiler and linker output only, not the debugger log output...

With regards, Marfi
Title: Re: The 17 november 2006 build is out.
Post by: MortenMacFly on November 19, 2006, 03:11:18 pm
Quote from: marfi on November 19, 2006, 02:48:24 pm
but your undelined note about using of Full command line log option haven't helped me [...]
This is not an underlined note but my signature which is appended on all of my posts automatically... ;-)
With regards, Morten.
Title: Re: The 17 november 2006 build is out.
Post by: Madster on November 20, 2006, 04:17:02 pm
Tool command line options stopped working in this build (maybe earlier):

example for Binify 0.2:

Name:Binify
Executable: C:\Archivos de programa\binify\binify-0.2\binify.exe
Parameters: ${ACTIVE_EDITOR_FILENAME}

Launching from the interfase (Tools/Binify) gives this output:
Launching tool 'Binify': C:\Archivos de programa\binify\binify-0.2\binify.exe ${ACTIVE_EDITOR_FILENAME} (in D:\Madman\coding\megamad\bin\Debug)
Tool execution terminated with status -1073741819

notice that the parameter wasn't replaced by its value  :shock:
Title: Re: The 17 november 2006 build is out.
Post by: Pecan on November 20, 2006, 08:59:47 pm
Quote from: Madster on November 20, 2006, 04:17:02 pm
Tool command line options stopped working in this build (maybe earlier):

example for Binify 0.2:

Name:Binify
Executable: C:\Archivos de programa\binify\binify-0.2\binify.exe
Parameters: ${ACTIVE_EDITOR_FILENAME}

Launching from the interfase (Tools/Binify) gives this output:
Launching tool 'Binify': C:\Archivos de programa\binify\binify-0.2\binify.exe ${ACTIVE_EDITOR_FILENAME} (in D:\Madman\coding\megamad\bin\Debug)
Tool execution terminated with status -1073741819

notice that the parameter wasn't replaced by its value  :shock:

http://forums.codeblocks.org/index.php?topic=4472.msg35369#msg35369