Building samples with Microsoft® Visual Studio®
For building samples from the release archive of a specific configuration,
the proper version of Visual Studio must be used.
To build sample application code, follow the steps below:
- Unpack the downloaded archive. After unpacking, the root folder will contain the following subfolders in addition to TD and TG source code folders:
- exe — Contains .exe, .dll, .tx files.
- lib — Contains .lib files.
- Platforms — Contains solutions, projects, intermediate build files.
These folders have subfolders for different configurations. For example, if you unpack Kernel_vc10dll.zip, there will be vc10dll subfolders. If you unpack Kernel_vc10dlldbg.zip, vc10dlldbg subfolders will appear.
- Go to Platforms\<configuration name> and open the solution for samples.
- Build the solution.
- Find compiled .exe files in the exe\<configuration name> folder.
For example, to build the samples for MSVC 2010, DLL configuration:
- Unpack Kernel_vc10dll.zip.
- Open the solution Platforms\vc10dll\Kernel_vc10dll_ex.sln.
- Build the solution.
- Executables are in the exe\vc10dll folder.
Notes:
- Some samples use the DirectX rendering device, the building of which requires
DirectX 9 SDK. It can be downloaded from Microsoft
download center. After downloading and installing this SDK, a DXSDK_DIR
environment variable needs to be created and set to the full path of the dxsdk-9.0
directory.
- Some projects in the solution depend on others. If you open an individual
project (.vcproj) outside of the solution (.sln), its build may fail.
Using multiple configurations
It's acceptable to unpack different Windows archives into the same folder. This is convenient, for example, to build Release and Debug configurations using the same sources or even to have dynamically and statically linked configurations. Unpacking other archives to the same folder will cause warnings because some files are duplicated in both archives. This is okay; duplicate files are the same.
Note: Always use empty folders for upgrading Kernel versions. Mixing files from different Kernel versions may cause problems.
Building samples with Borland Builder 2010
For building sample applications, the CMake tool is provided.
To build sample application code with Borland Builder 2010, follow the steps below:
- Unpack the downloaded archive of the specific configuration (bb2010wm, bb2010wmdbg, bb2010wr, or bb2010wrdbg).
- Run the configure.bat file from the root folder.
- Be sure the Platforms folder is created in the root folder.
- To build all the samples, run 'make' in the root folder. For any particular example, go to the sample source code folder under Platforms where makefile is placed, e.g. Platforms\bb2010wm\Kernel\Examples\Ex_Alloc\ and run 'make' there. Or go to the \Platforms folder and run
make <ExampleName>
, for example:
make Ex_Alloc
- Find compiled .exe files in the exe\<configuration> folder and .lib files in the lib\<target> folder.
See also
Compiling Sample Applications
Compiling Sample Applications on Non-Windows Platforms
Building Applications
Copyright © 2002 – 2020. Open Design Alliance. All rights reserved.
|
|