home *** CD-ROM | disk | FTP | other *** search
- =========================================================================
- BUILD AND RUN INSTRUCTIONS FOR THE WorkFrame ENVIRONMENT:
-
- To build the sample, click the "Build normal" button on the project's
- toolbar or from the Project pulldown, select "Build normal"
-
- To execute the sample, click the "Run" button on the project's toolbar.
-
- NOTE:
- Data Access Builder Samples: the above Build and Run methods
- do not apply to these samples. Please see the README.TXT file
- associated with each of the Data Access Builder samples for
- detailed information on building and running these samples.
-
- SOM Samples: the above Build and Run methods do not apply to
- these samples. Please see the README.TXT file associated with
- each of the SOM samples for detailed information on building
- and running these samples.
-
- Visual Builder Samples: the above Build method does apply to
- the Visual Builder samples. Please see the README.TXT file
- associated with each of the Visual Builder samples for detailed
- information on building these samples.
-
- All Samples: Because all samples are enabled for Performance
- Analyzer, CPPWPA3.DLL must be present to Run a sample
- and CPPWPA3.OBJ must be present to Build a sample without errors.
- These objects are automatically installed if you installed the
- Performance Analyzer component. Otherwise, copy the CPPWPA3.DLL
- from the \BIN directory and the CPPWPA3.OBJ from the \LIB directory
- of the CD-ROM to the corresponding directories on your system.
-
- Copying CPPWPA3.DLL and CPPWPA3.OBJ simply allows you
- to invoke Run and Build on the samples without errors. To actually
- use the Performance Analyzer, or any other component, with a sample
- you must have installed these components.
-
- IF YOU DIDN'T CHOOSE THE 'TYPICAL INSTALL' OPTION:
-
- If you chose a CD-ROM install, a MINIMAL install, or a CUSTOM install
- which left the Samples and Documentation component on the source drive,
- the %REPLACEDIR% portion of the samples path in the WorkFrame project
- will not have been updated.
-
- To RUN or BUILD a particular sample under the above install options,
- you must
-
- - copy the files from the source directory on the server or
- CD-ROM to a directory on your hard drive.
-
- It is recommended you create the same subdirectories for the
- samples as they appear on the CD-ROM then copy each set of samples
- files into their respective sub-directory.
-
- - set the path for the sample's WorkFrame project.
-
- From the Guide to Samples notebook, select the sample of interest then
- choose the Open Project View button. The Project View will open but
- no files will be displayed. To set the path to the files copied in
- the previous step, choose VIEW -> SETTINGS -> DIRECTORIES. Substitute
- the correct path segment for the %REPLACEDIR% variable to complete the
- path specification in the 'Source directories for project files'
- listbox. Change the path displayed in the 'Working Directory' list box
- to match that of the Source Directory list box. Finally, select the
- OK button to complete the update.
-
- Your sample project is now locally installed and accessible for building
- and running.
-
- ADDITIONAL INFORMATION:
-
- For additional information on a particular VisualAge for C++ sample
- (including how to build and run the sample from the command line),
- please view the readme file for that sample.
-
- From the Guide to Samples notebook
- - Select the Component (choose ALL for a list of all samples)
- - then, select the sample from the sample list
- - finally, select the View Readme button to open the readme file
- for that sample
-
-
- RUNNING SAMPLES IN Win32s:
-
- Many of the samples can be built to run in Win32s. However, since most
- use COUT, and since a text window is not a default in Win32s like it
- is in WindowsNT and Windows95, you won't see the output. A solution
- to this is:
-
- - Redirect the output of the sample to a file by linking the sample
- with redirect.obj.
-
- icc -b-noe sample.c redirect.obj
-
- - Run the sample from within File Manager, using Run in the File
- menu and redirect output to a file.
-
- Redirect.obj is shipped with VisualAge for C++ for Windows in the
- LIB directory. The code inside of redirect.obj is skipped when NOT
- executing in a Win32s environment, so one binary for all Windows
- platforms is sufficient.
-
- Profiler support is not available on Win32s, so either do not build
- samples using -Gh option, or make cppwpa3.dll available on your
- Win32s machine.
-
- There are some restrictions. The file handles are not inherited by
- child processes. Redirect.obj does not work with the subsystem library.
-
- Under Win32s, there are further restrictions if you are creating shared
- DLLs or your own custom DLL initterm function. See the Programming
- Guide for more information.
-
- SAMPLES WHICH CANNOT BE BUILT TO RUN IN WIN32S
-
- The following are the samples which are shipped with VisualAge for C++ for
- Windows which cannot be built to run with Win32s.
-
- Compiler
- --------
- MultiThread Hello World (Sample02)
- Thread Local Storage (TLS)
- Direct-To-SOM (DTS)
- Subsystem DLL (Sample05)
-
- Database
- --------
- SOM Stock (StockSOM)
-
- Editor
- ------
- LPEX (LXMIN2)
-
- Visual Builder
- --------------
- All Samples
-
- SOM
- ---
- All Samples
-
- IOC
- ---
- Basic Server (ACDF1)
- Advanced Server (ACDF2)
- Basic Container (ACDF3)
- Advanced Container (ACDF4)
- Collection Streaming (ACDF5)
- Compound Document Hello5 (ACDF6)
-