cargo support.

[davehorner]

hey there,
just wondering what projects you are using this with that I might give it a go and have success.

I tried pointing it at a local repo and it tells me no repo specified. I'm not sure what's up with that. I would like to allow this to work with rust cargo. Is there a config file I can edit? There's no way to see the settings that I see.

I tried git@github.com:davehorner/cargo-e.git and the local path on my disk. The url/path just sits in the box when I hit return. Then it tells me Cannot sync, no repo specified.

[nbolton]

Hey, I think #14 should address cargo support, which I think is a good idea, or we could add a cargo option explicitly so it's a bit easier to configure.

As for the repo error, that seems like a separate bug/feature request so I'll raise that now.

Edit: Raised #16

[nbolton]

just wondering what projects you are using this with that I might give it a go and have success.

Forgot to address this question.

I'm using it with Deskflow right now, a C++ project which is what I built it for. I also tried using it with some Node projects but the hard-coded CMake stuff is a pain which is why I plan to make it optional.

[davehorner]

I'm working on it right now. I have it running cargo; I am working on getting a list of targets.

// Check if Cargo.toml exists in the repo root
  const git = getGitAPI();
  const repoObj = git.repositories.find((r) => path.basename(r.rootUri.fsPath) === repo);
  if (repoObj) {
    const cargoFiles = await vscode.workspace.findFiles("**/Cargo.toml");
    console.debug(`${logTag} Found Cargo.toml files:`, cargoFiles.map(f => f.fsPath));
    if (cargoFiles.length === 0) {
      vscode.window.showErrorMessage(`${extensionName}: No Cargo.toml files found in the workspace.`);
      return;
    }

    const selectedFile = await vscode.window.showQuickPick(
      cargoFiles.map((file) => ({
        label: path.basename(file.fsPath),
        description: file.fsPath,
        filePath: file.fsPath,
      })),
      {
        placeHolder: "Select a Cargo.toml file",
      },
    );

    if (!selectedFile) {
      vscode.window.showErrorMessage(`${extensionName}: No file selected.`);
      return;
    }

    const targetName = await vscode.window.showInputBox({
      prompt: "Enter the target name (optional)",
      placeHolder: "e.g., my-target",
    });

    const selectedDir = path.dirname(selectedFile.filePath);
    console.log(`${cargoLogTag} Found Cargo.toml, running 'cargo-e' in ${selectedDir}`);
    const terminal = vscode.window.createTerminal({
      name: "Cargo Build",
      cwd: selectedDir,
    });
    terminal.show();
    const cargoCommand = targetName ? `cargo-e --manifest-path ${selectedFile.filePath} --target ${targetName}` : `cargo-e --manifest-path ${selectedFile.filePath}`;
    terminal.sendText(cargoCommand);

    // Send WebSocket message to synchronize with other systems
    sendMessage({
      type: "cargo-e",
      data: {
        manifestPath: selectedFile.filePath,
        target: targetName,
      },
    });
    return;
  }

  // Check if CMakeLists.txt exists in the repo root
  const cmakeFiles = await vscode.workspace.findFiles("**/CMakeLists.txt");
  if (cmakeFiles.length > 0) {
    console.log(`${logTag} Found CMakeLists.txt files:`, cmakeFiles.map(f => f.fsPath));
    console.log(`${logTag} CMake configure`);
    await vscode.commands.executeCommand("cmake.configure");

    // Wait a moment for CMake to finish up (or we get "already running" errors).
    console.log(`${logTag} Waiting for CMake`);
    await new Promise((resolve) => setTimeout(resolve, 1000));

    console.log(`${logTag} CMake build`);
    await vscode.commands.executeCommand("cmake.build");
  } else {
    vscode.window.showErrorMessage(`${extensionName}: No CMakeLists.txt files found in the workspace.`);
  }

I am going to extend cargo-e to return a json array of targets or somethig...haven't gotten there quite yet. the above code is just to show you what I'm thinking about, it doesn't work yet. :)

essentially suggesting searching for the CMake files or the Cargo.tomls and allow selection of the file to operate on.

[davehorner]

I have the git extension installed. I'm still not quite sure how it works; but I open the git repo in code it works for the repo I'm in and that's fine.

[nbolton]

I have the git extension installed. I'm still not quite sure how it works; but I open the git repo in code it works for the repo I'm in and that's fine.

Maybe we could discuss the git repo stuff on the other issue:

• More intuitive repo input #16

That may make the 2 different threads of thought easier to follow, even though they're a bit intertwined.

[nbolton]

the above code is just to show you what I'm thinking about

Cool, looking forward to a PR! 😄

essentially suggesting searching for the CMake files or the Cargo.tomls and allow selection of the file to operate on.

Yeah that sounds sensible.

[davehorner]

#17