Two source folders?

[atarwn]

Why are there two separate source folders — src/ and source/ — in the RetroMCP workflow?

This is extremely confusing and counterproductive. In a typical development workflow, there should be a single canonical source directory. Having both folders present with overlapping or similar content makes it very hard to track down where changes should be made, and whether they’re being picked up by the toolchain at all.

• Is this duplication intentional or just legacy bloat?
• Which folder is actually used by recompile?
• Is it safe to remove or ignore source/ entirely?
• Why not consolidate everything into src/ for simplicity?

[atarwn]

OK, I see, the source/ folder appears when decompiling. But then what? Why do I need it after decompilation?

[Lassebq]

It's for generating patches. You have to compare against something to make a diff.