On May 27, 2:55 pm, Cactus wrote:
> On May 27, 2:38 pm, chrmhoffmann wrote:
>
> > > Ok, I've made a change to vsyasm.props in the MPIR repository that
> > > adds the ability to override the default vsyasm path.
>
> > > If the environment variable YASMPATH is set to the directory
> > > (includin
On May 28, 5:59 pm, "Chris Saunders" wrote:
> I know very little about the workings of Visual Studio(any version) but want
> to suggest that a meaningful error message would be useful in this
> circumstance. The "readme.txt" file in the "build.vc10" directory seems
> much improved and perhaps t
I know very little about the workings of Visual Studio(any version) but want
to suggest that a meaningful error message would be useful in this
circumstance. The "readme.txt" file in the "build.vc10" directory seems
much improved and perhaps this potential problem could be mentioned there if
a
On May 28, 12:15 pm, "Chris Saunders" wrote:
> I have now built the projects gc, p0, p3 and p4 both dll and lib using Visual
> Studio 2010 Express successfully.
Thanks for the feedback Chris.
The full release will avoid one of the issues you faced because I have
now removed illegal build conf
I have now built the projects gc, p0, p3 and p4 both dll and lib using Visual
Studio 2010 Express successfully.
Regards
Chris Saunders
--
You received this message because you are subscribed to the Google Groups
"mpir-devel" group.
To post to this group, send email to mpir-de...@googlegroups.c