Code::Blocks Forums
User forums => Nightly builds => Topic started by: killerbot on November 09, 2006, 10:52:59 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 09 November 2006 build is out.
- Windows : http://prdownload.berlios.de/codeblocks/CB_20061109_rev3197_win32.7z
- Linux :
http://prdownload.berlios.de/codeblocks/CB_20061109_rev3197_Ubuntu6.06.deb
http://prdownload.berlios.de/codeblocks/CB_20061109_rev3197_suse100+101.rpm (not yet)
http://prdownload.berlios.de/codeblocks/CB_20061109_rev3197_fc4+5.rpm (not yet)
Resolved Fixed:
- wxPdfDocument updated to version 0.7.6
- added new GTK wizard (Windows only)
Regressions/Confirmed/Annoying/Common bugs:
- toolbar-images-not-changing-state (is a wx problem/Win XP problem)
- menu items with icon not correctly aligned (since wx263)
-
Hey. New arivial here.
This is the first nightly I've tried so I don't know if this is a recent bug. When trying to build JUCE 1.39 (http://www.rawmaterialsoftware.com/juce/ ) with the MS VC 2003 Toolkit I get a linker error that indicates that the linker command string has been cut short.
Some earlier (smaller) versions build ok.
The current version (1.39) builds ok with all the other supported environments and I've looked at the project settings but find no problem.
The error looks like so:
:: === JUCE, Win32 Release ===
LINK:: fatal error LNK1181: cannot open input file '..\..\..\bin\intermediate_win32\static\src\juce_core\threads\juc'
:: === Build finished: 1 errors, 0 warnings ===
The path should read
"..\..\..\bin\intermediate_win32\static\src\juce_core\threads\juce_TimeSliceThread.obj"
So, is there some kind of string size limit at work on the linker command?
-
I tried to build Juce and got error also.
LINK:: fatal error LNK1181: cannot open input file '..\..\..\bin\inter'
I have changed the project file and got it to compile, I think a path is too long and the link command crashes.
What is the length allowed on link command? The one this project produces is several thousand bytes long.
Do you want me to send the .cbp file to you? If so, created from VC6 or VC8 conversion?
Size of Link command that works: 30,091
Size of Link command that fails: 33,180
code requires unsigned 16 bit int for values over 32767 my guess code in C::B or in windows is using signed 16 bit int.
Tim S
-
Thank you for your offer, but given that Jules releases new versions pretty often I need a more permanent solution.
It's good to know that it actually is the size of the command. Maybe there's a fix in the pipeline?
-
Thank you for your offer, but given that Jules releases new versions pretty often I need a more permanent solution.
It's good to know that it actually is the size of the command. Maybe there's a fix in the pipeline?
All I did was move the cbp file to same juce folder that holds juce.h file
and used a good text editor to change these items in the cbp file.
"..\..\..\" to ""
"..\platform_specific_code" to "build\win32\platform_specific_code"
Tim S
-
Oh. well that wasn't too bad. I guess all those ../ adds up. :D
-
Ubuntu 6.10 (Edgy) build here (http://www.savefile.com/projects/1037211).
-
3199 local build crashes in FindDlg::FindDlg, ReplaceDlg::ReplaceDlg. See attached crash reports.
[attachment deleted by admin]
-
are your xrc's up to date in the zip file ??
try :
make clean-zipfiles
make clean-binfiles
make clean
make
-
are your xrc's up to date in the zip file ??
try :
make clean-zipfiles
Aaah, that did the trick, thanks.
-
Has something changed on the code completion plugin? The version of 2006/10/29 works very well while the current version seems to have problems seeing all available functions.
-
Has something changed on the code completion plugin? The version of 2006/10/29 works very well while the current version seems to have problems seeing all available functions.
Nothing that would change its behaviour.
Read its log here (http://svn.berlios.de/wsvn/codeblocks/trunk/src/plugins/codecompletion/?op=log&rev=0&sc=0&isdir=1).