Jwasm 2.14

[TouEnMasm]

Hello,
It is not really easy to found so I put the link here

https://github.com/Baron-von-Riedesel/JWasm


New Msvc64.mak for vs2019 is provided 

[_japheth]

> New Msvc64.mak for vs2019 is provided 

Yes. However, it works with the "Native Tools Command Prompt" only.

I'd like to also supply a makefile that could be opened inside the IDE - socalled "Open Folder" development, where you can define "build tasks" (JSON scripts) and attach them to a makefile. My tries so far were not successful, I could't convince VS Community to generate a 64-bit jwasm - this intransparency is the main reason why I don't like IDEs anymore.

[hutch--]

Build it with a batch file, solves all of those problems. That is how I built your older versions.

[_japheth]

Build it with a batch file, solves all of those problems. That is how I built your older versions.

That's the simplest and best approach - if you're just interested in having a working binary.

However, if you want to play with the assembler source and run the assembler inside the VC debugger, it's a bit easier if you can create and debug the executable inside the IDE.

In the meantime, I found the (minimal) correct settings.

file tasks.vs.json:

Code Select Expand


{
  "version": "0.2.1",
  "tasks": [
    {
      "taskLabel": "Task-Msvc64",
      "appliesTo": "Msvc64.mak",
      "type": "launch",
      "contextType": "build",
      "command": "nmake",
      "args": [
        "-f Msvc64.mak",
        "debug=1"
      ]
    },
    {
      "taskLabel": "Task-Msvc64",
      "appliesTo": "Msvc64.mak",
      "type": "launch",
      "contextType": "clean",
      "command": "nmake",
      "args": [
        "-f Msvc64.mak",
        "clean",
        "debug=1"
      ]
    }
  ]
}


file launch.vs.json:

Code Select Expand


{
  "version": "0.2.1",
  "defaults": {},
  "configurations": [
    {
      "type": "default",
      "project": "build\\MSVC64D\\jwasm.exe",
      "projectTarget": "",
      "name": "jwasm.exe"
    }
  ]
}


Finally, in file Msvc64.mak, you should change a line:

Code Select Expand


!if $(DEBUG)
extra_c_flags = -ZI -Od -DDEBUG_OUT
!else


[TouEnMasm]

To debug jwasm,inside visual studio ,there is a debugging setting in the properties of the project.
https://docs.microsoft.com/en-us/visualstudio/debugger/project-settings-for-a-cpp-debug-configuration?view=vs-2019
This work not so bad and is fully documented.

[TouEnMasm]

Here the visual studio soluce to debug the compiler.