News:

Masm32 SDK description, downloads and other helpful links
Message to All Guests
NB: Posting URL's See here: Posted URL Change

Main Menu

JWASM / HJWASM with Visual Studio 2015 & Win 10 v1607

Started by pgw001, February 01, 2017, 01:56:46 AM

Previous topic - Next topic

pgw001

Folks,  bit of a newbee using the Forum, please excuse any unintended protocol problems.

Recently had to re-install Visual Studio together with latest JWASM and HJWASM downloads, I used the same install techniques as I used previously including
recopying the JWASM and HJWASM target files to the V140 Build Customisations folder.

Specifying MASM as the required compiler gives a clean compile of a sample program, specifying either JWASM or HJWASM always leads to the following:

Severity   Code   Description   Project   File   Line   Suppression State
Error   MSB3721   The command "jwasm.exe /c /nologo /Zi /Fo"Debug\Math1.obj" /Fl"ASM - Selector.lst" /I "c:\irvine" /I "c:\masm32\lib" /I "c:\masm32\include" /W1 /coff   Math1.asm" exited with code 1.   ASM - Selector   C:\Program Files (x86)\MSBuild\Microsoft.Cpp\v4.0\V140\BuildCustomizations\jwasm.targets   49

I have tried every remedial step that I know of, including switching Kaspersky Security off to no avail, I cannot move past this point.

Could anyone point out any factors that I need to consider,
Thanks in advance - pgw001   

TWell


pgw001

Tim,

Thanks for the prompt response, the Temp variable is viable.

Regards,
pgw001

jj2007

Same problem, apparently with a solution: http://stackoverflow.com/questions/33070734/error-msb3721-when-trying-to-assemble-a-simple-subtraction-program-in-assembly

IMHO Irvine is crap, and VS is both crap and an overkill for assembly programming. But of course, your teacher is always right :bgrin:

habran

Hi pgw001,
you have probably forgotten HJWasmTargets. You should copy these 3 filess and drop them here:
C:\Program Files (x86)\MSBuild\Microsoft.Cpp\v4.0\V140\BuildCustomizations
Cod-Father

pgw001

habran, jj2007,

thanks for the responses, sadly they do not address the problem.

there is no include file contention and the target file(s) were
copied to the BuildCustomizations directory ahead of time.

Any other suggestions would be appreciated

Best, pgw001