User forums > Using Code::Blocks

Changing the installation directory for Borland Compiler

(1/3) > >>

glenc:
I have changed the installation directory for the Borland C++ compiler to
C:\Progam Files\Borland\CBuilder6 in Settings->Compiler and Debugger->Programs but the build doesn't recognize it.
The result is

ilink32.exe -q -aa  -v -Tpe -aa  -LC:\wxWidgets-2.6.3\lib\bcc_lib -LC:\Borland\BCC55\lib  c0w32 obj\Debug\main.obj obj\Debug\app.obj ,bin\Debug\test.exe,,wxmsw26d_core.lib wxbase26d.lib wxpngd.lib wxzlibd.lib import32.lib cw32mti.lib ole2w32.lib kernel32.lib user32.lib gdi32.lib winspool.lib comdlg32.lib advapi32.lib shell32.lib ole32.lib oleaut32.lib uuid.lib comctl32.lib wsock32.lib odbc32.lib ,,

which gives me link errors because libs are not found. The -L parameter points to the default path.

What am I doing wrong?

stahta01:
Did you also updated Code::Blocks
Settings->Compiler and Debugger->Directories
Compiler
Linker
Resource Compiler

Tim S

glenc:
Yes, they all point to the correct programs. Another thought - if I use the default Borland compiler, my project shouldn't compile because the path C:\Borland\BC55 doesn't exist, and yet it does compile. It is obviously using my $PATH settings. Is this correct?
By the way, I'm using the Jan. 1 CodeBlocks build.

stahta01:
Have you check for bad info in the Borland file bcc32.cfg ?
Most likely under C:\Progam Files\Borland\CBuilder6 .
Tim S

stahta01:
Does your PATH variable contain the old C:\Borland\BCC55 or C:\BCC55 in it?
Is so remove it and test again.

As a last resort, Open the project file .cbp file in a text editor and look for BCC55 in it.
If yes, you have project settings that need updating.

Note: after changing the PATH variable, I always exit and re-start codeblocks; I am not sure if that is needed but I do it.
Tim S

Navigation

[0] Message Index

[#] Next page