Frameworks

alpha version, October 2000

The standard Epoc SDK way of storing the needed resources is particularly cumbersome: you must know where all the headers are (to be able to properly prepare the MMP file), you must even know which particular libraries to link (that should definitely be done by the SDK automatically!), and besides, there is no reasonable way to distinguish different sets of libraries/headers etc.: there is a mighty good mess in the appropriate folders (like the /epoc32/release/marm/rel one).

That's why the XSdk uses frameworks. A framework is a bundle (in fact, a dictionary somewhere in the file system, with the ".framework" extension), which contains all the relevant things: the headers, the interface LIBs, the dynamically linked DLLs with the real functionality, and even other resources whenever approriate (for example, there might be some standard toolbar icons, shared with all applications which use a particular framework).

<<<complete documentation forthcoming>>>

currently supported inside the framework:

.../Headers	this folder is automatically added to the include search list
.../Resources/<target>	any files in this folder are presumed to be accessible to the generated project (currently, this is used for the framework DLLs, and they are placed to the `/System/Libs`)
.../<target>/<fwk.name>.lib	this interface library is automatically linked in

where <target> is the target name (only "marm" currently), and the <fwk.name> is the name of the framework folder without the extension.