Installation, Workspace Architecture.

The Workspace Directory Architecture A simple archive extraction is enough to install the whole package, for all systems. All sources for AzurVeda 's base library and the Libraries that extends their objects stand at the base of a Workspace directory under a VedaLibXXXX directory, where XXXX is the specific name of the package. Sources for the Libraries that extends VirtualMachine are in the same directory, under a VedaMachineXXXX name, where XXXX explicits the target machine or API used to code it. Other Applications can perfectly choose to create a completly AzurVeda-dependant project, in the same base directory, with any name. Compilation Projects Are relatives to Machines. Like a Machine directory exists for each compilable target machine, the same directory is used to manage each Compilation projects for this machine, and as base for binary outputs for these projects. It means, each linux .o, .lib or binaries, will be found under VedaMachineLinux in subdirectories, the linux target directory. This way, The Library directories are left untouch. To launch the compilation of projects for a given machine, you usually need to type "make" in your favorite machine directory !

"Makefile includes."

As each platform will use a different compiler or cross compilers, and different makefiles, a makefile include, "Makefile.i" should be found in each Library source directory. This include explicits variables for the .o object list to create in this lib, for the lib name, and for the dependancies to other neighbour packages. Then this include file can be used by makefiles in the Machine Directories. This way,you just got to touch one file to manage each compilation project for each Machines.

"Notes about project management."

• The shape or project format of a project into a given machine is totally free! You can use the tool you want in the context of a machine, but this shall not affect the other Libs and Machines! And don't forget having a "cleaning" function is always useful!
• There should be no need for Environment variables in AzurVeda, all dependances to neighbour libraries can be done with relative paths. Once the Libraries are compiled, you may want to use them in an external project. We suggest you should copy your libs in your lib compiler directory, and refer each projects headers with the -I include directory option.

---

      /\/\        4         N         k         !         N         D
                      _______  _ __ ___  _____            ___ _ _  ____
     ___________  __//___   /________  |/    / ___________\_______/    \
    /   _   _   \/   _     /    _   /      _/_/____/    _       __     /
   /    /   /       /     /    /    \      \/     /    /    \   \     /
  \\___/___/___/    ¯    _____/_____/       ______\___/_____/\________\\
               \________/_ ___ __ l____\      /elD!  
                 http://www.m4nkind.com \____/