MASM32 installer claims v11r,
not sure in reference to what though,
i tried NASM as alternative only to get a heap of other issues;
i could barely handle the basic troubleshooting; let alone introducing an unknown application in the mix,
also too scared Andres will yell at me 😉
ATB
Chris
Problems building NSIS
62 posts
That version is new enough, it should work fine. This sounds like an environment path issue, scons obviously can't find a compiler for the assembly file for system.dll.
Just out of curiosity, try using VS2005 Express Edition instead of the 2003SDK, MSToolKit, and MASM. Do you absolutely need Windows 95/98/ME compatibility? This is generally for two reasons: using an old toolchain to get said compatibility; and for testing/debugging.
I use VS2008 as it's a nice compromise between compatibility and newness; and install size/time. I think that VS2010 onwards is just bloat, although the code editor in VS2012 is pretty cool.
Just out of curiosity, try using VS2005 Express Edition instead of the 2003SDK, MSToolKit, and MASM. Do you absolutely need Windows 95/98/ME compatibility? This is generally for two reasons: using an old toolchain to get said compatibility; and for testing/debugging.
I use VS2008 as it's a nice compromise between compatibility and newness; and install size/time. I think that VS2010 onwards is just bloat, although the code editor in VS2012 is pretty cool.