Rogue Wave banner
Previous fileTop of DocumentContentsNext file

4.5 Compiling in Windows with Borland

This section describes how to use Borland's C++ compilers to compile programs that use Rogue Wave's LAPACK.h++ class library.

4.5.1 Using a Static Version of LAPACK.h++ (Borland)

These instructions assume that the Borland include files and libraries are in the locations specified by the file bcc32.cfg for 32-bit compiles. If not, you will have to specify -I and -L flags as well, or change your configuration file. (See the Borland User's Guide for instructions.)

Let's say that we have a file named myapp.cpp and that we are compiling it in a Windows NT MS-DOS command prompt. Let's also say that the LAPACK.h++ and Math.h++ header file include path is

and that we have built a static, single-threaded, no debug version of LAPACK.h++ named lpk0s.lib. Then we can compile myapp.cpp with the Borland C++ compiler with the following command (all on one line):

The entire command line must be typed without carriage returns. Your operating system might have a line length limit. If your command line gets too long, use a response file.

The command above will compile and link in one step.

4.5.2 Using a Dynamic Version of LAPACK.h++ (Borland)

At this release, LAPACK.h++ cannot be built as a DLL using Borland C++ under Windows 95 and Windows NT.

4.5.3 Compiling from the Borland C++ IDE

When using the Borland C++ IDE, you must define the Rogue Wave include path, for example, <rw_root>\workspaces\WINNT4\BORLANDC++_Builder_30\0s, to every project. Use menu selection Options | Project | Directories.

You should also add the appropriate LAPACK.h++ library to your Project Window. See the Borland User's Guide for instructions.


Previous fileTop of DocumentContentsNext file

©Copyright 1999, Rogue Wave Software, Inc.
Contact Rogue Wave about documentation or support issues.