Author Topic: Jwasm 2.14  (Read 269 times)

TouEnMasm

  • Member
  • *****
  • Posts: 1531
    • EditMasm
Jwasm 2.14
« on: December 14, 2020, 07:49:08 PM »
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  :thumbsup:
« Last Edit: December 15, 2020, 01:33:48 AM by TouEnMasm »
Fa is a musical note to play with CL

_japheth

  • Regular Member
  • *
  • Posts: 36
Re: Jwasm 2.14
« Reply #1 on: December 15, 2020, 02:18:23 AM »

> New Msvc64.mak for vs2019 is provided  :thumbsup:

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.
The road to hell is paved with good intentions.

hutch--

  • Administrator
  • Member
  • ******
  • Posts: 8027
  • Mnemonic Driven API Grinder
    • The MASM32 SDK
Re: Jwasm 2.14
« Reply #2 on: December 15, 2020, 09:20:17 AM »
Build it with a batch file, solves all of those problems. That is how I built your older versions.
hutch at movsd dot com
http://www.masm32.com    :biggrin:  :skrewy:

_japheth

  • Regular Member
  • *
  • Posts: 36
Re: Jwasm 2.14
« Reply #3 on: December 15, 2020, 06:29:05 PM »
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]
{
  "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]
{
  "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]
!if $(DEBUG)
extra_c_flags = -ZI -Od -DDEBUG_OUT
!else

The road to hell is paved with good intentions.

TouEnMasm

  • Member
  • *****
  • Posts: 1531
    • EditMasm
Re: Jwasm 2.14
« Reply #4 on: December 15, 2020, 06:54:02 PM »
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.
Fa is a musical note to play with CL

TouEnMasm

  • Member
  • *****
  • Posts: 1531
    • EditMasm
Re: Jwasm 2.14
« Reply #5 on: December 21, 2020, 08:03:32 PM »

Here the visual studio soluce to debug the compiler.

Fa is a musical note to play with CL