On Mar 1, 6:47 pm, Jeff Gilchrist <jeff.gilchr...@gmail.com> wrote:
> On Sun, Mar 1, 2009 at 12:14 PM, Cactus <rieman...@googlemail.com> wrote:
> > On Windows I just generate both gmp.h and mpir.h from gmp-h.in.
>
> I guess I didn't notice that. Using your the "standard" convention you
> have set up for the various MSVC projects you have created, all I find
> in build.vc9\lib\Win32\Release or build.vc9\lib\x64\Release are the
> files:
> - mpir.h
> - mpir.lib
Hello Geoff,
At the moment the following should be there:
mpir.h
config.h
gmp-mparam.h
mpir.lib
mpir.pdb
mpirxx.h )
mpirxx.lib ) if the cpp library is built
mpirxx.pdb )
For the DLL subdirectory this list is (the DLL includes C and C++):
mpir.h
mpirxx.h
config.h
gmp-mparam.h
mpir.dll
mpir.exp
mpir.lib
mpir.pdb
Deepending on what people want I can add gmp.h and gmpxx.h if
necessary.
If you don't see these files after the appropriate builds, there is an
error
> So projects like GMP-ECM and others that link to GMP are expecting
> gmp.h and gmp.lib to be there so it fails and I have to rename those
> files. Maybe this is different in the trunk code, I haven't checked.
Until MPIR 1.0 is released I am leaving my GMP associated projects
with links to GMP.
When MPIR 1.0 is released I intend to switch all these projects to
use MPIR.
Given where MPIR performance is now, the exciting things that I know
are in the pipeline, and the hostility of the GMP maintainer to native
Windows support, I cannot see that it makes any sense for me to invest
further effort on native Windows support for GMP once MPIR 1.0 is
released.
> > Jeff wanted the same names on Windows and Linux but I am not sure this
> > matters since the name extensions .lib and .a are different anyway.
>
> They don't have to be identical names, I just meant it would be nice
> if it was consistent between the two using "gmp" or "mpir" as naming
> conventions for the lib and include files.
Right, I agree! The situation is that the mpir (and mpirxx) names
will be used on Windows.
This is quite easy for anyone who wants gmp names - the DOS command
'ren mpir.* gmp.*' will do it and I can add a batch file for this if
necessary.
> The name mpir.lib is fine, but it would be nice if compatibility with
> GMP was kept as well with a symbolic link of some sort. Unfortunately
> it seems creating a Windows shortcuts to mpir.h and mpir.lib with the
> names gmp.h and gmp.lib do not work. But if you are now creating both
> with the latest code, that solves my problem.
I have been doing this for the mpir.h header only - by copying it to
gmp.h. But I think a global rename might make more sense. In fact it
would be easy to run a post build script that asked what names were
wanted.
Brian
A simple batch file to rename all the files mentioned above would do
this wouldn't it?
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---
