This file contains instructions for building the XSD/e runtime
library (libxsde) and examples. The XSD/e compiler itself was
pre-built for your host development platform and can be found
in the bin/ directory. The runtime library and examples can be
built using either GNU make (normally on UNIX operating systems)
or Microsoft nmake (on Windows). The following sections describe
each of the two methods.


GNU make
--------

The first step in building the source code with GNU make is to
configure the runtime library by editing the build/config.make
file. There you can specify which toolchain should be used to
compile the source code as well as which optional feature (such
as STL, C++ exceptions, etc.) should be used. Follow the
instructions in the comments in build/config.make and make the
appropriate changes.

To start the compilation process simply execute make (or gmake)
in the root directory. This will build the libxsde.a runtime
library as well as the examples. If you do not want to build
the examples, you can start the compilation process from the
libxsde/ directory.

In order to start using XSD/e in your applications, you will
need add the libxsde/ directory to your include search paths
(-I) and link your executables with the libxsde/xsde/libxsde.a
library.


Microsoft nmake
---------------

This section provides general instructions for building the XSD/e
runtime and examples with nmake. For additional information on
eMbedded Visual C++ 4.0 and Visual Studio 2005 with Smart Devices
support see the corresponding notes after this section.

The first step in building the source code with nmake is to
configure the runtime library by editing the build\config.nmake
file. There you can specify which toolchain should be used to
compile the source code as well as which optional feature (such
as STL, C++ exceptions, etc.) should be used. Follow the
instructions in the comments in build\config.nmake and make the
appropriate changes.

If you are using an IDE (e.g., Visual Studio or eMbedded Visual
C++) to develop your applications, you can copy the compiler
options (such as CPU and Platform preprocessor macros, etc.)
from your project's C++ compiler settings.

The next step is to start a new command prompt and execute
the vcvars32.bat (or equivalent) file that is normally found
in your development environment's installation directory.
After executing vcvars32.bat, you can start the compilation
process by executing

nmake /f nmakefile

from the XSD/e root directory. This will build the xsde.lib
runtime library as well as the examples. If you do not want
to build the examples, you can start the compilation process
from the libxsde\ directory.

In order to start using XSD/e in your applications, you will
need add the libxsde\ directory to your include search paths
and link your executables with the libxsde\xsde\xsde.lib
library.


Notes on eMbedded Visual C++ 4.0
--------------------------------

You can find a sample configuration file for this development
environment in the etc\evc-4.0\ directory.

Instead of one vcvars32.bat file, eMbedded Visual C++ has a set
of such files each for a particular platform and CPU. They can be
found in the EVC\WCEnnn\BIN\ subdirectory in the eMbedded Visual
C++ installation directory. For example, a file for Windows CE
4.0 for ARMv4 CPU is EVC\WCE400\BIN\WCEARMV4.bat. You may want
to review the installation paths in this file to make sure the
reflect your setup. You can also study this file to find out the
name of the C/C++ compiler for this CPU. In case of ARM, it is
clarm.exe.


Notes on Visual Studio 2005 with Smart Devices support
------------------------------------------------------

You can find sample configuration files for this development
environment in the etc\vc-8.0\ directory.

This version of Visual Studio does not provide vcvars32.bat or
equivalent for Smart Devices development. Instead you can use
the vcvarssd.bat file provided in the etc\vc-8.0\ directory.
Modify it according to your setup as instructed by the comments
found in this file.

