How To Build

How To Build #

MMDAgent-EX runs on macOS, Linux, and Windows. It can also runs on WSL2 environment. The build operation has been confirmed in the following environments:

  • macOS: M2 Macbook Air / macOS Ventura, Intel Mac / macOS Sonoma
  • Linux: Ubuntu-22.04, Ubuntu-20.04
  • Windows: Windows 11 with Visual Studio 2022
  • Linux on WSL: Ubuntu-22.04 on WSL2 (v1.2.5.0) on Windows

Windows users can also get pre-built binaries from GitHub Release page.

Obtaining the Code #

GIT LFS should be installed beforehand.

Before obtaining repository, make sure to have Git LFS installed on your envieonment; if not, install it.

Check and Install Git LFS

Check if it’s installed

git lfs version

Install on macOS using brew:

brew install git-lfs
git lfs install

Install on Linux:

sudo apt install git-lfs
git lfs install


Install the LFS extension from the Git LFS website.

Obtain the repository from GitHub using Git LFS:

git clone

Build Procedure #

macOS #

The following packages are required. Install all before build with brew install.

  • cmake
  • poco
  • glew
  • libjpeg
  • re2
  • portaudio
  • minizip
  • libsndfile
  • libsamplerate
  • sox
  • rabbitmq-c
  • libomp
  • librdkafka

Do build with CMake. The built executable and plugins will be stored under to the Release/ directory.

cd MMDAgent-EX
cmake -S. -Bbuild -DCMAKE_BUILD_TYPE=Release
cmake --build build

Error on libomp: perform the following and retry.

brew link --force libomp

Error on jpeg: try installing jpeg-turbo and retry.

brew install jpeg-turbo

The brew package directory may change depending on your environment, i.e., /usr/local/ or /opt/homebrew. The build script will try to guess the prefix directory by executing brew --prefix. If it does not work well, specify the brew prefix path with environment variable HOMEBREW_PREFIX.

Linux (Ubuntu, WSL2) #

The list of required packages is in the requirements-linux.txt, so install all the packages listed in it in advance with apt install. If you are using Ubuntu, you can do all at once as follows:

cd MMDAgent-EX
sudo apt install `cat requirements-linux.txt`

Build with CMake:

cmake -S. -Bbuild -DCMAKE_BUILD_TYPE=Release
cmake --build build

After a successful build, the necessary executables and plugins are ready at the Release/ directory.

Windows #

Build with Visual Studio 2022. It requires C++ development environment and Windows SDK. During Visual Studio’s installation, check “Desktop development with C++” and install MSVC v143 and Windows 11 SDK (confirmed with 10.0.22000.0).

  1. Open MMDAgent_vs2022.sln with Visual Studio 2022
  2. Right-click on main in Solution Explorer and set as the startup project
  3. Set the build configuration to Release
  4. Execute “Build Solution”
Pre-built executable binaries are also provided for convenience. If you do not have build enviroment, download the latest zip file for win32 from the GitHub releases page and unzip the contents into the Release folder.

Built Files #

All the files required for execution will be generated under the Release folder.

On Windows, an executable file has “.exe” prefix and the plugin files has “.dll” suffix. On macOS and Linux, there is no “.exe” for executable file, and plugin file has “.so” suffix instead.

Under AppData, there are various data files required for execution, and DLLs includes external DLLs necessary for operation for Windows.

├── MMDAgent-EX.exe
├── MMDAgent-EX.mdf
├── AppData/
├── DLLs/
└── Plugins/
    ├── Plugin_AnyScript.dll
    ├── Plugin_Audio.dll
    ├── Plugin_Flite_plus_hts_engine.dll
    ├── Plugin_Julius.dll
    ├── Plugin_Kafka.dll
    ├── Plugin_LookAt.dll
    ├── Plugin_Network.dll
    ├── Plugin_Open_JTalk.dll
    ├── Plugin_RabbitMQ.dll
    ├── Plugin_Remote.dll
    ├── Plugin_TextArea.dll
    ├── Plugin_Variables.dll
    └── Plugin_VIManager.dll

If installation is necessary, copy everything under this Release folder, maintaining the directory structure.

Libraries included in the archive but not used in macOS and Linux #

The following bundled libraries are used only on Windows. On macOS / Ubuntu, these bundled files are not used, and the ones from the packages installed on the system are linked instead.

comments powered by Disqus