Borland C targeted the professional application development market, while Turbo C targeted the home and hobbyist market. Borland C included additional tools, compiler code-optimization, and documentation to address the needs of commercial developers. In 1997 Borland C was replaced with Borland C Builder. Borland C Builder 5.0 Professional for PC & Mac, Windows, OSX, and Linux. CBuilder 5 Professional combines the C Windows development environment for building desktop and database applications with native Internet components for building high-throughput Web applications. Originally released in 1985 by USA independent publisher Ansa Software in 1985, it was taken over by Borland in 1987, who went on to port it to OS/2. A version for the Mac was not shipped. The Reflex flat file database that on DOS was a budget software with limited programming abilities, existed in a version for the Mac was already quite an.

Next:Quick Start: Example OOMMF Download

Up:Installation Previous:Advanced Installation
Subsections

Unix Configuration
Microsoft Windows Options
Mac OS X Configuration

Platform Specific Installation Issues

The installation procedure discussed in the previous sections applies toall platforms (Unix, Windows, Mac OS X). There are, however, somedetails which pertain only to a particular platform. These issues arediscussed below.

Unix Configuration

Missing Tcl/Tk files

The basic installation procedure should be sufficient to install OOMMF on most Unix systems. Sometimes, however, the build will fail due tomissing Tcl header files (tcl.h, tk.h) or libraries (e.g.,libtcl.so, libtk.so). This problem can usually be solved byinstalling a ``development' version of Tcl/Tk, which may be found onthe operating system installation disks, or may be available from thesystem vender. There are also binary releases of Tcl/Tk for a numberof systems available from ActiveState, under the nameActiveTcl.Alternatively, one may download the sources for Tcl and Tk from theTcl DeveloperXchange, and build and install Tcl/Tk from source. The Tcl/Tk build follows the usual Unix configure, make, make install build convention.

Compiler Optimization Options

On most systems, OOMMF builds by default with relatively unaggressivecompiler optimization options. As discussed earlier(under Optimization), you may edit the appropriateoommf/config/platforms/ file to change the default compilation options.However, on some common systems (e.g., Linux, some BSD variants) OOMMF will try to deduce the hardware architecture (i.e., the CPU subtype,such as Pentium 3 vs. Pentium 4) and apply architecture-specific optionsto the compile commands. This is probably what you want if OOMMF isto be run only on the system on which it was built, or if it is run on ahomogeneous cluster. If, instead, you intend to run OOMMF on aheterogeneous cluster you may need to restrict the compiler options tothose supported across your target machines. In that case, open theappropriate configuration file in the oommf/config/platforms/directory, and look for the linesUncomment either the ``unset cpuopts' line to make a generic build, orelse edit the ``set cpuopts' line to an appropriate common-denominatorarchitecture and uncomment that line.

In a similar vein, some compilers support a ``-fast' switch, whichusually creates an architecture-specific executable. The sameconsiderations apply in this case.

An advanced alternative would be to define separate OOMMF ``platforms' for each CPU subtype in your cluster. At a minimum, thiswould involve creating separate platform name files inoommf/config/names/ for each subtype, and then making copies of theappropriate oommf/config/platforms file for each new platform. Theplatform name files would have to be written so as to reliably detectthe CPU subtype on each machine. See ``Managing OOMMF platform names' for details on creating platform namefiles.

Microsoft Windows Options

This section lists installation options for Microsoft Windows.

Using Microsoft Visual C++

If you are building OOMMF software from source using the MicrosoftVisual C++ command line compiler, cl.exe, it is necessary to runvcvars32.bat to set up the path and some environment variables.This file is distributed as part of Visual C++. You may want to set upyour system so this batch file gets run automatically when you boot thesystem, or open a command prompt. See your compiler and systemdocumentation for details.

Using the Cygwin toolkit

The CygwinProjectis a free port of the GNUdevelopment environment to Windows, which includes the GNU C++ compilerg++. OOMMF has been successfully built andtested within the Cygwin environment; sample configuration filesconfig/names/cygtel.tcl andconfig/platforms/cygtel.tcl areincluded in the OOMMF distribution.

Borland C For Mac Os High Sierra

IMPORTANT: Use astandard Windows build of Tcl/Tk (e.g., theActiveTclrelease) whenconfiguring, building, and launching OOMMF software. As of thiswriting (Oct. 2004), the tclsh distributed with Cygwin (i.e.,/usr/bin/tclsh) has problems involving sockets that make itunsuitable for use with OOMMF. Unfortunately, standard Windows versions of Tcl are not acquainted with the Cygwin POSIX-stylepathnames, so in many cases you will have to use Windows-style pathnamesinstead.

Note that OOMMF software determines whether it is running under Cygwinby examining the environment variablesOSTYPE andTERM. If either is set to a valuebeginning with cygwin, the Cygwin environment is assumed. If youare using the Cygwin environment with different values for both OSTYPEand TERM, you will have to modify the config/names/cygtel.tcl fileaccordingly.

Using Borland C++

OOMMF has been successfully built and tested using theBorland C++ command line compiler version 5.5.However, a couple preparatory steps are necessary before buildingOOMMF with this compiler.

Properly complete bcc55 compiler installation.
Be sure to read the readme.txt file in the BCC55subdirectory of the Borland install directory. In particular, checkthat the bcc32.cfg and ilink32.cfg configuration files existin the BIN subdirectory, and have appropriate contents. If youomit this step you will get error messages during the OOMMF buildprocess relating to the inability of the Borland compiler to findsystem header files and libraries. You will probably also need to addthe Borland BIN directory to your PATH environment variable.Some of the Borland tools are fragile with respect to spaces in theirpathnames, so you should either select the Borland install directoryto be one without spaces anywhere in the pathname (e.g., useC:Borland instead of'C:Program FilesBorland'), or at least when settingthe PATH use the ``8dot3' style short name version of eachcomponent of the Borland install directory, e.g.,Use ``dir /x' to display both the short and long versions offilenames. The Borland Developer Studio 2006 install automatically setsthe path to include the long name version of the Borland BINdirectory; you should manually change this via the System dialog boxfrom the Control Panel. Select the Advanced tab, and pull up theEnvironment Variables sub-dialog. Edit the Path variable asdiscussed above; check both the ``User variables' and the ``Systemvariables' settings. You will need to launch a new shell (commandprompt) for the changes to take effect.
Create Borland compatible Tcl and Tk libraries.
The import libraries distributed with Tcl/Tk, release 8.0.3 and later,are not compatible with the Borland C++ linker. However, the commandline utility coff2omf, which is distributed withthe Borland compiler, can be used to create suitable libraries fromthe Tcl/Tk .lib's. In the Tcl/Tk library directory (typicallyC:Tcllib or 'C:Program FilesTcllib'),issue the following commandsHere tcl84.lib and tk84.lib are the input libraries (in COFFformat) and tcl84bc.lib and tk84bc.lib are the new libraries(in OMF format).
If coff2omf doesn't work, you can try creat