Borland C++Builder

No Screenshot

Submit Screenshot
This is the free command line C++ compiler from Borland.

Application Details:

Version: 5.5.1
Votes: 0
Latest Rating: Platinum
Latest Wine Version Tested: 1.0.0

Maintainers: About Maintainership

No maintainers. Volunteer today!

Test Results

Old test results
The test results you have selected are very old and may not represent the current state of Wine.
Selected Test Results

What works

Compilation and linking, invoked through jam build system
Wrote a hello.cpp, invoked make.exe to compile and link together.

What does not

only message:

fixme:ntdll:RtlNtStatusToDosErrorNoTeb no mapping for 8000000a

seems to have no impact


What was not tested

I didn't test the installer, I'd installed it early last year.

Hardware tested


  • GPU:
  • Driver:

Additional Comments

compiler is old and sometimes can't handle some templates properly. The price is right and it works!

selected in Test Results table below
Operating systemTest dateWine versionInstalls?Runs?Used
ShowGentoo Linux x86_64Jun 18 20081.0.0Yes Yes Platinuman anonymous user 
CurrentGentoo Linux x86_64Mar 29 20080.9.58.N/A Yes Platinuman anonymous user 
ShowFedora 7Sep 27 20070.9.44.Yes Yes Goldan anonymous user 

Known Bugs

Bug # Description Status Resolution Other apps affected
13955 owner-drawn combobox height different to windows NEW View

Show all bugs

HowTo / Notes

by Luke Stedman (­September 27th 2007)

­---- Download ----
Borland C++ Builder can be downloaded at:

Borland C++ Builder information:

---- Installation ----
[ xxx@xxx tmp]$ wine freecommandLinetools.exe

You will get a few warnings/errors...

wine: creating configuration directory '/home/xxx/.wine'...
Xlib: extension "XFree86-DRI" missing on display ":0.0".
Xlib: extension "XFree86-DRI" missing on display ":0.0".
Xlib: extension "XFree86-DRI" missing on display ":0.0".
fixme:richedit:RichEditWndProc_common WM_STYLECHANGING: stub
fixme:richedit:RichEditWndProc_common WM_STYLECHANGED: stub
fixme:richedit:RichEditWndProc_common WM_STYLECHANGING: stub
fixme:richedit:RichEditWndProc_common WM_STYLECHANGED: stub

---- Post Installation ----
You need to create .cfg files in the Bin directory of the installation, the paths need to be in "Windows" format...

Create bcc32.cfg file in Bin directory containing:

Create ilink32.cfg file in Bin directory containing:

---- Usage ----

You can now compile and link binaries in two possible ways:

1. Compile from Bin directory
When compiled in the Bin directory using bcc32.exe the binary will compile and link without issue, the output will be in the Bin directory.

2. Compile and Link separately
You can compile the source file into a obj file using bcc32.exe and then link using ilink32.exe separately from any directory.


Use of makefiles
by Taiko on Sunday February 22nd 2009, 14:05
If you expand the Environment variable "path" like in the description on top of this article its even possible to use custom makefile.
For example create a file named "makefile" and type in the following text.

include = C:\Programme\Borland\BCC55\Include
lib = C:\Programme\Borland\BCC55\Lib
CPP = bcc32

helloworld.exe: helloworld.obj
$(CPP) -I$(include) -L$(lib) helloworld.obj -o$@

$(CPP) -I$(include) -L$(lib) -c $<

I tested it with the "wine cmd.exe" command line.
You can now compile a c++ file "helloworld.cpp" by simplify typing in "make" (without quotes).


Comments Disabled

Comments for this application have been disabled because there are no maintainers.