From: John L. <jla...@gm...> - 2012-08-11 04:48:56
|
On Thu, Aug 9, 2012 at 2:12 AM, Paul K <pau...@ya...> wrote: > Hi John, > > I think I'm close, but still not there yet. I did get luawx.dll > library, but it's 12+M in size and it depends on > libwxlua_lua51-wx28mswu-2.8.12.dll (which seems to be a renamed lua It is the Lua library dll named so that it will not clash with anybody's elses Lua dlls. > dll). There are also several other libraries, but the application > seems to work without them: > > 12,318,932 libwx.dll > 3,480,509 libwxlua-wx28mswu-2.8.12.dll > 11,973,978 libwxlua_bind-wx28mswu-2.8.12.dll > 3,413,790 libwxlua_debug-wx28mswu-2.8.12.dll > 215,408 libwxlua_lua51-wx28mswu-2.8.12.dll > 3,405,545 libwxlua_socket-wx28mswu-2.8.12.dll > 61,395 lua.exe > 219,561 luac.exe Did you build the shared libs first and these remain in the build directory from this earlier build? > Why do all the names start from libwx? Also, the library seems to be Because they are all libraries for wxLua. Currently I do not bother to detect that gcc is being used in Windows and I treat them like Linux libraries where there is an expectation that they might be installed to the system /usr/lib dir with hundreds of other libraries so they must have unique names that describe what they are to the rest of the world. > much larger in size than yours (12M vs. 5.5M) and this is in > MinSizeRel configuration. I couldn't find any setting that would > affect the size. Gcc creates much larger libraries and executables than Visual Studio, this is to be expected. > Is this possible to link against an existing *real* lua.dll > (lua5.1.dll or lua51.dll), rather than against > libwxlua_lua51-wx28mswu-2.8.12.dll? What do you mean "real"? Would a rose by any other name not smell as sweet? Why isn't modules/luaproxydll/lua51.dll and lua5.1.dll not copied over to the build/bin dir? The root CMakeLists.txt should copy them over if WIN32 is declared for Mingw, is it somehow not declared? Regards, John |