To illustrate the large purpose of VHDL, here is a commented VHDL "Hello world" program. Also 2.1 The hello world program: 2.1 The hello world program In the ghdl manual see 1.3 What is GHDL?, (The Windows(TM) version of GHDL is not based on GCC but on an internal code generator). Where ever 'Windows' appears it should be read as 'Windows or other mcode version'.
As an oversight I didn't think to amend the ghdl manual to include the word mcode wherever Windows appeared and release modified manual. In ghdl.html you could search for every occurrence of 'Windows' to find reference to the mcode version. The documentation for ghdl is found in /usr/local/ghdl/doc/, there's the ghdl man page which is linked elsewhere, ghdl.html and ghdl.texi which are the ghdl manual and not linked elsewhere. This version is derived from svn129 (following the ghdl-0.29 release), and contains an i386 binary. cf files for pre-analyzed libraries, by default these will show up in /usr/local/ghdl/libraries, the executable ghdl found in /usr/local/bin links to /usr/local/ghdl/translate/ghdldrv/ghdl_mcode, and /usr/local/ghdl is a stripped down tree resulting from the compilation of the ghdl_mcode version. All you are going to see is the work-obj93.cf file for the working directory and any. In an mcode version of ghdl the -r run command also elaborates. The elaborated model only exists in memory at run time and the -e elaborate command is superfluous other than an entry in the working library. It's the mcode version (like on Windows), which means it doesn't produce object codes or a standalone executable of a VHDL model with the consequence you can't bind foreign objects (subprograms) to the model.
#Gtkwave tutorial for mac os
There's a version of ghdl for OS X running on Intel processors for versions 10.5, 10.6,10.7 and 10.8 available from (can be downloaded at GHDL for Mac OS X).