Hoping EMC-BDI is my friend....

----- Original Message -----
From: "Jon Elson" <elson@...>
> In general, you do not directly give compile commands to compile a large
> package. There is a very sophisticated command language that is part of
the
> make utility. The Makefile gives instructions to make to figure out
> which files need to be compiled, or linked, due to changes in the source,
> or follows directives to remove all derived files (ie. object, executable
> and libraries) and remake them from scratch. There is another tool called
> configure, that figures out where libraries are stored on your machine,
> what compiler to use in what circumstances, what order include files and
> libraries should be used in, and so on. It is an attempt to make
> compilation
> and linking adapt to the various versions of Unix, Linux and other posix-
> compliant system environments.
>
> When I am compiling any package that consists of more than about 3
> C source files, I create a make file for it, and let make do the work.

Thanks Jon for the info. I'm assuming most of the configs would come with
the Tarball and create a standard tree to work within and be able to output
to the proper directories like /boot for the kernel, etc. But I've been
looking for a Master set of docs to read up on How To Do it, and examples of
it being done... Havent found any.
Is the 2meg EMC PDF file the only one out there that has any info on
compiling EMC? I have to look at a sample Make file to see what your
talking about.
Also hoping that this doesnt go too far over my head... Honestly...

Vince