Distribute a zenilib Game

Previous Step: Build a Game

Clean up your work

Instructions vary by development environment.
Visual Studio
1. Make sure that you did your final build in Release mode rather than in Debug mode.
2. Pick a cleaner script to run:
  - zenilib/clean/zenilib_clean.bat deletes object files and other "junk" files related to Visual Studio. This is the safest choice, and I recommend running this whenever you're archiving a project anyway.
  - zenilib/clean/zenilib_clean_extra.bat additionally deletes per-user Visual Studio settings and Debug builds.
  - zenilib/clean/zenilib_clean_extra_x86.bat additionally strips out support for x64 builds and deletes MacOS X Frameworks if they are present. This is probably the one you want.
  - zenilib/clean/zenilib_strip_x64.bat will just strip out support for x64 builds.
3. If you're using version control, do an export to avoid distributing .svn/ (or equivalent) directories.
XCode

GCC
1. Make sure that you did your final build in Release mode rather than in Debug mode.
2. Pick a cleaner script to run:
  - zenilib/clean/zenilib_clean.py deletes object files and other "junk" files related to Visual Studio. This is the safest choice, and I recommend running this whenever you're archiving a project anyway.
  - zenilib/clean/zenilib_clean_extra.py additionally deletes per-user Visual Studio settings and Debug builds.
  - zenilib/clean/zenilib_clean_extra_x86.py additionally strips out support for x64 builds and deletes MacOS X Frameworks if they are present. This is probably the one you want.
  - zenilib/clean/zenilib_strip_x64.py will just strip out support for x64 builds.
3. If you're using version control, do an export to avoid distributing .svn/ (or equivalent) directories.

Make a self-contained archive

Instructions vary by development environment.
Visual Studio
1. Make sure you've cleaned up your work, following the instructions above.
2. zenilib/clean/zenilib_strip_sources.bat will delete your source code, should you wish not to distribute it. Beware, it is non-recoverable. Make sure you're working on a copy of your project, and run this script at your own risk.
3. Download the redists:
  zenilib Redists for Visual Studio 2010 (7z) or zenilib Redists for Visual Studio 2010 (zip)
  
  These are valid for:
  - Direct3D 9.0c
  - OpenAL 1.1 Core SDK 3.05
4. Extract the redists to the directory containing your zenilib/ directory. You may need to merge the directories manually if you have changed your zenilib/ directory's name.
5. Inform your users that they must run the included redists in zenilib/redist/ before they can run your application.
6. zip up your project.
7. Test your application one last time.
XCode
1. Rename your Release build, Application.app, to whatever is desired. It may be in a DerivedData directory if you are using Xcode 4.x.x.
2. zip up your Application.app.
3. Test your application one last time.
GCC

This is unsupported.

Make a self-contained installer

Instructions vary by development environment.
Visual Studio
1. Make sure you've cleaned up your work, following the instructions above.
2. zenilib/clean/zenilib_strip_sources.bat will delete your source code, should you wish not to distribute it. Beware, it is non-recoverable. Make sure you're working on a copy of your project, and run this script at your own risk.
3. Name your copy zenilib/.
4. Download NSIS:
  NSIS / Portable NSIS
5. Install NSIS.
6. Download the release package:
  zenilib Release (7z) or zenilib Release (zip)
  
  These are valid for:
  - Direct3D 9.0c
  - OpenAL 1.1 Core SDK 3.05
7. Extract the release package to the directory containing your zenilib/ directory. You may need to merge the zenilib/ directories manually if you have changed your zenilib/ directory's name.
8. Edit Zeni NSIS Settings.txt
  - Ensure that the definition for EXECUTABLE_FILE_X86 matches the x86 .exe launcher name in zenilib/. Similarly, ensure that EXECUTABLE_FILE_X64 matches the x64 .exe launcher name in zenilib/.
  - PRODUCT_NAME should be changed to match the name of your game.
  - PRODUCT_VERSION should be changed to match the version number of your game (e.g. '1.0').
  - PRODUCT_PUBLISHER should be changed if you are not affiliated with Wolverine Soft.
  - PRODUCT_WEB_SITE should be changed if you have a website for your game.
  - PUBLISHER_WEB_SITE should be changed to your website, or to your organization's website.
9. Run Zeni NSIgen.exe to generate Zenilib.nsi.
  - If you have problems running it, try running zenilib/redist/visualc/vcredist_x86_9.0.30729.17.exe
  - Alternatively, rebuild Zeni NSIgen.exe from the included source.
10. Use NSIS to compile Zenilib.nsi into an installer.
11. Test the installer (ideally on a fresh install of Windows XP or lower).
XCode

This is unsupported and unidiomatic for MacOS X.
GCC

This is unsupported.

Next Step: Read (some) documentation and have fun!