8000 properly check for already installed NASM executable in the %NASMPATH% by GerHobbelt · Pull Request #21 · ShiftMediaProject/VSNASM · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content

properly check for already installed NASM executable in the %NASMPATH% #21

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
May 28, 2023

Conversation

GerHobbelt
Copy link
Contributor
  • properly check for already installed NASM executable in the %NASMPATH% path, e.g. NASMPATH=C:\Program Files\NASM\
  • update the NASM executable sought to the latest NASM release
  • fixed NASM exec error on MSVC (2022 / v17.16.2)

These patches made NASM work again on a fresh install of MSVC on a new system with fresh Win10 22H2 install, so I expect this to work well for others too.

Used here: https://github.com/GerHobbelt/qiqqa_tooling_devtree_snapshots/blob/main/DEVELOPERS-README.md#nasm-assembler--visual-studio-add-on

…% path, e.g. NASMPATH=C:\Program Files\NASM\
@GerHobbelt
Copy link
Contributor Author

Copy of the install procedure described there (which necessitates a working %NASMPATH%):


NASM (Assembler) + Visual Studio add-on

When missing, you'll see "missing nasm.props" errors when attempting a build.

You need to install the NASM for Visual Studio add-on:

  • First, you'll first need to install NASM by way of https://github.com/netwide-assembler/nasm --> https://nasm.us/ --> https://www.nasm.us/pub/nasm/releasebuilds/2.16.01/win64/

    • run the downloaded NASM installer As Administrator and install for Everybody.

    • add nasm to your system PATH via: Windows Explorer > This PC (right-click) > Properties > Advanced System Settings > (Advanced Tab) [Environment Variables] > System Variables > Edit > Add

    • verify that nasm is found by opening a CMD console window and typing nasm -v --> expected output: NASM version 2.16.01 compiled on Dec 21 2022

    • add the NASMPATH system environment variable pointing out your nasm.exe path via: Windows Explorer > This PC (right-click) > Properties > Advanced System Settings > (Advanced Tab) [Environment Variables] > System Variables > New

      so that the next command lists that path like this (DO NOT forget to add the trailing backslash!):

      set | grep NASM
      # --> NASMPATH='C:\Program Files\NASM\'

      The NASMPATH environment variable is used by the visual Studio NASM add-on (see below) to run the installed nasm.exe.

  • Then you can install the required Visual Studio 2022 add-on (VSNASM), which can be found at: https://github.com/ShiftMediaProject/VSNASM -- for install instruction, see the README there.

    • extract the VSNASM.zip file to a fresh directory, e.g. "C:\Users\Ger\Downloads\VSNASM" and then run a MSVC2022 CMD as Administrator via: Start > Visual Studio 2022 (open submenu in Start) > Developer Command Prompt for VS 2022 (right click) > More > Run as Administrator

    • then execute these commands (or their local equivalent!) in that console window:

      rem CD to the VSNASM extract directory you just created:
      cd C:\Users\Ger\Downloads\VSNASM
      install_script.bat
      rem :: expected output:
      rem :: 	
      rem :: Detected 64 bit system...
      rem :: Existing Visual Studio 2022 environment detected...
      rem :: Installing build customisations...
      rem :: Checking for existing NASM in your PATH...
      rem :: NASM version 2.16.01 compiled on Dec 21 2022
      rem :: Using existing NASM binary...
      rem :: Finished Successfully
      rem :: Press any key to continue . . .
      

@Sibras Sibras merged commit 7e70d3c into ShiftMediaProject:master May 28, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants
0