On 9/12/2013 12:50 PM, K. Frank wrote: > Hi Vadim! > > On Thu, Sep 12, 2013 at 11:16 AM, Vadim <> wrote: *snip* >> Before we embark on that, I'd like to clarify a couple more things: >> >> 1. Have you guys considered adopting/forking phtreads-win32? I believe this >> is what the regular mingw uses. That library looks more mature, at least as >> far as mutexes go. *snip* > I think that pthreads-win32 has a less flexible license. I think one > reason for winpthreads is to offer users a more flexible license. > (Maybe they don't have to ship source code for pthreads-win32, > or something.)
This is absolutely the case. The pthreads-win32 library is LGPL, forcing the distribution of its source code along with all binary distributions -- and since all binaries compiled by a pthreads-enabled GCC depend on the pthreads library, everyone would have to distribute the pthreads source along with every program. Cheers to Kai et al. for creating an alternative. -John E. / TDM ------------------------------------------------------------------------------ How ServiceNow helps IT people transform IT departments: 1. Consolidate legacy IT systems to a single system of record for IT 2. Standardize and globalize service processes across IT 3. Implement zero-touch automation to replace manual, redundant tasks http://pubads.g.doubleclick.net/gampad/clk?id=51271111&iu=/4140/ostg.clktrk _______________________________________________ Mingw-w64-public mailing list Mingw-w64-public@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/mingw-w64-public
