Full SDK 10.0 translate for 64 and 32 bits

[TouEnMasm]

Thanks

I have added a demo64 in the first post
It's a window and an interface in 64 bits.
The zip have also two littles modifies made. (duplicate def of Hcursor)

[habran]

I was unable to setup your SDK for use on my computer :(
I am curious if anybody else except you succeeded to set it up
I think that it requires to much work and I am wondering how someone new in programming can use it
I will stick to WinInc, it is simple to use and runs without flow :t
Why use XMASM
It is more clear like this in WinInc:

Code Select Expand


@DefProto WINOLEAPI, OleCreate, stdcall, ,<:REFCLSID,:REFIID,:DWORD,:LPFORMATETC,:LPOLECLIENTSITE,:LPSTORAGE,:ptr LPVOID>, 28

than this in SDK:

Code Select Expand

OleCreate PROTO :DWORD ,:DWORD ,:DWORD ,:XMASM ,:XMASM ,:XMASM ,:XMASM

[TouEnMasm]

I was unable to setup your SDK for use on my computer

using a batch with INCLUDE path and a single line in the code is not a setup,he can be use as it is on windows 8.1.
You can't use an API without the msdn help , the translated form don't give you enough help .
The form given by wininc just allow you to search for defines elsewhere and anywhere.this is not the case in the translated sdk who grant usable defines.
There is 161 files in the wininc and no alignment of the structure, no UNICODE
There is 1700  files in the full sdk,alignment is the same as vc++,UNICODE is supported
More,if i can say that the translated sdk can work on all windows,wininc couldn't say that (miss system switck)
More where are the defined GUID in wininc ?,from wich windows version are those files (winerror is truncated ).
It's too much generous to call the wininc a usable translate.

[habran]

It's too much generous to call the wininc a usable translate.

I would say that for SDK, because I have been using WinInc for years successfully
but I can't use SDK at all
I wish that someone tells me here that they were able to use it without difficulties

If you want someone to use it you should probably make an installer for it

I am curious why have you separated it in 3 folders, why not one?

Why XMASM?

[TouEnMasm]

I am curious why have you separated it in 3 folders, why not one?

It is the choice of microsoft,not mine.With the subdiretories,there is more than three path in the windows sdk.
Further include paths seems to be a problem for you,not for me.Perhaps have you an IDE who don't allow this?

[habran]

I use Microsoft Visual Studio Community 13 

[TouEnMasm]

Microsoft Visual Studio Community 13

For asm file couldn't be a good choice.
If you have the soluce to build an asm project with it,post it.

[habran]

I have no problem to build asm pfrojects with it as long as I use WinInc
However, I can not setup your SDK to do that
I don't think that your SDK is a bad idea but IMO you should not use .sdk extension but .inc
and you should put all headers in 1 folder and also use proper names for vars and not XASM
Do not complicate things but simplify

I'll send you one asm project later tonight

[TouEnMasm]

Microsoft Visual Studio Community 13
I'll send you one asm project later tonight

I wait for it (hope it will be not to much later,before the next version)

[habran]

Did you look in 64 Bit Assembler topic?
I couldn't post it here because of the limitation ::)

[TouEnMasm]

It's a joke ?

Give me a link where it is!

[habran]

http://masm32.com/board/index.php?topic=3902.0

[satpro]

Give the guy a break.

[TouEnMasm]

For those who want to use visual studio to build an asm project,there is a problem to solve explain here.
http://masm32.com/board/index.php?topic=4470.msg47890#msg47890
The include paths are not send  to the compiler.
The use of an IDE dedicated to masm is better than visual studio,there is more help and windbg is an excellent debugger.

---------------------------------------------------------------------------------------------------------------

Quote
jwasm.exe /c -win64 -Zp8 /nologo /Zi /Fo"x64\Release\Win64_8.obj" /Fl"" /I "H:\sdkrc81\shared" /I "H:\sdkrc81\um" /I "H:\sdkrc81\vc" /W2 /coff 
All seems OK but:
At compile , couldn't find ...

The debug log file show this command line received:
Quote
fenetre.log
         jwasm.exe /c /nologo /Zi /Fo"Debug\Win64_8.obj" /W2 /coff   Win64_8.asm
The include paths had diseappeared from the command line,Any idea ?????????
Modify message

[TouEnMasm]

This file is enough to do a test

    .486                                    ; create 32 bit code
    .model flat, stdcall                    ; 32 bit memory model
    option casemap :none                    ; case sensitive

    include \masm32\include\kernel32.inc


    .code                       ; Tell MASM where the code starts

; «««««««««««««««««««««««««««««««««««««««««««««««««««««««««««««««««««««««««

start:                          ; The CODE entry point to the program

invoke ExitProcess,0
; «««««««««««««««««««««««««««««««««««««««««««««««««««««««««««««««««««««««««

end start                       ; Tell MASM where the program ends

The upper code had no problem at compile
Now this one ......

    .486                                    ; create 32 bit code
    .model flat, stdcall                    ; 32 bit memory model
    option casemap :none                    ; case sensitive

    include kernel32.inc


    .code                       ; Tell MASM where the code starts

; «««««««««««««««««««««««««««««««««««««««««««««««««««««««««««««««««««««««««

start:                          ; The CODE entry point to the program

invoke ExitProcess,0
; «««««««««««««««««««««««««««««««««««««««««««««««««««««««««««««««««««««««««

end start                       ; Tell MASM where the program ends

The upper code need an include path working