When I get home i will post you a macro that epic seems to use to avoid variable conflicts that you can turn on and off but still you should definitely not include “windows.h” or atlslt.h etc in your custom header that you expose to the game.
I have the same problem here. I am trying to read serial port data into unreal. So far without success.
I have two code versions (one with managed C++=/CLR, one without) and don’t manage to get any one of them to compile or link (static DLL versions, online advice seems outdated) in Unreal Engine. I think I also have some problems with the unreal build system which doesn’t quit know what to do.
For example I just try adding a cpp and h file to the project (in VS), use the code in existing cpp files and the whole think won’t build anymore.
The DWORD problem shows up when I try to the non-CLR version.
What exactly is meant with “DLL and expose only headers to the actual interface”? How is that done?
Could you please give me a hint how to proceed or what worked for you?