WineHQ
Borland C++Builder 5.5.1



Category: Main > Programming / Software Engineering > Borland C++Builder > 5.5.1


NameBorland C++Builder
Version5.5.1
License  
URLhttp://www.borland.com/cbuilde...
Votes  
RatingPlatinum
Wine Version1.0.0
Maintainers of this version:
No maintainers. Volunteer today!
Description
This is the free command line C++ compiler from Borland.
Old test results
The test results you have selected are very old and may not represent the current state of Wine.
Selected Test Results (selected in 'Test Results' table below)

What works

Installation.

Compilation to an .obj file from any directory.

Linking of .obj files from any directory.

Combined Compiling and Linking in the Bin directory only.  


What does not

Combined Compiling and Linking in any directory.


What was not tested
All other functionality.


Additional Comments

Manual creation of .cfg files also required.
Test Results
DistributionTest dateWine versionInstalls?Runs?RatingSubmitter
ShowGentoo Linux AMD64Jun 18 20081.0.0 Yes Yes Platinum an anonymous user 
ShowGentoo Linux AMD64Mar 29 20080.9.58. N/A Yes Platinum an anonymous user 
CurrentFedora 7Sep 27 20070.9.44. Yes Yes Gold an anonymous user 


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

 
HOWTO
by Luke Stedman (­September 27th 2007)

­---- Download ----
Borland C++ Builder can be downloaded at:
www.codegear.com/products/cppbuilder

Borland C++ Builder information:
dn.codegear.com/article/20633

---- 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:
-I"C:\Borland\BCC55\Include"
-L"C:\Borland\BCC55\Lib"

Create ilink32.cfg file in Bin directory containing:
-L"C:\Borland\BCC55\Lib"

---- 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.obj:
$(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).


 




   << Back

Page loaded in 0.09001 seconds.