如何从可运行Jar中执行.exe并实现跨平台多依赖文件打包运行

Hey there! Let's break down your problem and land on the best solution for your cross-platform Java desktop app. The short answer: sticking with a single Java application (your first idea) is absolutely the optimal choice—it keeps your codebase unified, avoids maintaining separate Windows/Mac projects, and solves your core issue of running embedded binaries with a straightforward resource extraction workflow.

The reason you can't run the .exe/.dylib directly from the JAR is simple: operating systems only execute files that exist as physical entities on the filesystem, not compressed entries inside a JAR archive. The workaround is to extract these binaries to a temporary directory first, then execute them from there. Here's a step-by-step implementation:

1. Identify the Current Platform #

First, detect which OS the app is running on to pick the right binaries:

String osName = System.getProperty("os.name").toLowerCase();
boolean isWindows = osName.contains("win");
boolean isMac = osName.contains("mac");

2. Extract Binaries to a Temporary Directory #

Create a dedicated temp folder for your app's resources, then pull the relevant files out of the JAR using the classloader. You'll want to organize your JAR resources into platform-specific folders (e.g., /windows/ for .exe/.dll, /mac/ for Unix executables/.dylib) to keep things clean.

Add this helper method to handle extraction:

private static void extractResource(String resourcePath, File outputFile) throws IOException {
    try (InputStream resourceStream = YourMainClass.class.getResourceAsStream(resourcePath);
         OutputStream fileStream = new FileOutputStream(outputFile)) {
        byte[] buffer = new byte[4096];
        int bytesRead;
        while ((bytesRead = resourceStream.read(buffer)) != -1) {
            fileStream.write(buffer, 0, bytesRead);
        }
    }
}

Then use it to extract your files:

File tempDir = new File(System.getProperty("java.io.tmpdir"), "MyAppResources");
tempDir.mkdirs(); // Create the temp folder if it doesn't exist

File executable;
if (isWindows) {
    // Extract Windows-specific files
    extractResource("/windows/myapp.exe", new File(tempDir, "myapp.exe"));
    extractResource("/windows/mydep.dll", new File(tempDir, "mydep.dll"));
    executable = new File(tempDir, "myapp.exe");
} else if (isMac) {
    // Extract Mac-specific files
    extractResource("/mac/myapp", new File(tempDir, "myapp"));
    extractResource("/mac/mydep.dylib", new File(tempDir, "mydep.dylib"));
    executable = new File(tempDir, "myapp");
    executable.setExecutable(true); // Critical: Grant execute permissions on Mac
} else {
    throw new UnsupportedOperationException("Unsupported operating system");
}

3. Execute the Extracted Binary #

Use ProcessBuilder to launch the executable, making sure to set the working directory to the temp folder so dependencies (like .dll/.dylib) are found:

ProcessBuilder processBuilder = new ProcessBuilder(executable.getAbsolutePath());
processBuilder.directory(tempDir); // Set working dir to temp folder

try {
    Process process = processBuilder.start();
    // Optional: Handle process input/output or wait for completion
    int exitCode = process.waitFor();
    System.out.println("Binary exited with code: " + exitCode);
} catch (InterruptedException | IOException e) {
    e.printStackTrace();
}

4. Cleanup (Optional) #

You can delete the temp files after execution, or on app startup to clean up old resources:

private static void deleteTempFiles(File dir) {
    File[] files = dir.listFiles();
    if (files != null) {
        for (File file : files) {
            file.delete();
        }
    }
    dir.delete();
}

To give users a single file to run:

• Build a Fat JAR: Use Maven's maven-shade-plugin or Gradle's shadow plugin to package your code, dependencies, and all platform binaries into one JAR. Users can run it with java -jar your-app.jar.
• Wrap as Native Executables (for double-click convenience):
  • Windows: Use Launch4j to wrap the JAR into a .exe that users can double-click without opening a command prompt.
  • Mac: Use jpackage (built into Java 14+) to package the JAR into a native .app bundle, which integrates seamlessly with macOS.

If you decide splitting into separate Windows/Mac apps is better (e.g., for deep OS-specific UI integration), here are solid language choices:

• Windows: C# with WinForms/WPF (native feel, easy to package into .exe) or Python with PyInstaller (quick development, cross-compile if needed).
• Mac: Swift with SwiftUI/AppKit (native macOS experience) or Python with PyInstaller (same as above, packages into a .app bundle).

That said, this approach doubles your maintenance work—you'll have to sync business logic across two codebases. Only go this route if you need OS-specific features that Java can't handle well.

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