hello,banjo run fail

[aubreychao]

os=>windows7 sp1
msvc=>vs2019

Also i tried banjo toolchain install x86_64-windows-gnu,but nothing happened

[chnoblouch]

First off, I'm surprised that the toolchain even runs on Windows 7.

Secondly, it seems like the banjo2 command is working, so I'd suggest you use that since it will anyway replace the banjo command in the future. The interface of banjo2 is documented less well, but you should be able to figure it out by running banjo2 --help.

[aubreychao]

First off, I'm surprised that the toolchain even runs on Windows 7.

Secondly, it seems like the banjo2 command is working, so I'd suggest you use that since it will anyway replace the banjo command in the future. The interface of banjo2 is documented less well, but you should be able to figure it out by running banjo2 --help.

Oh,banjo2 is future,i just thought banjo2 was outdated haha.

[aubreychao]

hey,how can i add a new toolchain by banjo2.i have gcc and clang installed.

[chnoblouch]

hey,how can i add a new toolchain by banjo2.i have gcc and clang installed.

You only need to add a toolchain if you want to cross-compile for another platform (e.g. from Windows to Linux), otherwise the host toolchain gets detected automatically when running banjo2 for the first time:

$ banjo2 run
Setting up toolchain for target aarch64-macos
Locating macOS toolchain...
  Found xcodebuild: /usr/bin/xcodebuild
  Found xcrun: /usr/bin/xcrun
  Found Xcode linker: /Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/ld
  Found macOS SDK: /Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX.sdk
  Caching toolchain...
Compiling...
Linking...
Build finished (1.48 seconds)
Running...
Hello, World!

[aubreychao]

hey,how can i add a new toolchain by banjo2.i have gcc and clang installed.

You only need to add a toolchain if you want to cross-compile for another platform (e.g. from Windows to Linux), otherwise the host toolchain gets detected automatically when running banjo2 for the first time:

$ banjo2 run
Setting up toolchain for target aarch64-macos
Locating macOS toolchain...
  Found xcodebuild: /usr/bin/xcodebuild
  Found xcrun: /usr/bin/xcrun
  Found Xcode linker: /Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/ld
  Found macOS SDK: /Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX.sdk
  Caching toolchain...
Compiling...
Linking...
Build finished (1.48 seconds)
Running...
Hello, World!

I’ve installed VS2019, Clang 21, GCC 15 and Banjo 2. The MSVC toolchain is detected and set as the active one when running the project, yet I can’t launch the program directly with the banjo2 run command. I have to manually open the VS2019 Developer Command Prompt and execute the relevant commands in this console instead, which is quite inconvenient .

[chnoblouch]

I see, could you attach the output displayed when banjo2 run fails as well as your toolchain configuration? The path to the toolchain configuration is <path to banjo installation>/toolchains/x86_64-windows-msvc.json.

[aubreychao]

x86_64-windows-msvc.json

[chnoblouch]

Hmm... so far everything seems fine. Could you verify that C:/Program Files (x86)/Windows Kits/10/Lib/10.0.10240.0/lib/x64 contains kernel32.lib and the other Windows libraries?

It looks like you've compiled Banjo yourself. In that case, you could also try editing line 1221 of src/cli/cli.cpp so Banjo uses the LLVM linker (lld-link.exe) instead of the one from MSVC (link.exe):

  Command command{
-     .executable = (msvc_tools_path / "link").string(),
+     .executable = "lld-link",
      .args = args,
  };

Another thing you could do is force Banjo to use the MinGW toolchain, which is of course less convenient than running banjo2 run:

banjo2 build --target x86_64-windows-gnu; ./out/x86_64-windows-gnu-debug/demo.exe

[aubreychao]

I'm away from my computer during the Spring Festival holiday. I'll check it once I get back after the holiday.
૮₍ ˶•ᴗ•˶₎ა

[aubreychao]

Hmm... so far everything seems fine. Could you verify that C:/Program Files (x86)/Windows Kits/10/Lib/10.0.10240.0/lib/x64 contains kernel32.lib and the other Windows libraries?

It looks like you've compiled Banjo yourself. In that case, you could also try editing line 1221 of src/cli/cli.cpp so Banjo uses the LLVM linker (lld-link.exe) instead of the one from MSVC (link.exe):

Command command{

• .executable = (msvc_tools_path / "link").string(),
  

• .executable = "lld-link",
  .args = args,
  

  };
  Another thing you could do is force Banjo to use the MinGW toolchain, which is of course less convenient than running banjo2 run:

banjo2 build --target x86_64-windows-gnu; ./out/x86_64-windows-gnu-debug/demo.exe

no lib folder there

[chnoblouch]

no lib folder there

Very strange, do you know where the Windows SDK libraries (kernel32.lib, user32.lib, msvcrt.lib, etc.) are installed on your system? They don't seem to be in the usual directory where banjo2 looks for them.

[aubreychao]