Re: [mpir-devel] Simplifying MSVC projects: using PropertySheets

2015-11-21 Thread SeVlaT
For example, the same way as I did in my previous pull request: https://github.com/sevlat/mpir/commit/591918b046f251743aa3376df02bfcbd6b2220ca I can do it again but not now. Maybe tomorrow. -- You received this message because you are subscribed to the Google Groups "mpir-devel" group. To unsub

Re: [mpir-devel] Simplifying MSVC projects: using PropertySheets

2015-11-21 Thread Brian Gladman
On 21/11/2015 21:30, SeVlaT wrote: > Thank you very much, Brian! > > I have observed your commits during this week. > I see that many files (*.bat, *.c, *.h) was moved to build.vc directory > and became common. Probably this structure will be much clear and easier > to support. > >> However I hav

Re: [mpir-devel] Simplifying MSVC projects: using PropertySheets

2015-11-21 Thread SeVlaT
Thank you very much, Brian! I have observed your commits during this week. I see that many files (*.bat, *.c, *.h) was moved to build.vc directory and became common. Probably this structure will be much clear and easier to support. > However I have not adopted an approach that relies on propert

Re: [mpir-devel] Open source high precision math tools built under 64 bit Windows operating systems state of the union

2015-11-21 Thread 'Bill Hart' via mpir-devel
We've now committed fixes for the howell_form issue. We haven't sorted out the fmpz_lll issue yet. Bill. On 20 November 2015 at 23:14, Bill Hart wrote: > Thanks. > > We think we have a fix on the way for the Howell form bug. However I don't > see the problem at all for the fmpz_lll bug. > > Som

Re: [mpir-devel] Simplifying MSVC projects: using PropertySheets

2015-11-21 Thread Cactus
a On Saturday, 7 November 2015 22:50:22 UTC, SeVlaT wrote: > > Hi. > > This becomes an issue if people don't explicitly specify the libraries >> that they are going to use. But in our case we explicitly set up the >> correct libraries for Release and Debug so we don't make any use of the >> MSP