Author Topic: C::B With IM  (Read 14039 times)

Offline kirash4

  • Multiple posting newcomer
  • *
  • Posts: 42
Re: C::B With IM
« Reply #30 on: April 07, 2014, 01:34:07 am »
You're probably right, and I think the pthread issue has more to do with MinGW than IM. But, staying on C::B, I need to understand how it works if I'm going to make the transition. So what I want to ultimately do, is create an application with the help of wxWidgets and IM. And I need to be able to distribute that to other people who may or may not have supporting pieces (libraries) installed. What does that mean for me? Are there things I need to be setting within C::B to be able to create binary files that are self contained?

Offline dmoore

  • Developer
  • Lives here!
  • *****
  • Posts: 1576
Re: C::B With IM
« Reply #31 on: April 07, 2014, 02:58:54 am »
That's mostly a choice about using static vs dynamic libs. Most of the libs can be compiled static. But it's also not a huge deal to bundle in a handful of dlls. E.g. code::blocks itself has a handful of self built 3rd party DLLs alongside the main executable.

Offline kirash4

  • Multiple posting newcomer
  • *
  • Posts: 42
Re: C::B With IM
« Reply #32 on: April 07, 2014, 03:00:03 am »
Cool, thanks. I'll look into that. Thanks for all your help with this!