We'd need something like this if we want to have incremental builds without having to write out a whole output file map. I'm not quite sure it's the right name because it's the directory used for intermediate files, not outputs, when swiftc is responsible for producing the output binary as well.

Comment by Raphael (JIRA)

Yes, please!

@belkadan The we probably need one parameter for tmps and one for outputs?

Interesting. I'm not sure there are many temporaries that don't make sense to persist in an incremental build, but I suppose we could support a separate directory for those.

I'm interested in trying my hand at this task, if that's alright. I have a few questions:

1. The task description mentions integrating swiftc with build systems such as Ninja. Is there another tool that integrates well with Ninja by providing something similar to this --outdir option? Does Clang provide something like this? I'd like to copy prior art if you have something in mind.

2. Based on the way --outdir behaves in the task description above, to me it sounds similar to git -C <dir>, ninja -C <dir>, and make -C <dir>. That is, an option that switches to the directory <dir> before the tool does anything else. Is that the feature that's being described here?

Thanks to z (JIRA User), who informed me that there's a clang -working-directory option. My understanding is that something similar should be implemented in Swift. I like the name of that option just fine, so I'll begin working on a swift -working-directory option.

No, this is completely different from -working-directory. That sets PWD; this is providing a place to put object files and other outputs without an output file map. We actually don't want to change PWD because search paths can be relative.

The only thing this should affect is calculating the paths of output files.

OK, I think I understand. For my own clarification, though: is it possible that the original task was describing something like -working-directory? Because, as far as I've researched so far, the output file map doesn't effect input source file paths, but the original task description describes passing an input file tmp/myexe.swift as just myexe.swift. But output file maps are only used to specify paths to object files and other build products, not source files, right?

I don't think so. Note that in the original description ../Sources/myexe.swift is still supposed to be resolved relative to the (shell's) current directory, not the output directory.

Oooh, I see! Yes, thanks, I think I was misreading it.