Sublime Text 3中MASM32编译系统配置失效问题排查

Let’s walk through why your custom MASM32 build systems aren’t working and get them sorted out step by step.

First: Make Sure Your Build File is Saved Correctly #

This is the most common gotcha. Sublime Text only picks up build systems that meet two criteria:

• Saved as a .sublime-build file (e.g., name it MASM32.sublime-build)
• Stored in your Sublime Text User packages folder. On Windows, that’s usually C:\Users\[YourUsername]\AppData\Roaming\Sublime Text 3\Packages\User

If you saved it in the wrong folder or used a different file extension, Sublime won’t recognize it—even if you see it in the menu temporarily.

Fix Syntax & Configuration Issues in Your Build Files #

Both of your configs have small mistakes that are blocking them from working properly. Here’s how to fix each:

Fix 1: Your build.bat-Based Config #

Your first setup is almost there, but let’s tweak it to avoid path and encoding issues:

{
    "shell_cmd": "\"c:\\masm32\\bin\\build.bat\" \"${file_base_name}\"",
    "file_patterns": ["*.asm"],
    "file_regex": "^(..[^:]*):([0-9]+):?([0-9]+)?:? (.*)$",
    "selector": "source.asm",
    "working_dir": "${file_path}",
    "encoding": "cp1252"
}

• Encoding change: MASM32 uses Windows’ default cp1252 encoding, not UTF-8. Using UTF-8 can break output parsing and cause unexpected errors.
• Quoted paths: Wrapping build.bat in quotes ensures it works even if your MASM32 path had spaces (it doesn’t now, but it’s a safe habit).
• Simplified argument: build.bat expects just the filename without extension, and since we set working_dir to the file’s folder, ${file_base_name} is all you need.

Fix 2: Your Direct ml/link Config #

The main issue here is how you structured the command chain with shell: true. When using shell: true, the command needs to be a single string (not split into array elements). Here’s the corrected version:

{
    "shell": true,
    "cmd": ["ml /c /coff \"$file\" && link /SUBSYSTEM:WINDOWS \"${file_base_name}.obj\" && explorer.exe \"$file_path\""],
    "selector": "source.asm",
    "file_patterns": ["*.asm"],
    "working_dir": "${file_path}",
    "encoding": "cp1252"
}

• Single command string: Chaining commands with && works when the entire line is one string in the cmd array.
• Quoted file paths: Prevents errors if your .asm file is in a folder with spaces.
• Consistent encoding: Again, using cp1252 matches MASM32’s expectations.

Verify MASM32 is Set Up Properly #

Before blaming Sublime, test your build commands outside the editor:

• Open Command Prompt, navigate to your .asm file’s folder, and run c:\masm32\bin\build.bat [YourFileName] (without the .asm extension). If this fails, your MASM32 installation is missing something, or the tools aren’t in your system PATH.
• If you want to use ml and link directly, make sure they’re accessible via PATH, or use full paths in your config (e.g., replace ml with "c:\\masm32\\bin\\ml.exe").

Double-Check Build System Selection #

• Open your .asm file, go to Tools > Build System, and make sure your MASM32 build is explicitly checked (not "Automatic"). Sometimes "Automatic" fails to detect the correct system even with a proper selector.
• Use Ctrl+Shift+B to bring up the build system picker and select your config directly—this bypasses any automatic detection issues.

If you still have trouble, open the Sublime Console (View > Show Console) and look for error messages. They’ll tell you exactly where the build is failing, whether it’s a path issue, syntax error, or something else.

内容的提问来源于stack exchange，提问作者user1156544