In this (size=2.1Mbytes, duration=4m18s) "Hello World" example a complete transformation cycle is shown. First, some basic checks are performed like the validity of the input sources. Then, a toplevel 'Makefile-ScottySetup' file is created, configured, and executed. This results in a transformed design. As demonstrated, these sources can readily be compiled and executed. Even though no explicit transformation is specified in this demo, the resulting source code is transformed to one programming style; a predefined directory structure (Network, Process, TestBench, etc) and a predefined file name convention. This increases the changes of reuse, since the resulting application source code is easier to understand. |
Commands issued during this demo: |
|
---|---|
> ls | show directory listing before compilation |
> pwd | show current path |
> make | compile the YAPI Producer-Consumer example |
> ls | show directory listing after compilation |
> pc | execute the compiled program |
> echo $MPC | show environment variable MPC is defined in current shell |
> echo $YAPIROOT | show environment variable YAPIROOT is defined in current shell |
> echo $TRIPLEMROOT | show environment variable TRIPLEMROOT is defined in current shell |
> scotty -setup | create toplevel Makefile for scotty |
> e Makefile-ScottySetup | edit toplevel Makefile |
comment-out MPC since it is a well defined environment | |
check if CPP_INCLUDES path for YAPI is well defined | |
check if APISPECIFICATION is well defined for example at hand | |
provide symbol table file to scotty to speed up the parsing process | |
> make -f Makefile-ScottySetup | create the required Makefile to execute the scotty tool |
> make -f Makefile-Scotty | execute the scotty tool via this generated Makefile |
> ls | look at directory structure for newly created intermediate files |
> make -f Makefile-Mpc | compose the design in compilable source files |
> cd ../../Design | go to toplevel directory where designs are created |
> ls | show which designs are there |
> cd yapi/Yapi | enter one design |
> e Config.h | check environment variables in config file |
> ../../Compile | compile the generated design |
> cd TestBench/PC | go to the toplevel of the YAPI network |
> PC | execute the created executable |
> The End | end of demo |