-----Original Message-----
From: Bill Hart
Sent: Friday, September 28, 2012 5:42 PM
To: mpir-devel@googlegroups.com
Subject: Re: [mpir-devel] Possible Issue with the Windows command lIne
build?
[snip]
Its such a good idea that I have already done it!
In the big gap in MPIR development progress, I had completely forgotten
about solving this problem over a year ago.
So all that has to happen is that anyone building the command line build
has
to run mpir_config.py only once and all the cfg.h files are generated.
So we can either (a) add all these files to distributions, (b) document
the
need to run mpir_config.py once before any Windows command line build, or
(c) run a slightly modified mpir_config.py from the command line build
script.
I now like either b or c. But I'll leave it up to you to decide. Of
course the other option is to test for the existence of a cfg file. If
none is found, report to the user that they must first run
mpir_config.py and abort. We can then document this.
==============================
I have now made the changes to the Windows command line build to generate
all the cfg.h files.
This means that the this build will now fail when Python is not installed.
If we don't like this we will have to go back to the previous make.bat file
and arrange for one of the other solutions.
Case, can you please check that the command line build is still OK for you?
Brian
--
You received this message because you are subscribed to the Google Groups
"mpir-devel" group.
To post to this group, send email to mpir-devel@googlegroups.com.
To unsubscribe from this group, send email to
mpir-devel+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/mpir-devel?hl=en.
