Linux/Unix 
*Installing from source*

Unpack the archive and give the following commands 
./configure --help
./configure --prefix=%{prefix} [other options] 
make 
make install 

This will compile all the targets excluding examples. If you want to
compile the examples use the --enable-examples option with configure.

Normally ,g++ does optimization of c++ code and it becomes impossible to
debug.If you wish to debug then do --disable-opt with configure.

For logging related code to be present add --with-log with configure.

To write a web service client using wsdlpull make sure to add the
$(prefix)/include in your include path and add $(prefix)/libs and -lwsdl
-lschema -lxmlpull to your LDFLAGS .

*Installing from rpms*

As of now there are rpms for Fedora core 3. However if you want to use
wsdlpull to develop web service clients you need to install from source
until there is a developer rpm.

----------------------------------------------------------
Windows

Win32 users can find MSVC++ project files in the win32 directory.
Open wsdlpull.dsw in MSVC++ and do a clean build. 

For logging related code to be present add LOGGING in the preprocessor defines of 
the MSVC++ project 

Since the soap.xsd schema is required for parsing wsdl documents with
soap binding elements (which means almost all wsdl documents) you need
to adjust the relative path so that the parser can locate the soap
binding schema. Soap.cpp file has the path to the soap schema. Hence for
win32 platforms executables for the wsdl tool is generated in the
wsdlpull root directory,and has the path to the soap.xsd schema
hardcoded relative to the wsdlpull root directory.So be wary before you
move try to execute this from another location,because you would have
to change some code to make it work from other locations. 

Some older compilers may give errors with the << operator on Qname.If this is
the case then change those statments to use the << on Qname::getLocalName().


