I never tried building a static library, so I'd say use OpenTTD's. As for the second question, the answer is yes.
On Tue, Mar 1, 2011 at 10:15 AM, Jose Mondefo <[email protected]>wrote: > Stefan, thanks for your clear explanation. The only this I don't fully > understand is, if I need to build a static library (for boost library), do I > have to use the OpenTTD patch, or can I use yours? > > One extra thing, as I read in a previous post, this patch works with the > .zip icu file, and the OpenTTD was thinked to work with the tgz, I'm ok? > > By the way, thanks you and Richards for this great contribution! > > ------------------------------ > Date: Tue, 1 Mar 2011 09:26:55 -0600 > Subject: Re: GNUstep + libicu on Windows > From: [email protected] > To: [email protected] > CC: [email protected] > > > Sure, no problem. The OpenTTD patch wasn't very generic, so I needed to > change a few things. First off, the OpenTTD patch is made to strictly > create a static library, we needed a shared one. Most of the changes I made > were to make the patch more generic (setting LIBPREFIX=lib, etc). As the > the lib/dll thing, the way I understand it, the .lib file type is used for > static libraries on Windows (same as .a on UNIX). > > Does that explain it? > > On Tue, Mar 1, 2011 at 7:57 AM, Jose Mondefo <[email protected]>wrote: > > Hi Stefan and Richard, > > I was looking for compiling icu in mingw32 for another project (more > precisely for compiling then boost for using in freeling project), and found > your patch, and the original patch at openttld. I see that your patch is a > kind of improvement over that (more complete), but I see that there are one > difference in the mh-mingw I don't understand very well. > More precisely in the opentld patch there are a rename of the SO from dll > to lib mention something about not working if --disable-shared, and some > extra differences about the stubnames, both of theme not applied in your > patch. Could you explain me what this difference represent? > > Thanks in advance! > > _______________________________________________ > Gnustep-dev mailing list > [email protected] > http://lists.gnu.org/mailman/listinfo/gnustep-dev > > >
_______________________________________________ Gnustep-dev mailing list [email protected] http://lists.gnu.org/mailman/listinfo/gnustep-dev
