Elzed 2.5.0 requires MacOSX 10.5 or later.

The sample project is initially set to build a universal binary and (obviously) to link against the universal version of the Elzed static library.

When deploying, the dynamic libaries should go into /usr/local/lib

Place the *.lzo files in the same directory as the sample executable.

We've found that the Elzed Sample programs don't run the Life and Select/Case demos reliably
  if you double-click the sample app.  The path to the .lzo files isn't set correctly in this case.
  For best results, open a console window, navigate to the executable's folder and launch
  it from the command line.