On Thursday, August 1, 2013 8:56:38 AM UTC+2, Cactus wrote:
>
> On 31/07/2013 18:24, Jean-Pierre Flori wrote: 
> > Dear all, 
> > 
> > I'm currently working on some pieces of the build system. 
> > I must admit I don't really like the fact that MPIR ships a modified 
> yasm 
> > source tree. 
> > I think it would be cleaner, and easier to maintain, to ship a tarball 
> and 
> > untar it, or to the least a vanilla source tree, possibly patch it and   
> > then configure/build it if needed (i already added options to use a 
> > system-wide or user-provided yasm, when autotools are used at least). 
> > A little like what we do in Sage when we patch upstream software (like 
> > MPIR!). 
> > 
> > Do you really need to pass specific options to yasm? or a "generic" 
> > (./configure && make) build would do? 
> > That's important because the main modification I see is to let the 
> > autotools stuff recognize options given to MPIr and automatically passed 
> to 
> > yasm. 
> > 
> > My other question is about the VS builds because I never tried them and 
> > feel completely incompetent. 
> > With VS, is yasm always built? Is it possible to let VS untar something? 
> or 
> > does yasm directory have to be uncompressed? 
>
> As Bill has said, I can confirm that YASM is not a part of MPIR on 
> Windows.  The user has to download and install VSYASM from the YASM site 
> in order to build MPIR on Windows. 
>
> Good news!
That will simplify things.
 

> The source code routines in the x86w and x86_64w directories are either 
> original code or translations of the routines in x86 and x86_64.  These 
> routines are designed to work using the full Windows ABI including the 
> Windows x64 exception handling specification, which YASM fully supports. 
>
> I didn't think at first of the exception handling mechanism, thanks for 
the hint!
Is there anything similar on x86?

Best,
JP

-- 
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/groups/opt_out.


Reply via email to