[mbackup-devel] sourcecode layout

[James O'K. <jo...@mi...>]

ftp://mbackup.sourceforge.net/pub/mbackup/mbackup-newlayout.tar.gz

That tarball is my proposed source layout.

/base
	This directory will contain the very core of the suite. main()
will be in here.

/communicators
	This is for modules whose job it is to contact other processes,
other than mbackup


/controllers


/docs
	Documentation.

/filters
	The modules that do the actual work on data.

/include
	header files (* see note below)

/lib
	library files

/readers
	Modules that read from media

/tests
	Regression tests

/writers
	Modules that write to media



* In the /include directory, I've thrown together an example of my ideas
for how cross-platorm issues will be handled. In general code, I would
like everything to make calls to mb_foo() where foo is a standard C
function. So we would call mb_open() to open a file. For posix, it's easy,
mb_open() is just a #define for open(). On other systems, it would be a
wrapper function.


Could I have some comments from people who have done large projects or
people who have done cross platform work before?

-james