To build XML4C from it source (using MSVC), you will need to open the workspace containing the project. If you are building your application, you may want to add the XML4C project inside your applications's workspace.

The workspace containing the XML4C project file and all other samples is:

	xml4c-src-3_5_1\Projects\Win32\VC6\xerces-all\xerces-all.dsw

Once you are inside MSVC, you need to build the project marked XercesLib.

If you want to include the XML4C project separately, you need to pick up:

	xml4c-src-3_5_1\Projects\Win32\VC6\xerces-all\XercesLib\XercesLib.dsp

You must make sure that you are linking your application with the xerces-c_1.lib library and also make sure that the associated DLL is somewhere in your path.

If you are working on the AlphaWorks version which uses ICU, you must have the ICU data DLL named icudata.dll available from your path setting. For finding out where you can get ICU from and build it, look at the How to Build ICU.

Inside the same workspace (xerces-all.dsw), you'll find several other projects. These are for the samples. Select all the samples and right click on the selection. Then choose "Build (selection only)" to build all the samples in one shot.

Requirements:

• VisualAge C++ Version 4.0 with Fixpak 1:
  Download the Fixpak from the IBM VisualAge C++ Corrective Services web page.

To include the ICU library:

• ICU Build:
  You should have the ICU Library in the same directory as the XML4C library. For example if XML4C is at the top level of the d drive, put the ICU library at the top level of d e.g. d:/xml4c-3_5_1 d:/icu.

Instructions:

1. Change the directory to d:\xml4c-3_5_1\Projects\Win32
2. If a d:\xml4c-3_5_1\Project\Win32\VACPP40 directory does not exist, create it.
3. Copy the IBM VisualAge project file, XML4C2X.icc, to the VACPP40 directory.
4. From the VisualAge main menu enter the project file name and path.
5. When the build finishes the status bar displays this message: Last Compile completed Successfully with warnings on date.

These instructions assume that you install in drive d:\. Replace d with the appropriate drive letter.

Before doing the build, you must first set your environment variables to pick-up the compiler and also specify where you extracted XML4C on your machine. While the first one is probably set for you by the system administrator, just make sure you can invoke the compiler. You may do so by typing the compiler invocation command without any parameters (e.g. xlc_r, or g++, or cc) and check if you get a proper response back.

Next set your XML4C root path as follows:

	export XERCESCROOT=<full path to xml4c-src-3_5_1>

This should be the full path of the directory where you extracted XML4C.

As mentioned earlier, you must be ready with the GNU tools like autoconf and gmake before you attempt the build.

The autoconf tool is required on only one platform and produces a set of portable scripts (configure) that you can run on all other platforms without actually having the autoconf tool installed everywhere. In all probability the autoconf-generated script (called configure) is already in your src directory. If not, type:

	cd $XERCESCROOT/src autoconf

This generates a shell-script called configure. It is tempting to run this script directly as is normally the case, but wait a minute. If you are using the default compilers like gcc and g++ you do not have a problem. But if you are not on the standard GNU compilers, you need to export a few more environment variables before you can invoke configure.

Rather than make you to figure out what strange environment variables you need to use, we have provided you with a wrapper script that does the job for you. All you need to tell the script is what your compiler is, and what options you are going to use inside your build, and the script does everything for you. Here is what the script takes as input:

	runConfigure runConfigure: Helper script to run "configure" for one of the supported platforms. Usage: runConfigure "options" where options may be any of the following: -p <platform> (accepts 'aix', 'linux', 'solaris', 'hp-10', 'hp-11', 'irix', 'unixware') -c <C compiler name> (e.g. xlc_r, gcc, cc) -x <C++ compiler name> (e.g. xlC_r, g++, CC, aCC) -d (specifies that you want to build debug version) -m <message loader> can be 'inmem', 'icu', 'iconv' -n <net accessor> can be 'fileonly', 'libwww' -t <transcoder> can be 'icu' or 'native' -r <thread option> can be 'pthread' or 'dce' (only used on HP-11) -l <extra linker options> -z <extra compiler options> -h (to get help on the above commands)

XML4C can be built as either a standalone library or as a library dependent on International Components for Unicode (ICU). For simplicity, the following discussion only explains standalone builds.

