Makefile to FDL Utility

Makefile to FDL is a utility to quickly create a new Flow Description Language for projects that already have a working Makefile. This utility reads a Makefile and then generates an output FDL file, which is the FlowTracer equivalent of the Makefile. This utility provides a quick way to get started with a "near enough" FDL equivalent.

Makefiles can be very complex, which can affect the results. We strongly recommend checking the FDL output for accuracy and completeness. For example, it is known that self-generating Makefiles are not supported; FDL files generated from self-generated Makefiles are not guaranteed to be a complete equivalent of the original Makefile.

Access and Set Up Makefile to FDL

Access Makefile to FDL utility through the vovconsole.

Go to the Tools menu and then select the Makefile to FDL menu item.
A dialog opens, which enables you to specify a working directory, an input Makefile and an output FDL file.
Enter the working directory or navigate to it using the ellipsis (...) button on the right.

Note: The working directory is often the directory containing the Makefile. It allows relative pathnames in the Makefile to be resolved.
Use the Makefile text field to enter the path to the Makefile to be translated. Ensure that the Makefile is readable.
The Makefile loads into the left pane.
Enter the pathname to be used to store the output FDL file (default: FDL.out).
The system is now ready to generate FDL.

Generate FDL

To generate FDL, click Convert at the bottom of the dialog.
The FDL is shown in the right pane. The FDL will then be generated. Details can be viewed as follows:
- Clicking on a line in the FDL pane on the right will cross-highlight the corresponding rule in the Makefile from which the FDL line was derived.
- Clicking a line in the Makefile, highlights the corresponding line in the FDL.
Note: Cross-highlighting may not work for all lines, but it will work for the most significant lines in the FDL and the Makefile.
If satisfied with the FDL, click Save FDL to capture it into the named output file for use with FlowTracer.
Optional: Click Clean to delete the intermediate files that were created during FDL generation. We recommend reviewing the FDL and ensure that all dependencies and generation rules have been captured correctly.