Code::Blocks

User forums => Help => Topic started by: SpringRainSoftware on November 02, 2005, 02:20:20 am

Title: wxWidgets: why monolithic?
Post by: SpringRainSoftware on November 02, 2005, 02:20:20 am
What is the design reason to go with a monolithic build for wxWidgets?  Seems like it could be unnecessary overhead for a majority of projects.

Is there a semi-easy way to get C:B to play nicely with a split up build of wxWidgets?  I played for a couple hours but didn't make any headway.
Title: Re: wxWidgets: why monolithic?
Post by: mandrav on November 02, 2005, 08:40:00 am
You have to build C::B yourself. Other than that, just change the linking libraries...
Title: Re: wxWidgets: why monolithic?
Post by: SpringRainSoftware on November 02, 2005, 06:39:02 pm
mandrav: thanks for the reply.  When it comes to release time I'll look into that.  Mostly I was just surprised that C:B went with a monolithic as default.