Codeblock do not start properly

[luisalberto]

Iam using Codeblocks ver. svn rev5911 on Windows Vista Basic. When I start Codeblocks the welcome splash screen appear and then the program seems to be halted. When I check the Windows Task Manager both compilers mingw32-gcc-4.4.0.exe and mingw32-gcc.exe has been called and are in memory. And it is only when I kill those processes using Windows task manager that Codeblocks can be started normally. Today I removed the path c:\mingw\bin from the Path environment variable from Vista to see if Codeblock IDE do not find the compilers and could be started normally but to no avail. It continues loading in memory those compilers and do not start until I kill the compiler processes. Perhaps those compilers are waiting to compile something and the Codeblocks start up process is halted. Perhaps Codeblocks ask the compilers their version number and as a result the start up is halted do to a version mismatch. This has been occurring in the last 3 nighties but do not occurred on Windows XP. I have Mingw version 4.4.0 installed.

[ollydbg]

I also have vista basic, and install the codeblocks SVN and TDM GCC 4.4.1. I haven't meet this problem. The most probability is like your said:

Perhaps those compilers are waiting to compile something and the Codeblocks start up process is halted. Perhaps Codeblocks ask the compilers their version number and as a result the start up is halted do to a version mismatch.

 

[MortenMacFly]

Perhaps Codeblocks ask the compilers their version number and as a result the start up is halted do to a version mismatch.

I doubt this happens casue such functionality is not implemented.

However - please enable full compiler logging (see my sig), than note down the command line C::B is using to compile your file and try exactly that in a command shell (command prompt) on Windows to see what happens. If it happens in the command shell, too it seems to be an issue with the compiler.

Do you have setup MinGW/GCC as defualt compiler, or as a copied compiler?

[Jenna]

If I understand it correctly the OP has a problem starting C::B.

And while starting we call in fact the standard compiler (compilerMINGW.cpp:368) to determine the version-string.

I can not see if something wents wrong here, but instead of only removing the MiNG's path from environment, I suggest renaming the folder MinGW resides in, because C::B executes the gcc in the compiler's masterpath.

Another possibility would be to rename C::B's config-folder (the one where default.conf is in,  don't know the vista path at the moment, because I'm on linux), to see if it works then.

[MortenMacFly]

And while starting we call in fact the standard compiler (compilerMINGW.cpp:368) to determine the version-string.

Yes, but if that may fail it's quite certain that calling the compiler for other purposes (e.g. ... erm... compiling?!) fails, too.

For me it works just fine under Vista (ult.) daily.

[luisalberto]

I have renamed the c:\MinGw directory to c:\MinGW1 and only then I can start Codeblocks without any problem. Previously I have deleted C::B's config-folder (the one where default.conf) is and C::B creates a new one with the default configuration asking me again for the default compiler. I also change the default compiler to VC2008 and it continues loading the compilers in memory and with the program halted. I continuosly use VC2008 and Codeblocks for one of my program that compiles using makefiles. One program for VC2008 (nmake.exe) and other for MinGW (mingw32-make). I have also always compiled wxwidgets using mingw32-make on the command line window on Vista and I do not have any problem. Right now I am starting to believe that the start up sequence of C::B asking for version string to the compilers perhaps needs a switch like -v but I do not Know. Thanks for your help and congratulations for the great IDE that is C::B.