I installed Visual C++ 2010 express on my pc, so I got the
new set of tools [ML, LINK, LIB, CL...] version 10.
If I'd like to use these new tools instead of ML 6.14 that is
the default assembler in MASM32 package, what do you
suggest?
Is it better do have two separate directories, \masm32 in a disk and
the new tools in a new one? Or what?
How do I make the new tools the default for compiling and linking?
Probably this is not the first time the question arises, but maybe somebody
else can use these information.
Thanks
Frank
an backup of the \bin folder may be useful, but is not necessary. You need only to copy
ml.exe, link.ex, lib.exe, mspdbsrv.exe, msobj100.dll, mspdb100.dll, mspdbcore.dll
to the \bin folder.
Quote from: qWord on May 04, 2010, 09:55:58 PM
an backup of the \bin folder may be useful, but is not necessary. You need only to copy
ml.exe, link.ex, lib.exe, mspdbsrv.exe, msobj100.dll, mspdb100.dll, mspdbcore.dll
to the \bin folder.
Thanks qWord, :U
I'll try it, renaming existing tools to ML_OLD and so on, you never know :P
I tried with a sample program and it works fine :U
Now I'm almost ready for programming in MASM32 :lol
Frank,
BEWARE, its addictive :bg
The current binaries from VC2010 work fine with the rest of the MASM32 stuff. If you like to suffer the VC IDE, I think some of the members have worked out how to configure it for MASM.
Quote from: qWord on May 04, 2010, 09:55:58 PM
an backup of the \bin folder may be useful, but is not necessary. You need only to copy
ml.exe, link.ex, lib.exe, mspdbsrv.exe, msobj100.dll, mspdb100.dll, mspdbcore.dll
to the \bin folder.
I personally tried it this way myself and ran into issues with batch files looking for the DLL in the current directory that called link.exe, not in the directory link.exe was in... i personally just copied mspdb100.dll, into C:\windows\system32, but editing your "path" environmental variable to include your masm bin this should be ok, or your common7\IDE directory.
Quote
You need only to copy
ml.exe, link.ex, lib.exe, mspdbsrv.exe, msobj100.dll, mspdb100.dll, mspdbcore.dll
If you have resources you may need "cvtres.exe" as well, which has a strange dependency on "msvcr100.dll" and "msvcr100_clr0400.dll" but you can use "cvtres.exe" from the 9.x serie that does not have that.
They really have made Visual Studio easier to use with MASM projects in VS 2008 and even more so in VS 2010.