Code::Blocks

User forums => Using Code::Blocks => Topic started by: diego_pmc on October 07, 2009, 09:07:08 pm

Title: Getting Borland C++ compiler to work on CB
Post by: diego_pmc on October 07, 2009, 09:07:08 pm
I asked about this before. I want to get this compiler to work on CB for my school, not for me. I've never tried installing a new compiler before, so please bare with me. :D

I downloaded Borland C++ from embarcadero.com (https://downloads.embarcadero.com/free/c_builder) (my mirror). I extracted it (not install) in the default folder (C:\Borland\BCC55), and I set it as the default compiler for CB. CB detects it and I even get error reports (does that mean there's a debugger included?).

The problem is I can't seem find a file called "C0X32.OBJ" and Windows Finder can't find it either in BC++'s folder;here's the code and the error:
Code: Text
  1. // as I understand BC++ is an old compiler, which still
  2. // uses the outdated version of the language. I want
  3. // to use it to compiler programs written in 'old' C++
  4. #include <iostream.h>
  5. #include <conio.h>
  6.  
  7. void main()
  8. {
  9.     cout << "works";
  10.     getch();
  11. }

Quote
Unable to open file 'C0X32.OBJ'
=== Build finished: 1 errors, 0 warnings ===

It would be great if I could get this working, and I'd greatly appreciate any help.


Title: Re: Getting Borland C++ compiler to work on CB
Post by: diego_pmc on October 07, 2009, 09:19:15 pm
I clicked "Reset to default" in CB's compiler options and I started all over. Now a seem to get some other stranger errors, but still related to C0X32.OBJ:
Code: [Select]
Compiling: C:\Documents and Settings\Paul\Desktop\bcpp.cpp
C:\Documents and Settings\Paul\Desktop\bcpp.cpp:
Linking console executable: C:\Documents and Settings\Paul\Desktop\bcpp.exe
Error: Unresolved external '___CRTL_VCL_Init' referenced from C:\BORLAND\BCC55\LIB\C0X32.OBJ
Error: Unresolved external '___CRTL_MEM_UseBorMM' referenced from C:\BORLAND\BCC55\LIB\C0X32.OBJ
Error: Unresolved external '___CRTL_VCLLIB_Linkage' referenced from C:\BORLAND\BCC55\LIB\C0X32.OBJ
Error: Unresolved external '__ExceptInit' referenced from C:\BORLAND\BCC55\LIB\C0X32.OBJ
Error: Unresolved external 'GetModuleHandleA' referenced from C:\BORLAND\BCC55\LIB\C0X32.OBJ
Error: Unresolved external '__startup' referenced from C:\BORLAND\BCC55\LIB\C0X32.OBJ
Error: Unresolved external '__GetExceptDLLinfoInternal' referenced from C:\BORLAND\BCC55\LIB\C0X32.OBJ
Error: Unresolved external 'HeapAlloc' referenced from C:\BORLAND\BCC55\LIB\C0X32.OBJ
Error: Unresolved external '___CRTL_TLS_SetValue' referenced from C:\BORLAND\BCC55\LIB\C0X32.OBJ
Error: Unresolved external '___CRTL_TLS_InitThread' referenced from C:\BORLAND\BCC55\LIB\C0X32.OBJ
Error: Unresolved external '___CRTL_TLS_Alloc' referenced from C:\BORLAND\BCC55\LIB\C0X32.OBJ
Error: Unresolved external '___CRTL_TLS_GetValue' referenced from C:\BORLAND\BCC55\LIB\C0X32.OBJ
Error: Unresolved external 'GetProcessHeap' referenced from C:\BORLAND\BCC55\LIB\C0X32.OBJ
Error: Unresolved external 'HeapFree' referenced from C:\BORLAND\BCC55\LIB\C0X32.OBJ
Error: Unresolved external '___CRTL_TLS_ExitThread' referenced from C:\BORLAND\BCC55\LIB\C0X32.OBJ
Error: Unresolved external '___CRTL_TLS_Free' referenced from C:\BORLAND\BCC55\LIB\C0X32.OBJ
Error: Unresolved external 'std::cout' referenced from C:\DOCUMENTS AND SETTINGS\PAUL\DESKTOP\BCPP.OBJ
Error: Unresolved external 'std::basic_ostream<char, std::char_traits<char> >& std::operator <<(std::basic_ostream<char, std::char_traits<char> >&, const char *)' referenced from C:\DOCUMENTS AND SETTINGS\PAUL\DESKTOP\BCPP.OBJ
Error: Unresolved external '_getch' referenced from C:\DOCUMENTS AND SETTINGS\PAUL\DESKTOP\BCPP.OBJ
Error: Unresolved external '__matherr' referenced from C:\BORLAND\BCC55\LIB\C0X32.OBJ
Error: Unresolved external '__matherrl' referenced from C:\BORLAND\BCC55\LIB\C0X32.OBJ
Error: Unresolved external '__fmode' referenced from C:\BORLAND\BCC55\LIB\C0X32.OBJ
Error: Unresolved external '__argv_expand_ptr' referenced from C:\BORLAND\BCC55\LIB\C0X32.OBJ
Error: Unresolved external '__wargv_expand_ptr' referenced from C:\BORLAND\BCC55\LIB\C0X32.OBJ
Error: Unresolved external '__handle_setargv' referenced from C:\BORLAND\BCC55\LIB\C0X32.OBJ
Error: Unresolved external '__handle_exitargv' referenced from C:\BORLAND\BCC55\LIB\C0X32.OBJ
Error: Unresolved external '__handle_wsetargv' referenced from C:\BORLAND\BCC55\LIB\C0X32.OBJ
Error: Unresolved external '__handle_wexitargv' referenced from C:\BORLAND\BCC55\LIB\C0X32.OBJ
Error: Unresolved external '__fileinfo' referenced from C:\BORLAND\BCC55\LIB\C0X32.OBJ
Error: Unresolved external '__setargv__' referenced from C:\BORLAND\BCC55\LIB\C0X32.OBJ
Error: Unresolved external '__setenvp__' referenced from C:\BORLAND\BCC55\LIB\C0X32.OBJ
Error: Unresolved external '__turboFloat' referenced from C:\BORLAND\BCC55\LIB\C0X32.OBJ
Process terminated with status 2 (0 minutes, 0 seconds)
0 errors, 0 warnings
Title: Re: Getting Borland C++ compiler to work on CB
Post by: stahta01 on October 07, 2009, 10:00:18 pm
Read this message on how I setup Code::Blocks for BCC 5.5


http://forums.codeblocks.org/index.php/topic,11261.msg76703.html#msg76703

If complete newbie try these links
http://apurvaslair.50g.com/cpp/compilers/borland.html
http://rudeserver.com/how-to/install-borland/

Tim S.

PS: Please read the posts you start....

Title: Re: Getting Borland C++ compiler to work on CB
Post by: diego_pmc on October 07, 2009, 10:36:32 pm
Thanks, the last two links helped. I am able to create and run programs from the cmd window, but I still get the same errors in CB. Was this to be expected? What didn't I understand?
Title: Re: Getting Borland C++ compiler to work on CB
Post by: stahta01 on October 08, 2009, 01:54:19 pm
Did you add the needed Libs?

Turn on full Compiler Logging

http://wiki.codeblocks.org/index.php?title=FAQ#Q:_How_do_I_troubleshoot_an_compiler_problem.3F

Tim S.
Title: Re: Getting Borland C++ compiler to work on CB
Post by: iskatel on December 24, 2009, 08:34:18 pm
I had the same problem, I couldn't compile in the command line but not in Code::Blocks IDE, even after creating files bcc32.cfg and ilink32.cfg, so I tried the following:
Settings>> Compiler and debuggers... >> linker settings
and under "link libraries" box I clicked "Add" button and I went to directory "C:\Borland\BCC55\Lib" and added all the files that were visible ( Library files (*.a, *.so, *.lib, *.dyl) and now I can compile from CB IDE using Borland compiler.
Title: Re: Getting Borland C++ compiler to work on CB
Post by: stahta01 on December 24, 2009, 09:03:02 pm
The .cfg I am using once or twice a year.
My Borland  Installation is in folder "D:\GreenApps\BCC61"; this would need to be adjust to match your installation folder.

I have been trying bcc32 a few times a year for over a decade; I find setting up the cfg files is faster than configuring all the settings in Code::Blocks. Both methods work.

Note, I am usually doing very simple Borland coding projects.

Tim S.

bcc32.cfg
Code: [Select]
-I"D:\GreenApps\BCC61\include\";"D:\GreenApps\BCC61\include\vcl\";"D:\GreenApps\BCC61\include\dinkumware\";"D:\GreenApps\BCC61\include\Indy10\"
-L"D:\GreenApps\BCC61\lib\";"D:\GreenApps\BCC61\lib\obj\";"D:\GreenApps\BCC61\lib\release\";"D:\GreenApps\BCC61\lib\PSDK\";"D:\GreenApps\BCC61\lib\Indy10\"

ilink32.cfg
Code: [Select]
-L"D:\GreenApps\BCC61\lib\";"D:\GreenApps\BCC61\lib\obj\";"D:\GreenApps\BCC61\lib\release\";"D:\GreenApps\BCC61\lib\Indy10\";"D:\GreenApps\BCC61\Lib\PSDK"
Title: Re: Getting Borland C++ compiler to work on CB
Post by: Kargbo on May 02, 2014, 10:29:05 pm
I just started with Code::Blocks and run in de same problem.
I 've concluded the following:

In the Menu: Settings. Compiler. Global compiler settings. Linker settings: in the colom Link Libraries,
1) I had to fill in all the (paths) to the individual libs.
2) The order matters i.e. first the files in ..\BC55\Lib\PSDK\ .. and after that de files in ..\BC55\Lib\.. ( the paths to the directories doesn't work!) .  ::)

Thats how I solved the problem.