Skip to content
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

VSCode Extension does not install MIPS Toolchain on MacOS #1793

Closed
5 tasks
rclement opened this issue Nov 4, 2024 · 1 comment
Closed
5 tasks

VSCode Extension does not install MIPS Toolchain on MacOS #1793

rclement opened this issue Nov 4, 2024 · 1 comment

Comments

@rclement
Copy link
Contributor

rclement commented Nov 4, 2024

Describe the bug

Trying to install the MIPS Toolchain through the PSX.Dev VSCode Extension v0.3.8 on MacOS seems to be working well but keeps failing as not being installed (cannot see the final terminal output as it is auto-closing).

The mipsel-none-elf-binutils Brew Formula installs properly though.
All other tools seems to be installed and recognized fined.

Here is the state of the Tools tab after multiple install trials:

Screenshot 2024-11-04 at 23 16 25

Expected behavior

The MIPS Toolchain is installed and recognized in the Tools tab (and the template creator enable the "create" buttons).

Steps to reproduce the bug

  1. Install PSX.Dev VSCode Extension
  2. Show Panel
  3. Go to Tools tab
  4. Try to install MIPS Toolchain

Operating System

MacOS 14.7 (Sonoma)

PCSX-Redux version

Version: bc029a7
Build: 107
Changeset: bc029a7
Date & time: 2024-10-24 07:41:10

CPU model

2,7 GHz Dual-Core Intel Core i5

GPU model & Drivers

Intel Iris Graphics 6100 1536 MB

BIOS version

OpenBIOS

Options

  • Dynarec CPU
  • 8MB
  • OpenGL GPU
  • Fastboot
  • Debugger

Iso checks

No response

Logs

No response

Additional information

After investigating the issue, I may have found the culprit in the VSCode Extension implementation:

  • The MIPS Toolchain command checks for mipsel-none-elf-g++ and mipsel-linux-gnu-g++ executable to be runnable: however both are not found in bin path after the install process
    check: () => checkCommands(
  • In the installToolchain command implementation for MacOS, the gccScriptPath variable actually points to the mipsel-none-elf-binutils.rb formula instead of the mipsel-none-elf-gcc.rb one!
    const gccScriptPath = vscode.Uri.joinPath(

So the fix seems to be as trivial as fixing the gccScriptPath variable with the proper formula path.
Trying the fix locally on my end (by directly modifying the VSCode Extension code) is working well:

Screenshot 2024-11-04 at 23 43 23

I'll submit a PR ASAP.

@rclement
Copy link
Contributor Author

rclement commented Nov 5, 2024

Fixed by PR #1794

@rclement rclement closed this as completed Nov 5, 2024
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

No branches or pull requests

1 participant