20051128 build

[jmccay]

I just installed the 11/28/2005 build over RC2, and I get "The procedure entry point _ZN8wxDialog17MSWProcessMessageEP6tagMSG could not be located in the dynamic link library wxmsw26_gcc_cb.dll."

   I downloaded the dll from the web page & installed it in the c:\windows\system32 directory.  I am next going to try a reboot since I been running C::B with another dll just in case XP still has the old in memory.

Anyone else know how to solve the problem?
jmccay

[sethjackson]

You mean you installed the new C::B over the old one in porgram files? I don't think that is a good idea. Uninstall C::B then install the new C::B and see what happens.

[jmccay]

Actually, I installed the build from http://paginas.terra.com.br/informatica/mauricio/codeblocks/ for the 20051128 build.  It doesn't come with an installer.  I think I copied the DLL to the wrong place.  I need to try this again.

jmccay

[jmccay]

ok.  I reinstalled, and I got it to run.  When I attempt to compile, I get the following error:
"Can't create object output directory C:\development\projects\code\20051026wxTest\wx_pch.h.gch\"

Any ideas?
jmccay

[jmccay]

Where do you get the cc1plus.exe and the other stuff needed?

jmccay

[Ceniza]

Where do you get the cc1plus.exe and the other stuff needed?

Check this and this too (to install MinGW, which is one of the supported compilers)

[Urxae]

ok.  I reinstalled, and I got it to run.  When I attempt to compile, I get the following error:
"Can't create object output directory C:\development\projects\code\20051026wxTest\wx_pch.h.gch\"

Any ideas?
jmccay

Did you previously compile precompiled headers to a file instead of a directory? If so, there may be a file by that name remaining. As long as that's there, you obviously can't create that directory there. Delete it and try again.

[jmccay]

I figured out my problem.  When I copied the build files into the C::B directory, my directories settings were still stored in the registry.  The new build only saw the stuff in the %APPDATA%.  This meant that my mingw directory (the prepackage one) was not in the list of directoires.  I can't test this out tonight, but I plan on doing it tomorrow or on Friday when I get the time.  The error now makes sense because it was not seeing the mingw.