[XPS-devel] Basic Development Framework Committed

[Reid S. <re...@re...>]

*This message was transferred with a trial version of CommuniGate(tm) Pro*
I have checked into CVS a basic development framework for the XPS
project. I'm preparing a series of "Developer's Guidelines" documents to
help you find your way around. Until then, I suggest you just check out
the software and browse. Its pretty straight forward stuff. Here's a
quick overview:

1. Use CVS to check out the entire set of sources to your local machine
(Linux or cygwin at this point)
2. run the "bootstrap.sh" script that is at the top level. This should
successfully configure your source tree for your platform (let me know
if you have problems)
3. All the goodies are in the "src" directory. The "xps" link that
configure creates is so that we can #include <xps/module/header.h>
instead of <src/module/header.h>.  This is preferred because we want to
ensure that our software doesn't conflict with any 3rd party software
(of which we'll be using a lot).
4. The directories under "src" contain the following:
	doc -- all documentation, guides, howtos, web site, papers, etc.
	mem -- the memory management module (incomplete, still working on it)
	obj -- the XVM runtime object management module (TBD)
	schema -- the XPL schemas and examples (moved from xplc/schema)
	test -- a unit testing framework (complete, works)
	util -- various utilites for debugging, etc (complete, works)
	www -- defunct (I'll remove this eventually)
	xplc --  the XPL Compiler (have at it Vic!)
	xplec -- the XPL Extension Compiler (no code yet)
	xvm -- the XVM program (trivial framework committed)
	xvmapi -- the XVM API (basic macros defined)
	xvmsh -- the XVM shell to send commands to XVM (no code yet)
	Configuration.h -- high level #defines
	config.h -- generated by configure, platform config stuff.

I am currently working the xvmapi so that we have a standard "output"
format for the XPL compiler.

It's time to start cutting some code!

Reid.