Just checking: everything is ok for now though, right? I mean, the static lib passed on Cygwin64 for me after the latest fix.
Bill. On 7 April 2014 16:31, Jean-Pierre Flori <jpfl...@gmail.com> wrote: > > > On Monday, April 7, 2014 4:27:32 PM UTC+2, Bill Hart wrote: >> >> I actually don't think I had problems on MinGW64 either. But I'd have to >> check to be sure. >> >> The problem with using the other kind of magic is old versions of Cygwin >> which don't support it. I don't know if these exist or not. And whether >> they build MPIR anyway is entirely another consideration. >> >> I think we definitely should look at providing the ability to do both >> static and shared builds for Windows at the next release. If I'm >> understanding correctly, that means we get rid of one kind of magic and >> replace it with another. The user doesn't have to change anything? >> > In fact, we should use no magic at all if possible. > That's more or less what GCC/binutils advertise since 2002, cf. a link I > posted in this thread. > > Unfortunately that's not the case right now and we use the dllimport magic. > I expect that if you put the dllimport stuff, then linking to the static > lib may fail (though not tested yet). > I don't know if putting the yasm export directive will break linking to > the static lib. > > Anyway, I'm now waiting on some feedback by the Cygwin folk (who has been > very helpful already) and the GCC/binutils folk. > -- You received this message because you are subscribed to the Google Groups "mpir-devel" group. To unsubscribe from this group and stop receiving emails from it, send an email to mpir-devel+unsubscr...@googlegroups.com. To post to this group, send email to mpir-devel@googlegroups.com. Visit this group at http://groups.google.com/group/mpir-devel. For more options, visit https://groups.google.com/d/optout.
