There is no point changing gmp.h or gmp-impl.h as other programs are not going to compile if we do that. I see no point in changing gmp-mparam.h to mpir-mparam.h, though I see no problem in changing it if we want to.
However, we should definitely change doc/gmp.tex to doc/mpir.tex and ensure that make pdf, make ps, etc still work, creating mpir.pdf, mpir.ps, etc. Bill. 2009/2/12 <ja...@njkfrudils.plus.com>: > > On Thursday 12 February 2009 14:48:00 Cactus wrote: >> On Feb 12, 2:30 pm, ja...@njkfrudils.plus.com wrote: >> > On Thursday 12 February 2009 13:29:33 ja...@njkfrudils.plus.com wrote: >> > > On Thursday 12 February 2009 08:54:06 ja...@njkfrudils.plus.com wrote: >> > > > As we have our first release now , I will go ahead and change the >> > > > names of the library components to mpir. I will do this in trunk >> > > > starting with r1601. It should be fairly straight forward and I >> > > > imagine the testing will take longer than doing it. I'll do the >> > > > changes one step at a time and each step will not build until I >> > > > finish. So dont expect trunk to build properly for the next few >> > > > revisions. >> > > > >> > > > Jason >> > > >> > > It now passes the usual >> > > >> > > ./configure && make && make check >> > > >> > > and with --enable-cxx >> > > >> > > I not done any thing with windows build >> > > >> > > probably a few more things to do >> > >> > rev 1612 , just done the info files as well. >> > I think this is everything except windows. >> > >> > Now to get testing.... >> > >> > Jason >> >> Hi All, >> >> Before I start the changes for Windows, I would like to be sure that >> file names won't keep changing as these can be costly for me to >> implement. >> >> It appears that we are going to keep the gmp-* files with their 'gmp-' >> prefixes rather than changing to 'mpir-' (e.g. gmp-h.in, gmp-impl.h >> gmp-mparam.h). Is this correct? >> > > At the moment all I have changed are > > gmp.h to mpir.h > gmpxx.h to mpirxx.h > libgmp.* to libmpir.* > libgmpxx.* to libmpirxx.* > gmp.info to mpir.info > > so to the user , its a new library , I've left all the internal stuff alone. > > I can change gmp-h.in gmp-impl.h gmp-mparam.h to mpir-* ? > > >> In particular, I generate gmp.h from gmp-h.in and then copy gmp.h to >> mpir.h. It appears that I don't need to change this since the gmp- >> h.in name doesn't change and I end up with both gmp.h and mpir.h >> anyway. >> >> 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 -~----------~----~----~----~------~----~------~--~---
