building pari,mpir on windows

[Jason Moxham]

Hi

Using current MPIR and pari-2.4.2 (svn pari requires a few minor changes, I
think!)

MPIR and Pari both build under cygwin using the usual configure,make

MPIR builds under MSYS ( a few minor issues to sort out)
Pari does not build under MSYS , although I expect it to be fairly easy to
fix.

MPIR and Pari build under MSVC with solutions&projects for the gui interface
and with projects for the batch build.

Getting Pari to work with MPIR on MSVC I decided to get rid of the solutions
and projects , so the build is purely command line only. At the mo I using
command.com(yuck) for the script , python or powershell appear better
choices , I've never used either , but being cross platform python seems the
better choice.One disadvantage of projects is that it ties them to a
specific compiler? One disadvantage of CL only is you can't use the gui to
change anything.

Pari doesn't require a complicated build system so we can do it anyway we
want or all the ways. It's simple enough that maintaining two separate build
systems is fairly trivial.The CL version is much easier in this regard.

MPIR build is complicated and the current windows build is suboptimal , ie
not as many targets, no fat build(or install equivalent).

Jason

[William Stein]

On Wed, Jun 24, 2009 at 6:57 PM, Jason Moxham<ja...@njkfrudils.plus.com> wrote:
>
> Hi
>
> Using current MPIR and pari-2.4.2 (svn pari requires a few minor changes, I
> think!)
>
> MPIR and Pari both build under cygwin using the usual configure,make
>
> MPIR builds under MSYS ( a few minor issues to sort out)
> Pari does not build under MSYS , although I expect it to be fairly easy to
> fix.
>
> MPIR and Pari build under MSVC with solutions&projects for the gui interface
> and with projects for the batch build.
>
> Getting Pari to work with MPIR on MSVC I decided to get rid of the solutions
> and projects , so the build is purely command line only. At the mo I using
> command.com(yuck) for the script , python or powershell appear better
> choices , I've never used either , but being cross platform python seems the
> better choice.One disadvantage of projects is that it ties them to a
> specific compiler? One disadvantage of CL only is you can't use the gui to
> change anything.

For the purposes of Sage windows, using Python is definitely
encouraged, since we are all supposed to be really good at Python.
I'm personally fine with the command line too.

Great work. I'm looking forward to testing this all out, and making
it available to people as well.

> Pari doesn't require a complicated build system so we can do it anyway we
> want or all the ways. It's simple enough that maintaining two separate build
> systems is fairly trivial.The CL version is much easier in this regard.
>
> MPIR build is complicated and the current windows build is suboptimal , ie
> not as many targets, no fat build(or install equivalent).
>
> Jason
>
>
> >
>

--
William Stein
Associate Professor of Mathematics
University of Washington
http://wstein.org