One of the common ways to build XML4C is as follows:

	runConfigure -plinux -cgcc -xg++ -minmem -nfileonly -tnative

The response will be something like this:

	Generating makefiles with the following options ... Platform: linux C Compiler: gcc C++ Compiler: g++ Extra compile options: Extra link options: Message Loader: inmem Net Accessor: fileonly Transcoder: native Thread option: Debug is OFF creating cache ./config.cache checking for gcc... gcc checking whether the C compiler (gcc -O -DXML_USE_NATIVE_TRANSCODER -DXML_USE_INMEM_MESSAGELOADER ) works... yes checking whether the C compiler (gcc -O -DXML_USE_NATIVE_TRANSCODER -DXML_USE_INMEM_MESSAGELOADER ) is a cross-compiler... no checking whether we are using GNU C... yes checking whether gcc accepts -g... yes checking for c++... g++ checking whether the C++ compiler (g++ -O -DXML_USE_NATIVE_TRANSCODER -DXML_USE_INMEM_MESSAGELOADER ) works... yes checking whether the C++ compiler (g++ -O -DXML_USE_NATIVE_TRANSCODER -DXML_USE_INMEM_MESSAGELOADER ) is a cross-compiler... no checking whether we are using GNU C++... yes checking whether g++ accepts -g... yes checking for a BSD compatible install... /usr/bin/install -c checking for autoconf... autoconf checking for floor in -lm... yes checking how to run the C preprocessor... gcc -E checking for ANSI C header files... yes checking for XMLByte... no checking host system type... i686-pc-linux-gnu updating cache ./config.cache creating ./config.status creating Makefile creating util/Makefile creating util/Transcoders/ICU/Makefile creating util/Transcoders/Iconv/Makefile creating util/Transcoders/Iconv390/Makefile creating util/Transcoders/Iconv400/Makefile creating util/Platforms/Makefile creating util/Compilers/Makefile creating util/MsgLoaders/InMemory/Makefile creating util/MsgLoaders/ICU/Makefile creating util/MsgLoaders/MsgCatalog/Makefile creating util/MsgLoaders/MsgFile/Makefile creating validators/DTD/Makefile creating framework/Makefile creating dom/Makefile creating parsers/Makefile creating internal/Makefile creating sax/Makefile creating ../obj/Makefile creating conf.h cat: ./conf.h.in: No such file or directory conf.h is unchanged Having build problems? Read instructions at http://xml.apache.org/xerces-c/build.html Still cannot resolve it? Find out if someone else had the same problem before. Check the mailing list archives at http://archive.covalent.net. In future, you may also directly type the following commands to create the Makefiles. export TRANSCODER=NATIVE export MESSAGELOADER=INMEM export USELIBWWW=0 export CC=gcc export CXX=g++ export CXXFLAGS=-O -DXML_USE_NATIVE_TRANSCODER -DXML_USE_INMEM_MESSAGELOADER export CFLAGS=-O -DXML_USE_NATIVE_TRANSCODER -DXML_USE_INMEM_MESSAGELOADER export LIBS= -lpthread configure If the result of the above commands look OK to you, go to the directory XERCESCROOT and type "gmake" to make the XML4C system.

The error message concerning conf.h is NOT an indication of a problem. This code has been inserted to make it work on AS/400, but it gives this message which appears to be an error. The problem will be fixed in future.

So now you see what the wrapper script has actually been doing! It has invoked configure to create the Makefiles in the individual sub-directories, but in addition to that, it has set a few environment variables to correctly configure your compiler and compiler flags too.

Now that the Makefiles are all created, you are ready to do the actual build.

	gmake

Is that it? Yes, that's all you need to build XML4C.

Similarly, you can build the samples by giving the same commands in the samples directory.

	cd $XERCESCROOT/samples runConfigure -plinux -cgcc -xg++ gmake

The samples get built in the bin directory. Before you run the samples, you must make sure that your library path is set to pick up libraries from $XERCESCROOT/lib. If not, type the following to set your library path properly.

	export LD_LIBRARY_PATH=$XERCESCROOT/lib:$LD_LIBRARY_PATH

You are now set to run the sample applications.