csde_rats
Newcomer
Posts: 2
|
 |
« Reply #45 on: January 09, 2010, 03:31:24 pm » |
|
Currenty I can't download this nightly build, it seems like berlios.de isn't currently reachable.
Could anyone upload it to his/her server or a free file hoster?
|
|
|
|
|
Logged
|
|
|
|
|
|
|
|
csde_rats
Newcomer
Posts: 2
|
|
« Reply #48 on: January 09, 2010, 05:46:45 pm » |
|
Thanks a lot!  |
|
|
|
|
Logged
|
|
|
|
JRHeisey
Newcomer
Posts: 1
|
|
« Reply #49 on: January 09, 2010, 08:58:56 pm » |
|
I really appreciate the continued development of CB. It looks like there has not been a major stable release of CB since 8.02. It has been almost two years. I would like to suggest that it is time. Also the road map on the twiki at http://wiki.codeblocks.org/index.php?title=Roadmap hasn't been updated in two years. Is there another publicly available road map? Thanks, J.R. Heisey |
|
|
|
|
Logged
|
|
|
|
Wavesonics
Advanced newcomer
Posts: 39
|
|
« Reply #50 on: January 11, 2010, 05:10:03 pm » |
|
The "Lets please have a new Stable release" debate is a sensitive topic on here, treed softly  |
|
|
|
|
Logged
|
|
|
|
|
Loaden
|
|
« Reply #51 on: January 12, 2010, 04:02:26 pm » |
|
The button to see the status unclear, it is recommended to use gray icon represents is not enabled, while the colored icons on behalf of the opening.
Thanks!
Disabled buttons are in fact greyed out. What you mean (I think) is the difference between toggled (active option) and untoggled (inactive option) button. On XP there is not much difference between the two states, on linux it's much better. I will look into it. Also, why the path does not support global variables? For example: $ (WX.include) or $ (WX)
Because it's not (yet) implemented. I will see how easy this can be done. Thanks for the suggestion. SVN 6077, This version still does not work properly. From the search results view, ThreadSearch did not receive $ (WX) the correct path. |
|
|
|
|
Logged
|
|
|
|
|
Loaden
|
|
« Reply #52 on: January 12, 2010, 04:07:19 pm » |
|
This API can not be resolved, do not know whether the information will help CC the bug fixes? #include <iostream>
#include <string>
#include <windows.h>
using namespace std;
int main()
{
Wai
string s;
return 0;
}
|
|
|
|
|
Logged
|
|
|
|
|
Loaden
|
|
« Reply #53 on: January 12, 2010, 04:11:01 pm » |
|
With make_pair, seems CC can not resolve it correctly.
|
|
|
|
|
Logged
|
|
|
|
|
jens
|
|
« Reply #54 on: January 12, 2010, 04:49:07 pm » |
|
The button to see the status unclear, it is recommended to use gray icon represents is not enabled, while the colored icons on behalf of the opening.
Thanks!
Disabled buttons are in fact greyed out. What you mean (I think) is the difference between toggled (active option) and untoggled (inactive option) button. On XP there is not much difference between the two states, on linux it's much better. I will look into it. Also, why the path does not support global variables? For example: $ (WX.include) or $ (WX)
Because it's not (yet) implemented. I will see how easy this can be done. Thanks for the suggestion. SVN 6077, This version still does not work properly. From the search results view, ThreadSearch did not receive $ (WX) the correct path. Try $(#wx) ! |
|
|
|
|
Logged
|
|
|
|
|
Loaden
|
|
« Reply #55 on: January 12, 2010, 05:22:12 pm » |
|
The button to see the status unclear, it is recommended to use gray icon represents is not enabled, while the colored icons on behalf of the opening.
Thanks!
Disabled buttons are in fact greyed out. What you mean (I think) is the difference between toggled (active option) and untoggled (inactive option) button. On XP there is not much difference between the two states, on linux it's much better. I will look into it. Also, why the path does not support global variables? For example: $ (WX.include) or $ (WX)
Because it's not (yet) implemented. I will see how easy this can be done. Thanks for the suggestion. SVN 6077, This version still does not work properly. From the search results view, ThreadSearch did not receive $ (WX) the correct path. Try $(#wx) ! OK, it's work fine! |
|
|
|
|
Logged
|
|
|
|
pir
Advanced newcomer
Posts: 25
|
|
« Reply #56 on: January 12, 2010, 10:40:44 pm » |
|
Having problems with this build on Ubuntu 9.10. I get a message:
"codeblocks: relocation error: /usr/lib/libcodeblocks.so.0: symbol _Z18wxSafeConvertWX2MBPKw, version WXU_2.8 not defined in file libwx_baseu-2.8.so.0 with link time reference"
which I gather from a previous post is wxWidgets-related. I have:
libwxbase2.8
wx-common
libwxgtk2.8-0
installed (+ a few dev versions). All are version 2.8.10.1-1 from apt.wxwidgets.org/universe
Can anybody tell me what's wrong? Have I got the wrong packages?
BTW: The CodeBlocks packages come from lgp203.free.fr/universe: codeblocks, codeblocks-common, codeblocks-contrib, codeblock-contrib-common and libwxsmithlib0, all versions svn6023-0ubuntu1-karmic.
Peter
|
|
|
|
|
Logged
|
|
|
|
|
jens
|
|
« Reply #57 on: January 12, 2010, 10:54:16 pm » |
|
pasgui's packages for karmic are build against the wxwidgets-packages shipped with ubuntu 9.10 (karmic koala), the ubuntu-packages and the packages from apt.wxwidgets.org are not fully comaptible. The nightly builds will depend/based upon wxWidgets 2.8.10, which is not available in the default Ubuntu repositories except for Karmic Koala.To successfully install these packages, you have to add the wxWidgets repository except for Karmic Koala on i386 architecture where the universe repository must be enabled. That means you have to use the packages shipped with ubuntu 9.10 if you use the codeblocks-packages for karmic. |
|
|
|
|
Logged
|
|
|
|
pir
Advanced newcomer
Posts: 25
|
|
« Reply #58 on: January 12, 2010, 11:11:19 pm » |
|
Right! Got it. Works now.
(This package business has confused me. I have clearly misinterpreted the role of packages from wxWidgets).
Peter
|
|
|
|
|
Logged
|
|
|
|
|
