- Put fmod.dll as custom ressource into your resource
- Check on startup if fmod.dll is present and up to date; if not, extract it from the resources
- WHEN DONE CHECKING/EXTRACTING, initialize fmod.dll
Visual Basic checks if fmod.dll is present the first time your program uses it. So you can check if it’s present before. Once used, you cannot overwrite or delete it, because it’s used as long as visual basic / your program is running
If fmod.dll is missing, visual basic raises an error which can be handeled with on error goto …
There are two options:
1) Pay for a commercial (not shareware) FMOD license. This gets you the FMOD source code. But that won’t help you much with Delphi or VB.
2) Use a static DLL linking tool.
Using a static DLL linking tool (embedding the FMOD DLL in your executable as a resource and extracting to a file in your application directory at runtime) is discouraged by the FMOD End-User License Agreement. See README.TXT in your FMOD directory. Why would this be? The first reason I can think of is since FMOD is free for freeware, the only exposure it gets is having the fmod.dll file in your application directory. If you go and hide the fmod.dll file in your executable, then FMOD gets no exposure at all, essentially giving FMOD no credit.
If you [u:5lgwpp8j]need[/u:5lgwpp8j] static linking, it could be some democompo or such that requires 1 file only. If so, then you could check out the minifmod library that’s available for download.
If minifmod isn’t good enough, then pay the price for the full deal, or live with the dll so fmod get enough advertising
- DEVLiN answered 14 years ago
Please login first to submit.