++++++ This doesnt make sense yet. Needs to be fixed ++++++++

The Polyflow toolchain consists of a cross compiler (gcc Version 2.8.1), a fortran 77 to C converter (f2c version 20050501) a cross assembler (gas 2.9.1) and linker (gnu ld 2.9.1).

In addition we have our own (rudimentary) Ansi-C and Fortran libraries and include files that get compiled by the toolchain.

First, cd to the directory where you want to build (this can either be the polyflow-tools/ directory or some other directory if you prefer to keep your .o files seperate from the source files).

In the build directory run the "setup" script from the polyflow-apps/ directory. The setup script takes one argument -install_dir=<dir to install in>. If you leave off the argument then the default is $pwd/install.

If you only want to build one of the tools, library or applications then you can just run the setup script in the appropriate subdirectory of ece511/ (tools/ target-env/ or apps/). These setup scripts also just take the -install_dir argument.

(In particular, if you want to use the precompiled toolchain to compile the apps, then run "ece511/apps/setup -install_dir=/home/mfrank/polyflow-tools".)

Finally, type "make" and you should be off and running building the toolchain and libraries and installing the result in whatever directory you chose.

The apps don't have a toplevel Makefile, so you will have to go into each directory one by one.