Visual Studio 17下C++游戏引擎FMOD库配置及教程求助

Hey there! Let's walk through getting FMOD set up properly for your C++ game engine in VS 2022. I’ve done this a bunch of times, so let’s break it down step by step.

Locating Your FMOD Libraries #

First off, let's find where those FMOD files are hiding. By default, the FMOD Studio API installs to:

C:\Program Files\FMOD SoundSystem\FMOD Studio API <your-version-number>

Inside this folder, you’ll see an api directory with two key subfolders:

• core: Contains the core FMOD audio functionality (for basic sound playback)
• studio: Contains the Studio-specific tools (for event-based audio, banks, etc.)

For each of these, you’ll find:

• inc: Header files you need to include in your project
• lib: Library files, organized by platform (look for win > x64 or x86 depending on your project’s target architecture)
  • Debug libraries end with L (e.g., fmodL.lib, fmodstudioL.lib)
  • Release libraries have no suffix (e.g., fmod.lib, fmodstudio.lib)

Configuring Visual Studio 2022 #

Open your C++ game engine project, right-click it in the Solution Explorer, and select Properties. We’ll tweak a few settings:

1. Add Include Directories #

Go to Configuration Properties > C/C++ > General > Additional Include Directories and add:

<FMOD-install-path>\api\core\inc
<FMOD-install-path>\api\studio\inc

(Replace <FMOD-install-path> with the actual path from the first section, e.g., C:\Program Files\FMOD SoundSystem\FMOD Studio API 2.02.20)

2. Add Library Directories #

Next, go to Configuration Properties > Linker > General > Additional Library Directories and add:

<FMOD-install-path>\api\core\lib\win\x64
<FMOD-install-path>\api\studio\lib\win\x64

(Use x86 instead of x64 if your project targets 32-bit systems)

3. Link the Required Libraries #

Head to Configuration Properties > Linker > Input > Additional Dependencies and add the libraries matching your build configuration:

• For Debug builds:

  fmodL.lib;fmodstudioL.lib;
  

• For Release builds:

  fmod.lib;fmodstudio.lib;
  

4. Copy DLLs to Output Directory #

FMOD needs its DLLs to be in your project’s output folder (where your .exe lives) to run. You can do this manually, or set up a post-build event to automate it:

1. Go to Configuration Properties > Build Events > Post-Build Event > Command Line
2. For Debug builds, add:

   xcopy /Y "<FMOD-install-path>\api\core\lib\win\x64\fmodL.dll" "$(OutDir)"
   xcopy /Y "<FMOD-install-path>\api\studio\lib\win\x64\fmodstudioL.dll" "$(OutDir)"
   

3. For Release builds, add:

   xcopy /Y "<FMOD-install-path>\api\core\lib\win\x64\fmod.dll" "$(OutDir)"
   xcopy /Y "<FMOD-install-path>\api\studio\lib\win\x64\fmodstudio.dll" "$(OutDir)"
   

The /Y flag overwrites existing files without prompting, which is handy for repeated builds.

Test Your Setup #

To make sure everything works, add a simple test snippet to your code (e.g., in your engine’s initialization):

#include <fmod.hpp>
#include <fmod_studio.hpp>
#include <iostream>

int main() {
    FMOD::Studio::System* studioSystem = nullptr;
    FMOD_RESULT result = FMOD::Studio::System::create(&studioSystem);
    
    if (result != FMOD_OK) {
        std::cout << "FMOD initialization failed: " << FMOD_ErrorString(result) << std::endl;
        return 1;
    }

    result = studioSystem->initialize(512, FMOD_STUDIO_INIT_NORMAL, FMOD_INIT_NORMAL, nullptr);
    if (result != FMOD_OK) {
        std::cout << "FMOD Studio initialization failed: " << FMOD_ErrorString(result) << std::endl;
        studioSystem->release();
        return 1;
    }

    std::cout << "FMOD initialized successfully!" << std::endl;

    // Cleanup
    studioSystem->release();
    return 0;
}

If this compiles and runs without errors, your setup is good to go!

Quick Notes #

• Always match your build configuration (Debug/Release) to the right FMOD libraries—mixing debug and release libraries will cause crashes.
• Make sure your project’s target architecture (x64/x86) matches the FMOD library architecture you’re using.
• If you’re using CMake instead of VS project properties, you can set up include directories, link directories, and dependencies using target_include_directories, target_link_directories, and target_link_libraries commands.

内容的提问来源于stack exchange，提问作者Omkar Patil