On Mar 20, 4:41 pm, "jason" <[email protected]> wrote: > ----- Original Message ----- > From: "Cactus" <[email protected]> > To: "mpir-devel" <[email protected]> > Sent: Sunday, March 20, 2011 2:11 PM > Subject: [mpir-devel] Re: MSVC command line build > > On Mar 20, 1:19 pm, "jason" <[email protected]> wrote: > > Also in the batch script , I've assumed that cl.exe and yasm.exe are at > > some > > fixed location , we just need some code to find out where they really are > > on > > the system or we could just assume they are already in PATH. > > The existing batch script which calls the project/solution files is still > > needed if we want to automate testing of the GUI builds. > > > Jason > > > ----- Original Message ----- > > From: "jason" <[email protected]> > > To: <[email protected]> > > Sent: Sunday, March 20, 2011 1:12 PM > > Subject: Re: [mpir-devel] Re: MSVC command line build > > > >I haven't done the C++ stuff yet , but I can't see it being difficult. > > > This should also backport to MPIR-2.3 , 2.2 and 2.1 if we want to , this > > > should be pretty trivial. > > > > Jason > > > > ----- Original Message ----- > > > From: "jason" <[email protected]> > > > To: <[email protected]> > > > Sent: Sunday, March 20, 2011 1:02 PM > > > Subject: Re: [mpir-devel] Re: MSVC command line build > > > >> Hi > > > >> In svn , in the directory win there is a MSVC command line build that > > >> is > > >> independant of MSVC project/solution files. > > >> This should work on any MSVC , ie 2010 2008 2005? and the free versions > > >> I've done a > > >> make > > >> make_clean > > >> make_check > > > >> There are still a few minor bits to sort out , at the moment the script > > >> is fixed to nehalem 64 bit build(see below) , a static lib , assumes > > >> stdint is availible , seems to create an endless %PATH% after a number > > >> of > > >> runs , t-mpz_reuse wont build , t-locale wont build , and a few other > > >> hacks , make try speed tune still to do , but mostly it's there and it > > >> works > > > >> We need some code to select the mpn path dependant on cpu and this > > >> could > > >> be shared with the GUI builds and also Linux if we used python say(or > > >> C) > > > >> Jason > > > >> -- > > >> You received this message because you are subscribed to the Google > > >> Groups > > >> "mpir-devel" group. > > >> To post to this group, send email to [email protected]. > > >> To unsubscribe from this group, send email to > > >> [email protected]. > > >> For more options, visit this group at > > >>http://groups.google.com/group/mpir-devel?hl=en. > > > > -- > > > You received this message because you are subscribed to the Google > > > Groups > > > "mpir-devel" group. > > > To post to this group, send email to [email protected]. > > > To unsubscribe from this group, send email to > > > [email protected]. > > > For more options, visit this group at > > >http://groups.google.com/group/mpir-devel?hl=en. > > Nice work Jason! > > The build will only work on Visual Studio 2008 because some of the > paths in your baatch files are specific to VS 2008 (e,g. > VS90COMNTOOLS). > > As far as I can see you are not setting up the compiler environment, > which means that it cannot find my compiler on VS 2010. > > ------------------ > Yeah , I wasn't sure what the paths were to set up , isn't VS2010 path the > same but with VS100COMNTOOLS instead? > --------------- > > But I am impressed with how far you have got! > > Brian > > -- > You received this message because you are subscribed to the Google Groups > "mpir-devel" group. > To post to this group, send email to [email protected]. > To unsubscribe from this group, send email to > [email protected]. > For more options, visit this group > athttp://groups.google.com/group/mpir-devel?hl=en.
With 'comspec' as the location of the Winndows DOS shell (%SystemRoot% \system32\cmd.exe), the three environemnts on my system are: Visual Studio x64 Win64 Command Prompt (2010): %comspec% /k ""C:\Program Files (x86)\Microsoft Visual Studio 10.0\VC \vcvarsall.bat"" amd64 Visual Studio x64 Cross Tools Command Prompt (2010): %comspec% /k ""C:\Program Files (x86)\Microsoft Visual Studio 10.0\VC \vcvarsall.bat"" x86_amd64 Visual Studio Command Prompt (2010): %comspec% /k ""C:\Program Files (x86)\Microsoft Visual Studio 10.0\VC \vcvarsall.bat"" x86 These are (-> is 'targetting'): x64 -> x64 x64 -> x86 x86 -> x86 -- You received this message because you are subscribed to the Google Groups "mpir-devel" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/mpir-devel?hl=en.
