not be in the main compiler directory.
a value, if you want output out of it).
3. Change to the main compiler directory.
5. The interpreter will output the final result of the program.
automatically synthesized into appropriate hardware.
using one of the provided examples in the examples/ directory).
2. Change to the main compiler directory.
* Use the `-m sim` switch to specify compiling for simulation.
tell you what it is doing.
Note that with many simulators, the order is significant.
`work.simulation_toplevel` as the top-level entity.
the code exits via asserting a failure (so if you see a "failure"
message, it means your program terminated).
although the process should be similar with other manufacturers.
are provided in the `lib` and `include` directories.
full advantage of the hardware.
2. Create a new directory to use for the Quartus project.
is capable of inferring it.
on it, while Quartus II is closed, not from within Quartus II).
9. Add the files mentioned by `gosc` above to your project.
12. Run "Fitter (Place and Route)" from the list in the sidebar.
13. Run "Assembler" from the list in the sidebar.
between your computer's USB port and the board's "BLASTER" port).
15. Run "Program Device" from the list in the sidebar.
16. Click the "Start" button in the programmer.
start running as soon as you release it.