Code::Blocks Forums
User forums => Nightly builds => Topic started by: killerbot on August 15, 2006, 06:21:18 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 15 August 2006 build is out.
- Windows : http://prdownload.berlios.de/codeblocks/CB_20060815_rev2853_win32.7z
- Linux :
http://prdownload.berlios.de/codeblocks/CB_20060815_rev2853_Ubuntu6.06.deb
http://prdownload.berlios.de/codeblocks/CB_20060815_rev2853_fc4+5.rpm (not yet)
Resolved Fixed:
- Killed a zombie
- fix to changes of ToolsManager (linux)
- Fixed issue with caret not staying visible in text boxes of various dialogs
- envvars plugin: enable renaming of envvar-keys, take IsChecked into account on edit (do not set envvar if not checked)
- added opengl wizard (modified to enable unix support, thanks sethjackson)
- opengl wizard: fixed issue with linux build
- add codesnippets plug-in to the contribs (TO DO : autobuild settings)
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)
-
- add codesnippets plug-in to the contribs (TO DO : autobuild settings)
Yay, thanks killerbot. Thanks to MortenMacFly too. :)
-
Is there a way to save the state of the block minimizers/expanders? The things between the line numbers and the code area, they always reset, If there isnt a way maybe it could be added to the list of fixes please? :D
-
Is possible to know if an option to generate the makefile will be implemented?
thanks.
-
Is possible to know if an option to generate the makefile will be implemented?
If you ask a question in the forum please do a search before. This question has been answered many times: Creating a Makefile has been disabled (it still is available in RC2 though) due to the changes that have been done and will be done to the build system. Once this work is finished the Makefile generation will be re-attached (and overworked).
Anyway, please notice that Makefiles are much less powerful and result in slower creation in addition compared to C::B. Why would you use Makefiles if you have C::B?! ;-)
With regards, Morten.
-
Wxsmith still hangs.
Hi got a 1,2,3 reproduction of the problem.
1. open new project wx
2. close the project./ C::B
3. open C::B and project again
4. select yes on the import info to file
5. add a Notebook to a dialog.
result ==> C::B 100% cpu time.
test was done on a winXp sp2 machine
-
Additional "feature",
a control is losing all of its settings while its moved in the tree structure.
is this a "known" issue?
regards,
Jewe
-
If you ask a question in the forum please do a search before. This question has been answered many times: Creating a Makefile has been disabled (it still is available in RC2 though) due to the changes that have been done and will be done to the build system. Once this work is finished the Makefile generation will be re-attached (and overworked).
Anyway, please notice that Makefiles are much less powerful and result in slower creation in addition compared to C::B. Why would you use Makefiles if you have C::B?! ;-)
With regards, Morten.
thanks for your answer,
I don't use Makefile explicitly with make.exe, I just need makefile sometime to see exectaly if I toke the good options, good path etc... But you are right I use C::B to avoid problems with makefile.
-
If you ask a question in the forum please do a search before. This question has been answered many times: Creating a Makefile has been disabled (it still is available in RC2 though) due to the changes that have been done and will be done to the build system. Once this work is finished the Makefile generation will be re-attached (and overworked).
Anyway, please notice that Makefiles are much less powerful and result in slower creation in addition compared to C::B. Why would you use Makefiles if you have C::B?! ;-)
With regards, Morten.
thanks for your answer,
I don't use Makefile explicitly with make.exe, I just need makefile sometime to see exectaly if I toke the good options, good path etc... But you are right I use C::B to avoid problems with makefile.
Well, makefiles are usable for example when you want to give your project to someone who doesn't have Code::Blocks yet (why? ;)).
That's why this functionality will probably be back (not in the near future though).
If all you want to do is check the options C::B passes to the compiler/linker, just follow the path in Morten's signature...
-
Well, makefiles are usable for example when you want to give your project to someone who doesn't have Code::Blocks yet (why? ;)).
That's why this functionality will probably be back (not in the near future though).
If all you want to do is check the options C::B passes to the compiler/linker, just follow the path in Morten's signature...
Actually, in my business the long-establish rule is that every piece of code that goes into version
control must have a makefile with it. regarless of whether we actually use the makefile or not.
Some brainiac higher up the food chain than I decided long ago that makefiles would be the company
standard for re-creating a product or family of products.
-- Ron --