Re: Assembling Visual Studio generated listing files
- From: Joseph M. Newcomer <newcomer@xxxxxxxxxxxx>
- Date: Mon, 03 Dec 2007 23:29:28 -0500
Actually, they don't do it at all well with the Platform SDK. I installed a new platform
SDK and it totally broke VS2005 because it has components incompatible with VS2005. It
turns out that the Platform SDK group is completely independent of the VS team, and
compatibility is something that at best appears to happen by accident.
The fact that I can't have a project which, with NO EFFORT on my part, can run with VS2003
and VS2005, is a sad commentary on the failure to deal with compatibility; we solved this
problem in 1977, and 30 years later, the same mistakes are being made.
joe
On Mon, 03 Dec 2007 22:12:38 GMT, Geoff <geoff@xxxxxxxxxxxxxxx> wrote:
On Mon, 3 Dec 2007 10:50:57 -0800 (PST), TahoeKid <rfdunn@xxxxxxxxxxx>Joseph M. Newcomer [MVP]
wrote:
I need to modify and assemble the assmelber listing files generated
from the VS 2005 IDE.
A test generated listing file did not assmeble 'as is'.
Has any tried this? It seems to me the listing file should assemble.
MASM 6.11 compatibility is lost with VS2005 (and presumably 2008) you
must use MASM 8.0 now. It looks like VS2005 generates .686 or blended
code and masm 6.x doesn't like the instruction set. I couldn't find
anything in VC++ 2005 IDE to select target code generation mode.
The link to the MASM 8.0 free download is here.
http://blogs.msdn.com/vcblog/archive/2006/06/08/622485.aspx
http://www.microsoft.com/downloads/details.aspx?FamilyId=7A1C9DA0-0510-44A2-B042-7EF370530C64&displaylang=en
Installation is problematic with non-Express Edition versions of
VC++2005. The installation executable looks for Express Edition and
aborts if not found. You can dig into the installer with WinZip and
extract the .cab file and then extract the tools to the appropriate
places but the whole thing is a hassle until the VC++ Team gets off
the pot and makes the installer work correctly.
If you are using the VC++ 2005 Express Edition the installation is
painless, the ML.exe and link.exe tools end up in the vc/bin/ folder.
You will still have path problems using it however, since the /Program
Files/Visual Studio 8/vc/bin folder is not on the path by default so
invoking the tool from a command line will be fun. You can create an
external tool in the Tools menu for it once you fix up the paths to
them.
I had a lot of trouble getting VC++ 6.0 to cohabit with VC++ 2005 EE.
It would be nice if the VC++ team would plan for these kinds of
configurations since there will no doubt be a lot of crossover
projects and they were able to do it for the Platform SDK and VS 6.0
so why not VS 2005 and 2008?
email: newcomer@xxxxxxxxxxxx
Web: http://www.flounder.com
MVP Tips: http://www.flounder.com/mvp_tips.htm
.
- Follow-Ups:
- Re: Assembling Visual Studio generated listing files
- From: TahoeKid
- Re: Assembling Visual Studio generated listing files
- References:
- Assembling Visual Studio generated listing files
- From: TahoeKid
- Re: Assembling Visual Studio generated listing files
- From: Geoff
- Assembling Visual Studio generated listing files
- Prev by Date: Re: XML editor using MFC
- Next by Date: Re: debug error
- Previous by thread: Re: Assembling Visual Studio generated listing files
- Next by thread: Re: Assembling Visual Studio generated listing files
- Index(es):
Relevant Pages
|
Loading
