Hi japheth
I am trying to build x64 with VS110 expres and get always this:
C:\Program Files (x86)\MSBuild\Microsoft.Cpp\v4.0\BuildCustomizations\jwasm.targets(49,5): error MSB3721: The command "jwasm.exe /c -win64 -Zp8 /Sg /Zi /Fo"x64\Debug\AX64Edit.obj" /Fl"AX64Edit" /I "C:\x64\aInclude" /W2 /win64 /Zp8 ..\AX64Edit.asm" exited with code -1073741819.
targets(49,5) = JWASM
regards
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I'm sorry, I cannot help: I just added the VC2010CustomBuildRule.zip, but didn't test it because I don't have VC 2010. Worse, my computer has dotnet uninstalled and it's impossible to install it - so it's also impossible to install VC.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I have tested japheth's files with VS Express 2010 and have no problems.
Maybe it is your VS 2012 ? Which edition do you use, "Express for Windows 8" ?
This toolset doesn't allow the user to build native Windows applications, only Metro-sh*t.
If you want to develop native Windows applications you need the "Express for Windows Desktop" editiion.
Or maybe it is the doubled command line switches …
However, my own custom build rules are a little bit bigger than japhet's.
They are created by VS 2010, if somebody wants to compare them with japheth ones, then let me know.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
> I will stick to VS8 it works fine for asm but can not build JWasm64
I recently tried PellesC to create a 64-bit jwasm - the result is, AFAICS, better (=faster) than that created with the 64-bit Intel compiler and a lot better than the one created with MinGW64.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I tried to build asm source with masm and VS110 but has got the same error in masm.targets
I am very pissed of with MS
thay can not do anything properly
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I tried again to build x64 with pelles IDE and if I delete "_makepath" function and use "enable Microsoft extension"
I succeed to build it but it but then JWasm.exe doesn't work properly
Can you japheth please tell me how you succeeded to build it with pelles c
it is such a pain in as to create a project with pelles c
why he did it so complicated ?!!!
where is the common sense?!!!
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Ok, I did a more thorough test of the jwasm binary created by PellesC. I'm not sure about the "Initializer magnitude too large" error, it might as well be a jwasm bug. However, it turned out that float constants are not fully compatible with Masm, the least significant bit may differ.
In short: currently it's not recommended to use PellesC to create JWasm!
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Thanks Greenhorn
However, I couldn't download it because it said I reached my free limit and now I have to pay
but I swear I did not download anything yet
I wish I could have it but I don't want to pay to that people
can you please post it to masm forum
regards
habran
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Sorry, but since it isn't possible to attach files here, I have to use those so called file hosters.
Thanks for support japheth.
I've tested the wrong files. The original files from japheth doesn't work for VS2010, too.
I think I have to tidy up my HDD …
The files from japheth's custom build rules have problems with the /D switch.
They produce in the command line e.g. /D"DEBUG;_DEBUG;UNICODE;_UNICODE;_WIN64"
but it should be /D"WIN32" /D"_WIN64" /D"_DEBUG" /D"_WINDOWS" /D"_UNICODE" /D"UNICODE"
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
IMO new version of some application should logically be improvement in speed, simplicity and new useful things
it looks like Microsoft has a different "logic"
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hi japheth
I am trying to build x64 with VS110 expres and get always this:
C:\Program Files (x86)\MSBuild\Microsoft.Cpp\v4.0\BuildCustomizations\jwasm.targets(49,5): error MSB3721: The command "jwasm.exe /c -win64 -Zp8 /Sg /Zi /Fo"x64\Debug\AX64Edit.obj" /Fl"AX64Edit" /I "C:\x64\aInclude" /W2 /win64 /Zp8 ..\AX64Edit.asm" exited with code -1073741819.
targets(49,5) = JWASM
regards
I'm sorry, I cannot help: I just added the VC2010CustomBuildRule.zip, but didn't test it because I don't have VC 2010. Worse, my computer has dotnet uninstalled and it's impossible to install it - so it's also impossible to install VC.
I have tested japheth's files with VS Express 2010 and have no problems.
Maybe it is your VS 2012 ? Which edition do you use, "Express for Windows 8" ?
This toolset doesn't allow the user to build native Windows applications, only Metro-sh*t.
If you want to develop native Windows applications you need the "Express for Windows Desktop" editiion.
Or maybe it is the doubled command line switches …
However, my own custom build rules are a little bit bigger than japhet's.
They are created by VS 2010, if somebody wants to compare them with japheth ones, then let me know.
Hi greenhorn70
I have instolled VS 2012 "Express for Windows Desktop" editiion because of the window 7
can you post here yours please
VS 2012 "Express for Windows Desktop" editiion is very good one because it can build JWasm 64 bit
but I would like to build asm 64 bit as well
thanks japheth
thanks greenhorn70
With VS 2010 it is also possible to build 64bit targets, in C/C++ ASM …
Here is the zip with the files:
http://ul.to/61fng9vd
Regards
Thanks greenhorn70
However, I have got the same error
I am very disappointed with VS 2012
I was going to by it but now I changed my mind
I will stick to VS8 it works fine for asm but can not build JWasm64
regards
> I will stick to VS8 it works fine for asm but can not build JWasm64
I recently tried PellesC to create a 64-bit jwasm - the result is, AFAICS, better (=faster) than that created with the 64-bit Intel compiler and a lot better than the one created with MinGW64.
japheth, did you build it with his IDE?
I tried before but did not succeed
I actually never succeed to build anything with it
and I stopped trying
I tried to build asm source with masm and VS110 but has got the same error in masm.targets
I am very pissed of with MS
thay can not do anything properly
I tried again to build x64 with pelles IDE and if I delete "_makepath" function and use "enable Microsoft extension"
I succeed to build it but it but then JWasm.exe doesn't work properly
Can you japheth please tell me how you succeeded to build it with pelles c
it is such a pain in as to create a project with pelles c
why he did it so complicated ?!!!
where is the common sense?!!!
> Can you japheth please tell me how you succeeded to build it with pelles c
I launched from the cmdline
nmake -f PellesC.mak amd64=1
I have got the same error as with IDE:
Error A2172: Initializer magnitude too large:
Ok, I did a more thorough test of the jwasm binary created by PellesC. I'm not sure about the "Initializer magnitude too large" error, it might as well be a jwasm bug. However, it turned out that float constants are not fully compatible with Masm, the least significant bit may differ.
In short: currently it's not recommended to use PellesC to create JWasm!
It is not JWasm bug because when I build it with VS110 it works beautifully
PellesC is shitty C
it is not able to build anything and is not compatible with anything
Hi habran,
please test these custom build rules for VS …
http://ul.to/r1x9w8zi
Greenhorn
Thanks Greenhorn
However, I couldn't download it because it said I reached my free limit and now I have to pay
but I swear I did not download anything yet
I wish I could have it but I don't want to pay to that people
can you please post it to masm forum
regards
habran
I added it to the jwasm folder on my site
http://japheth.de/Download/JWasm/
Thanks japheth
however, error is still the same
it is the same with VS10 or VS11
Sorry, but since it isn't possible to attach files here, I have to use those so called file hosters.
Thanks for support japheth.
I've tested the wrong files. The original files from japheth doesn't work for VS2010, too.
I think I have to tidy up my HDD …
The last files I've uploaded work in VS 2010.
Take a look at the picture:
http://www.pic-upload.de/view-16415704/VSCustomBuildJWASM.jpg.html
x64 build with VC 10 xpress
The files from japheth's custom build rules have problems with the /D switch.
They produce in the command line e.g. /D"DEBUG;_DEBUG;UNICODE;_UNICODE;_WIN64"
but it should be /D"WIN32" /D"_WIN64" /D"_DEBUG" /D"_WINDOWS" /D"_UNICODE" /D"UNICODE"
Here is the project configuration dialog …
No. o.O It isn't …
The IMG tag seems to be broken …
http://www.pic-upload.de/view-16417083/ProjConfig.jpg.html
Thanks Greenhorn
I am still unsuccesfully trying to compile
IMO new version of some application should logically be improvement in speed, simplicity and new useful things
it looks like Microsoft has a different "logic"
I finally managed to install MSVS 2010 and tried the files in VS2010CustomBuildRule.zip. They didn't work - there were 2 backslashes missing.
A corrected version is now included in v2.09 - should work in general, but might still have this and that issue.