On 10/04/11 2:28 AM, David G. Koontz wrote: > Mac OS X Installation > ---------------------
I sent a simple installer app to Tristan built with Duckbill, not the most robust tool apparently. It doesn't include gtkwave and comes in at a whopping 1.5 MB. The easiest way I know of to get gtkwave would be to 1. install Xcode (Apple's development environment), 2. install Macports and 3. sudo port install gtkwave. Unfortunately about 8 hours later you might have it. There are quite a lot of build dependencies, and those dynamic libraries are depending on other libraries ... Once you have all the libraries you need, you can build gtkwave manually quite easily by configure command, other that in the latest release(s) with a dependency on lzma_end() in liblzma not uspplied in Macports. It's used for VZT files. Don't know how but imagine it's possible to insure all the necessary API elements are included in liblzma. The latest gtkwave builds with configure --disable-xz, which would disable support for VZT. The big deal with distributing gtkwave would be the source for all the libraries. A light weight viewer would be useful if it were well portable. Anyway, I'll do some background work on improving the quality of an installer app (bundle). Make the scripts a little more bullet proof and maybe use a script for invoking over all action, or maybe just switch package builders. I've seen some inconsistent operation of the installation script I'd be tempted to blame on the binary program bit that invokes the script. Actions that just don't happen. You can make a Duckbill produced package crash at the drop of a hat and there doesn't appear to be proper error handling. Duckbill doesn't appear to have grown up yet. Or it isn't particularly compatible with my platform. _______________________________________________ Ghdl-discuss mailing list [email protected] https://mail.gna.org/listinfo/ghdl-discuss
