On May 27, 11:22 am, Cactus <[email protected]> wrote: > On May 27, 10:13 am, chrmhoffmann <[email protected]> wrote: > > > Hi, > > > I am building with vs2010 and the build works fine. I have just a > > question regarding the vsyasm.exe. I don't really like the idea that I > > have to put the vsyasm.exe in the visual studio installation path. > > Can't the solution just pick whatever vsyasm.exe that is in the PATH? > > Or at least have it configurable with envinronment variable? Some > > users may not have administrator rights on their development boxes and > > can't modify the installation. > > Hi Chris, > > You can change the vsyasm location by editing the vsyasm path set in > the <CommandLineTemplate> line in the vsyasm.props file. > > The use of the VC++ tools path is a convenient location because this > is where the default path where the IDE looks for tools. > > I'll look at the possibility of allowing an environment variable to > override the default.
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 (including the final backslash) where vsyasm is located, this will override the default vsyasm location. 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 at http://groups.google.com/group/mpir-devel?hl=en.
