10. Understanding the Output Folder and Files

Output Artifact	Purpose	User Action
Converted .pas files	FMX-oriented Pascal source units derived from the original VCL source.	Open in Delphi and build as part of the generated project.
Converted .fmx files	FireMonkey form definitions derived from DFM files.	Allow Delphi to load them and watch for reader errors.
Project files	The FMX project shell and startup metadata.	Open the project file in Delphi and build it.
Conversion report	Text summary of the run.	Keep it for diagnostics and engineering review.
Milestone backups	Snapshots of converter state or other preserved artifacts.	Store separately so they do not pollute source or output folders.

Project files now include a more complete FMX shell, and the generator attempts to carry along common companion assets such as .res, .ico, .manifest, and safe local project references. If the source project points at an absolute external asset outside the source tree, you should expect to verify or copy that file manually before runtime testing.

The output folder may now also contain staged runtime companions such as helper executables, DLLs, library files, or sound-font style support files. The generator adds them when it finds real candidates in the source root or in existing build-output folders such as Win32, Win64, Debug, Release, or deploy. Those files are copied to make review easier, but you still need to verify the final deployment location expected by the generated app.

A clean output folder is one of the most important habits in using the converter. Stale generated units and forms can create false problems, hide real changes, and lead Delphi to load the wrong copy of a file.