There's a Mac OS X disk image zipped for compatibility with Google Docs located at:
https://docs.google.com/leaf?id=0BzC1eu6V2h5MYjYxZTNmYTgtZGI4Zi00MzA2LTg0ZTgtOTNlMDAwZTM3MmEw&hl=en&authkey=CI7q0nQ 2.6 MB, 10.5/10.6 Intel (i386). Comprised of a managed install package and an uninstaller app, as well as some help, readme and build instructions to replicate the effort. This was built using MacAda 2.3 as a standalone effort. Anyone with this link can download the disk image, 2.6 MB. I know of a couple of typographic errors in the docs otherwise it's not too bad. Thanks to Dr. Doug Lyon for his aid in debugging SDK portability and installation packaging. This is ghdl-0.29 revision 142 build from the subversion repository, and is an mcode version. Instead of operating as a front end to a gcc compiler, it directly generates code in a just in time manner. The Getting Help document tells how to find a working gtkwave from the eng-osx effort at Sourceforge. The amount of source required to build and distribute gtkwave from a non-gtk start is somewhat high, and isn't contemplated. gtkwave can be built by installing Macports, implies having the Xcode developer tools loaded and can be invoked by 'sudo port install gtkwave' and waiting several hours for everything to build. Currently ghdl_mcode_r142.dmg.zip is the only thing in my Docs documents collection, it should stick around for a while. For GPL afficionado's there have been no changes made to any source code downloaded from the Subversion repository, although an additional step is inserted for relinking ghdl_mcode to the 10.5 SDK for portability. (This was built on a 10.6.7 based Macbook 5,1). A useful next step would be to make the installation relocatable, which would require 'building' the VHDL libraries at install time. The install package and uninstall app currently require administrative priviledge to use and ghdl is installed in /usr/local/ghdl with a link to the executable at /usr/local/bin/ghdl and the ghdl man page at /usr/local/man/man1/ghdl.1. I don't see the need for installing without administrative privileges as being urgent. Relocation wouldn't be hard at all. The effort is all in product testing. There's also a couple of minor annoyances with the installer, giving you the option to change installation locations when no options are available and the license plugin asking you to accept the GPL license when use is not restricted and distribution requires compliance. Use and distribution are really separate. I'm more inclined to focus any ghdl gcc front-end version efforts on Macports rather than Xcode build environments. The only draw back is that Macports doesn't do soft binding for SDK portability by default, the expectation being that everyone 'install' (read build) locally from source (bootstrapping original compilers aside). There is no particular advantage of one over the other for non-native software. Thanks to Dr. Douglas Lyon for help in debugging installation and soft binding SDK issues, Mac OS X 10.5 being out of reach for me today. I've tested this with a 4,700 gate equivalent VHDL model of a DES encryption chip with an 8 bit interface operated by a testbench doing assertion based validation against known results. 291 vectors in 2340 bus operations, around 2 milion signal assigns and around 30,000 clock events with over a thousand signals. The vector set insures full toggle coverage. _______________________________________________ Ghdl-discuss mailing list [email protected] https://mail.gna.org/listinfo/ghdl-discuss
