Difference between revisions of "Creating an FMOD package for Autobuild"
Jump to navigation
Jump to search
(Created page with " Creating your own FMOD package archive for autobuild to use. An autobuild installable package is a bz2 archive containing these directories: |-bin | |-include | |-lib | |-deb…") |
|||
| Line 1: | Line 1: | ||
Creating your own FMOD package archive for autobuild to use. | Creating your own FMOD package archive for autobuild to use. | ||
An autobuild installable package is a bz2 archive containing these directories: | An autobuild installable package is a bz2 archive containing these directories: | ||
<nowiki> | |||
|-bin | |-bin | ||
| | | | ||
| Line 14: | Line 13: | ||
| | | | ||
|-LICENSES | |-LICENSES | ||
</nowiki> | |||
Empty directories may be omitted. | Empty directories may be omitted. | ||
For FMOD, you need to place fmod375\api\inc\fmod.h and fmod_errors.h into the include directory, fmod375\api\lib\fmodvc.lib into lib\debug and lib\release (rename it to fmod.lib), and fmod375\api\fmod.dll also into lib\debug and lib\release. The appropriate license should be placed in LICENSES. | For FMOD, you need to place fmod375\api\inc\fmod.h and fmod_errors.h into the include directory, fmod375\api\lib\fmodvc.lib into lib\debug and lib\release (rename it to fmod.lib), and fmod375\api\fmod.dll also into lib\debug and lib\release. The appropriate license should be placed in LICENSES. | ||
Once these files are in place, archive the directory structure into a bz2 file. | Once these files are in place, archive the directory structure into a bz2 file. | ||
Revision as of 15:00, 15 April 2011
Creating your own FMOD package archive for autobuild to use.
An autobuild installable package is a bz2 archive containing these directories: |-bin | |-include | |-lib | |-debug | | | |-release | |-LICENSES Empty directories may be omitted.
For FMOD, you need to place fmod375\api\inc\fmod.h and fmod_errors.h into the include directory, fmod375\api\lib\fmodvc.lib into lib\debug and lib\release (rename it to fmod.lib), and fmod375\api\fmod.dll also into lib\debug and lib\release. The appropriate license should be placed in LICENSES. Once these files are in place, archive the directory structure into a bz2 file.