Author Topic: wxWidgets: why monolithic?  (Read 2659 times)

Offline SpringRainSoftware

  • Single posting newcomer
  • *
  • Posts: 3
wxWidgets: why monolithic?
« 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.
-----
C:B version -> RC2
wxWidgets -> 2.6.2 DLL

Offline mandrav

  • Project Leader
  • Administrator
  • Lives here!
  • *****
  • Posts: 4291
    • Code::Blocks IDE
Re: wxWidgets: why monolithic?
« Reply #1 on: November 02, 2005, 08:40:00 am »
You have to build C::B yourself. Other than that, just change the linking libraries...
Be patient!
This bug will be fixed soon...

Offline SpringRainSoftware

  • Single posting newcomer
  • *
  • Posts: 3
Re: wxWidgets: why monolithic?
« Reply #2 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.
-----
C:B version -> RC2
wxWidgets -> 2.6.2 DLL