[FEATURE] Build Delphi projects

[mtsre]

Plugin Name

Pascal Flow

Plugin Version

5.0

IDE Version

JetBrains Rider 2026.2.0.2

Issue Description

Since Delphi 12 projects can be build with MSBuild, I managed to wrap building instructions for Delphi 12 projects in a csproj file for Jetbrains Rider by using a dummy CS target. Now I can build projects and errors / warnings show up and are navigable in "Build" tool window in "Build Output" tab. They won't show up in "Problems" tool window though, so features like "Quick-Fixes" are not available. The setup with the dummy is also rather hacky. I think a better integrated way of building Delphi/Pascal projects would be a great addition to Pascal Flow. Thanks for providing this plugin as Freemium.

Steps to Reproduce

No response

[meanmail]

Hi @mtsre,

Thank you for using Pascal Flow, and for such a well-argued request. You're the first person to raise the topic of building — which means your input right now carries disproportionate weight in how this ends up being designed.

Your analysis is correct, and it's worth spelling out why a .csproj wrapper can't deliver the last part no matter how much you polish it. The Build Output tab is fed by events from the build session, while the Problems tool window and quick-fixes are fed by code analysis. Compiler diagnostics only become "real" problems — with highlighting, Problems entries and quick-fixes — once they are mapped back onto the Pascal code model. That is fundamentally a job for a plugin that understands Pascal, not for a build system. So what you've hit isn't a flaw in your setup, it's its ceiling: what you already have is roughly the maximum achievable from the outside.

Here's how I picture proper integration — and this is exactly where I'd value your opinion:

1. Building Delphi projects from the IDE (.dproj, including packages, and .groupproj) and FPC/Lazarus projects (lazbuild/fpc), with configuration and platform selection, and no wrapper project.
2. Structured parsing of compiler output (DCC and FPC), published as navigable events in the Build tool window.
3. Diagnostics mapped onto Pascal files, so that errors and warnings show up in the editor and in the Problems tool window, not merely as lines in a build log.
4. Quick-fixes for the most common compiler errors — for example, E2003 "Undeclared identifier" → add the missing unit to uses.

I won't promise any timeline, but the ordering here is fairly rigid: 3 and 4 stand on top of 1 and 2.

What would help most are details of your actual work:

• Which toolchains matter to you — Delphi 12 only, or FPC/Lazarus as well?
• What do you build in practice: a single .dproj, a .groupproj, packages? Which platforms and configurations matter most (Win32/Win64, Debug/Release)?
• Rider only, or other JetBrains IDEs too?
• And since you've already walked this path: what turned out to be the least obvious part of your MSBuild setup? That kind of thing isn't discoverable from documentation, only from someone else's experience.

I'm leaving this issue open.

Thanks again for the thoughtful report!