The normal way of working with Unibase is with the use of a make utility. This is
always present in every ANSI-C compiler. With the sources my makefile is included
and it checks for changes to modules and compile C source and creates object files.
You can alter this files for your own projects in the language but I am planning
on routines within unibase to create a makefile automatically.
Options
There are several compiling options coming for unibase. This can be used to create
separate development and production versions of the same program. These options
can be put in a module so the change of one module name can lead to a total
different C source.
Modules
All the modules are currently compiled every time unibase is called.
This can lead to waiting seconds on a large scale project. It is not very easy
to create different compiled sources to prevend the recompilation of the total
source every time. But I have some ideas and it should be technically possible.
Errors
The program creates several html files. The most import one is the 'errors.html' file.
It contains the errors and warnings of the compiler. Every error is a link to the
point in the sources where the error occurred. These source .html files are copies of the
source but contain additional handy links.
Routine calls link to the documentation of this routine.
Global variables are links to their documentation.
Table, indexes and pointers also are links.
Install application
The makefile should create a cgi and a server application. The cgi should be put
in the correct directory of the web-server. There should be given a correct path in the cgi to the
server and data file directory. Realize that the server can be called by all kind of
people the cgi should have rights to call the server and to change the data files but not to
look in any files outside this directory. If the application would be hacked it shouldn't leaf
the rest of the system open to prying eyes.
