Skip to content

feat: Add output directory configuration for compiled files#1258

Open
Sorata-kanda wants to merge 1 commit intoformulahendry:masterfrom
Sorata-kanda:feature/output-directory
Open

feat: Add output directory configuration for compiled files#1258
Sorata-kanda wants to merge 1 commit intoformulahendry:masterfrom
Sorata-kanda:feature/output-directory

Conversation

@Sorata-kanda
Copy link

Problem

When running compiled languages (C++, Java, etc.), Code Runner creates executable files in the same directory as source files, cluttering the workspace.

Solution

Added code-runner.outputDirectory configuration to organize compiled files into a dedicated folder (e.g., bin/, build/).

Features

  • New setting: code-runner.outputDirectory
  • Automatic directory creation
  • Cross-platform support (Windows, Linux, macOS)
  • Supports: C, C++, Java, Rust, D, Pascal, Fortran, Objective-C, VB.NET, Kotlin
  • Fully backward compatible (empty by default)

Usage

{
  "code-runner.outputDirectory": "bin"
}

- Add new configuration option 'code-runner.outputDirectory'
- Automatically create output directory before compilation
- Support for C, C++, Java, Rust, D, Pascal, Fortran, Objective-C, VB.NET, and Kotlin
- Cross-platform support (Windows, Linux, macOS)
- Backward compatible - empty by default

This feature helps keep source directories clean by organizing compiled
files (.exe, .class, .o, etc.) into a dedicated output folder.
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

Successfully merging this pull request may close these issues.

1 participant