User forums > Nightly builds
The 16 June 2006 build is out.
Pecan:
--- Quote from: oz on June 17, 2006, 03:01:17 pm ---
--- Quote from: Pecan on June 17, 2006, 01:52:48 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.
--- End quote ---
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. :?
--- End quote ---
The best I can remember is:
I had a dll build of wxWidgets 2.4.2 sitting in c:/wxWidgets242/lib and a wxWidgets dll build in c:/wxWidgets262/lib.
The path had something like c:\wxWidgets242\lib;c:\codeblocks\bin;c:\window;c:\windows\...blablabla;c:\beta\wxWidgets262\bin;
Somehow my codeblocks system was getting all balled up using the 2.4.2 dlls or the codeblocks2.4.2 dll's with my 2.6.2 build. I got one crash after another every time it attempted to use a system dialog.
I deleted all wxWidgets dll's and all codeblocks dll's I could find from my system. Removed 2.4.2 from the path. Removed codeblocks from the path; rebuilt wxWidgets 2.6.2. Then it all worked fine.
Just my experience. Thought it might help.
orefa:
I was wondering why BYO is included in the regular distribution. I don't see any relation between games and a programming IDE.
Can plug-ins be downloadable add-ons like Firefox extensions? If so then a core set can be included but frills would be downloaded as needed and questions about them would go directly to their writer instead of the C::B developpers.
MortenMacFly:
--- Quote from: orefa on June 17, 2006, 05:42:56 pm ---Can plug-ins be downloadable add-ons like Firefox extensions? If so then a core set can be included but frills would be downloaded as needed and questions about them would go directly to their writer instead of the C::B developpers.
--- End quote ---
This only applies to the nightlies which shall include all plugins on purpose -> for testing! I'd say the installer of a distribution will allow you to select which plugins you'd like to install. And (I guess you know already) you can disable plugin(s) you don't need/like. They remain disabled if you install a new nightly. You can even just delete the DLL of the plugin you don't like at all from the C::B folder it it's gone until you install it again...
With regards, Morten.
orefa:
Cool. Thanks. :)
oz:
--- Quote from: Pecan on June 17, 2006, 05:30:14 pm ---The best I can remember is:
I had a dll build of wxWidgets 2.4.2 sitting in c:/wxWidgets242/lib and a wxWidgets dll build in c:/wxWidgets262/lib.
The path had something like c:\wxWidgets242\lib;c:\codeblocks\bin;c:\window;c:\windows\...blablabla;c:\beta\wxWidgets262\bin;
Somehow my codeblocks system was getting all balled up using the 2.4.2 dlls or the codeblocks2.4.2 dll's with my 2.6.2 build. I got one crash after another every time it attempted to use a system dialog.
I deleted all wxWidgets dll's and all codeblocks dll's I could find from my system. Removed 2.4.2 from the path. Removed codeblocks from the path; rebuilt wxWidgets 2.6.2. Then it all worked fine.
Just my experience. Thought it might help.
--- End quote ---
emm....clear, but it seems the different problem we have. it actually does not crash, just pop up a dialog box, I randomly click whatever I want :lol: 'Abort', 'Cancel' or 'Ignore', and the CB will works as normal after that, it will not generate a report either. Because when I am at school, I have to make the clean install every time, so...do not have your problem, but thanks anyway. Anyone has some idea on that?
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version