Re: wxEuphoria and wxWidgets 2.9 is slow
- Posted by mattlewis (admin) Jan 15, 2012
- 1303 views
I meant that, I noticed at one point it seems you switched from building just one wxWidgets DLL to many, but I saw no reason to do that. So a better question would be, is one build any better than the other? The entire collection of separate DLLs is about ~30 MB, whereas the monolithic DLL on its own is about 20 MB. It seems wxWidgets got a lot bigger with 2.9, perhaps due to them drawing in previously "external" features.
Yes, shipping a single dll was simpler, especially if you wanted to redistribute wxEuphoria with your application. Are you building debug versions? MinGW produces massive binaries when you turn on debugging information.
It looks like there's just two DLLs it links with: libgcc_s_dw2-1.dll and libstdc++-6.dll. With a monolithic wxWidgets DLL, and the wxEuphoria DLL, we'd still have only four DLL files to ship. I may try cross compiling if I cannot solve the speed issue by paring down the library; perhaps it's a build issue with MinGW.
It shouldn't make a difference as far as loading the library, but it will definitely build faster. My understanding is that when you run MinGW / MSys under windows, it has to emulate a lot of POSIX stuff like fork, which makes a lot of things a lot slower. I've found that compiling in a VM running Linux is actually a lot faster than running MSys.
Matt
