如何在本地独立运行的R Shiny应用中调用exe程序？

Absolutely! You can absolutely trigger your local executable from an R Shiny app—this works similarly to using system() or system2() in your R console, but there are critical tweaks to account for Shiny's reactive, interactive environment.

Basic Implementation #

The core idea is to wrap your system()/system2() call inside a reactive trigger (like a button click) so it only runs when the user initiates it. Here's a quick breakdown:

• Use an actionButton() in your UI to let users trigger the EXE.
• In your server logic, use observeEvent() to listen for the button click and run the EXE command.

Critical Things to Watch For #

Always Use Absolute Paths #

Shiny's working directory might not match your R console's default directory (e.g., if you launch the app from a shortcut or RStudio's "Run App" button). Never rely on relative paths for your EXE. Instead:

• Use normalizePath() to convert relative paths to absolute ones, or
• Hardcode the full path (e.g., C:/my_apps/my_program.exe on Windows, /home/user/my_program on Linux/macOS)

Avoid Freezing the Shiny UI #

By default, system() runs synchronously—meaning your Shiny app will freeze until the EXE finishes executing. If your EXE takes more than a few seconds to run, use asynchronous execution:

• On Windows: Add start /B to your command to run it in the background:

  system2("cmd.exe", args = c("/c", "start /B", "C:/path/to/your.exe"))
  

• On Linux/macOS: Append & to run it in the background:

  system2("/path/to/your.exe", args = "", wait = FALSE)
  

• For more control (like monitoring if the process finished), use the processx package's process$new() function—it’s far more robust for async tasks in Shiny.

Permissions Matter #

If your EXE requires admin privileges, you’ll need to launch your R/RStudio session with admin rights first (right-click > "Run as administrator" on Windows, use sudo on Linux). Shiny inherits the permissions of the R process it runs in.

Capture Output (If Needed) #

If you want to display the EXE’s output or error messages in your Shiny app, use system2() with stdout = TRUE and stderr = TRUE to capture the output:

exe_output <- system2("C:/path/to/your.exe", args = "--your-arguments", stdout = TRUE, stderr = TRUE)

You can then render this output in the UI using verbatimTextOutput() or textOutput().

Full Working Example #

Here’s a complete minimal Shiny app that triggers an EXE, captures its output, and displays it:

library(shiny)

ui <- fluidPage(
  titlePanel("Run Local EXE from Shiny"),
  actionButton("run_exe", "Launch Executable"),
  verbatimTextOutput("exe_results")
)

server <- function(input, output) {
  # Define absolute path to your EXE
  exe_path <- normalizePath("C:/path/to/your_program.exe", mustWork = TRUE)
  
  observeEvent(input$run_exe, {
    # Run the EXE and capture output
    output$exe_results <- renderPrint({
      cat("Running executable...\n")
      results <- system2(exe_path, args = "", stdout = TRUE, stderr = TRUE)
      cat(paste(results, collapse = "\n"))
    })
  })
}

shinyApp(ui, server)

Quick Testing Tip #

Before integrating into Shiny, always test your system2() call directly in the R console to confirm it works. This helps rule out path or permission issues before debugging in the Shiny environment.

内容的提问来源于stack exchange，提问作者H.Ji