When you run OWLCVT it makes a directory called OWLBA K in your, C
Backing up your
current directory It then makes a copy of your original source file and any.
old source files
local headers and places these in the OWLBA K directory WhenC .
OWLCVT has finished converting your files, the modified source files are
in your current directory If, for some reason, the converted files don’t.
function correctly are corrupted, or are otherwise unsatisfactory you can, ,
easily restore your original files by copying them from the OWLBA KC
directory If you run OWLCVT again, and it finds a copy of a file already in.
the OWLBA K directory it leaves the copy that’ already in the directoryC , s
and does not overwrite it.
T convert your code from the command line using OWLCVT follow theseo ,
How to use
steps:
OWLCVT from the
command line
1. Copy the file that contains the compiler options you used for your
ObjectWindows 1.0 compilations, such as your makefile, configuration
file, response file, and so on, to a new file.
2. Make the following changes to the new file:
■ If you haven’t already changed the header-file include paths when
converting to Borland C++ 4.0, change the include path as follows:
● Change C:\BC31\OWL\INCLUDE to C:\BC4\INCLUDE\
OWLCVT (for ObjectWindows 1.0-compatible header files)
● Change C:\BC31\CLASSLIB\INCLUDE to C:\BC4\INCLUDE\
CLASSLIB\OBSOLETE (for Object-based container class header
files)
● Change C:\BC31\INCLUDE to C:\BC4\INCLUDE (for standard
header files)
This assumes the existing paths in your ObjectWindows 1.0-
compatible files use the directory C:\BC31 as the root directory of
your old Borland C++ installation, and that you have installed
Borland C++ 4.0 in the directory C:\BC4. Change these names to
reflect the actual directories in which you have your compilers
installed.
If you use any header files that duplicate the names of Borland header
W rning!a
files, you must place the directory containing these files in your
header file include path before the Borland include directories. Y uo
must do this even if the files are in the current directory and you use
the #include “
filename
.h” syntax to include these files.
■ If you’re using a makefile, batch file, or any type of command script:
Appendix A, Converting ObjectWindows 1.0 code to ObjectWindows 2.0
357
