|
Sorry for the top post. Are you building with Visual Studio? If so, it sounds like one of your build configurations might be a little different than the others? From the configuration manager you can select manage configurations and in the drop down there should be an option for all configurations. I'd double check the project isn't building a DLL by accident. My VS experience so far: I've had to set all configurations and go through each properties screen of each project to ensure they all align. WinLua currently only supports 5.1 and 5.3 so I've never tested against 5.2, nor have I tested my static libraries properly. WinLua builds a static and a dynamic library in separate projects in the one solution. For What It's Worth, Russ Sent from my BlackBerry 10 smartphone on the Virgin Mobile network.
I've run into a peculiar case while compiling and running my test suite for Lua and sol2 using Lua 5.2.4. In my tests, I build a lua_CFunction-containing DLL from source called "my_object". I also build Lua from source in various versions (everything from LuaJIT to Lua 5.3.4). Compiling Lua 5.3/5.1 statically or dynamically and linking against that for the DLL is also fine. |