...
- Go back to the work dir, create a subdir for Xerces-C++, and go into it.
No Format cd $sim_wrk mkdir xercesc cd xercesc
- Download the Xerces tarball.
No Format wget http://www.apache.org/dist/xml/xerces-c/xerces-c-src_2_6_0.tar.gz
- Unzip the tarball.
No Format tar -zxvf xerces-c-src_2_6_0.tar.gz
- Set XERCESCROOT for the build in your environment, only.
No Format export XERCESCROOT=${sim_work}/xerces-c-src_2_6_0 - Go into the Xerces-C++ build area.
No Format cd xerces-c-src_2_6_0/src/xercesc
- Configure the build.
No Format ./runConfigure -pcygwin -cgcc -xg++ \ -minmem -nsocket -tnative -rpthread \ -P `cd ../../..; pwd`
- Build and install it.
No Format make make install
- In setup.sh, set XERCESCROOT to the installation area and add the DLL location to the PATH.
No Format export XERCESCROOT=${sim_work}/xercesc export PATH=$XERCESCROOT/bin:$PATH
| Tip |
|---|
When rebuilding Xerces-C++, which you will probably not need to do once you get it working, XERCESCROOT needs to be set back to the Xerces-C++ source area rather than the installation base. |
GDML
GDML's CVS is not directly accessible from the command line, but a tarball is available through a WWW interface.
...
The above should be sufficient to "bootstrap" any future (re)builds with the following caveats.
...
.
Done!
That's it.
Happy simulating!
...