To Compile:Pre-compiled versions are posted for most major platforms. You should not need to re-compile unless you modify the program, or there is an incompatibility with your platform. To re-compile, normally you would invoke the Build-script at the top-level to compile the whole package. But you can also compile individual programs directly, as for example:
cc taxsolve_usa_fed1040_20xx.c -o taxsolve_usa_fed1040_20xx
To Run:Normally, you would invoke the tax programs from the graphical interface (Run_taxsolve_GUI), but you could also invoke individual programs directly, as for example:
... where fed1040_2013.txt is the name of -your- tax data file. (Two tax-data files are included for each form in OTS packages: an *example.txt and a blank *template.txt. The idea is to save the template to a personally meaningful file-name and fill in the lines with your numbers. You can maintain returns for multiple people over multiple years this way.) A file such as fed1040_2012_out.txt is produced and is automatically listed to the screen. You can print the file or store it for your records.
Starting OTS in Microsoft Windows:At the top directory of OTS there is a convenience script called Run_taxsolve_GUI that you can double-click and then it should invoke bin\ots_gui2.exe . If it does not work for you, just navitate into the bin folder and double-click ots_gui2.exe
Starting OTS in Linux, Unix, or Mac OSx:At the top directory of OTS there is a convenience script called Run_taxsolve_GUI that you can double-click or call from your command-line and then it should run bin/ots_gui2.exe . If it does not work for you, just navitate into the bin directory and run ots_gui2.exe