Building a DLL using miniaudio.

[psuong]

Hello, I'm trying to build a DLL (on Windows-x64/VS2022) of miniaudio so that I can use in a Unity project, but I'm pretty new to the process. After reading the readme and the docs, I'm not entirely sure on how to do it as I'm getting linker errors in an extern API.

unresolved external symbol ma_engine_init referenced in function init_engine_on_stack

The basic idea is that all I want to do for now is compile a working DLL where I call ma_engine_init on the stack.

// in framework.h
#pragma once

#define WIN32_LEAN_AND_MEAN             // Exclude rarely-used stuff from Windows headers
// Windows Header Files
#include <windows.h>
#include "miniaudio.h"

#ifdef AUDIO_EXPORTS
#define AUDIO_API __declspec(dllexport)
#else
#define AUDIO_API __declspec(dllimport)
#endif

extern "C" {
	AUDIO_API void init_engine_on_stack();
}

// in framework.cpp
#include "pch.h"
#include "framework.h"
#include "miniaudio.h"

void init_engine_on_stack() {
	ma_result result;
	ma_engine engine;

	result = ma_engine_init(NULL, &engine);

	if (result != MA_SUCCESS) {
		return;
	}
}

I've added a link of the visual studio project I'm working on, but I'm not really sure what I'm missing here.
https://github.com/psuong/miniaudio-dll.

Any tips and advice is appreciated.

[mackron]

That linking error is happening because you haven't included the implementation of miniaudio anywhere. Add #define MINIAUDIO_IMPLEMENTATION:

#define MINIAUDIO_IMPLEMENTATION
#include "miniaudio.h"

Alternatively, consider using the split version if you'd rather use a traditional .c and .h pair: https://github.com/mackron/miniaudio/tree/master/extras/miniaudio_split

[psuong]

Oh I should have mentioned that I added a miniaudio.cpp that implements:

#define MINIAUDIO_IMPLEMENTATION
#include "pch.h"
#include "miniaudio.h"

I'll try out the miniaudio_split versions today.

[psuong]

Okay thanks for the tip. I have something that can work for now. I guess I'm not too familiar with visual studio workflow so I decided to stick with cmake.

[mackron]

By the way, not sure if you were just using it for experimental purposes, but your init_engine_on_stack() is non-functional. Because your ma_engine object is initialized on the stack, as soon as the function returns your ma_engine object will be destroyed and unusable.

[psuong]

Yea, I was just experimenting with it.