Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[SR-6079] Incremental compilation should not require an output file map #48634

Open
modocache mannequin opened this issue Oct 6, 2017 · 0 comments
Open

[SR-6079] Incremental compilation should not require an output file map #48634

modocache mannequin opened this issue Oct 6, 2017 · 0 comments
Labels
compiler The Swift compiler in itself improvement legacy driver Area → compiler: the integrated C++ legacy driver. Succeeded by the swift-driver project

Comments

@modocache
Copy link
Mannequin

modocache mannequin commented Oct 6, 2017

Previous ID SR-6079
Radar None
Original Reporter @modocache
Type Improvement
Additional Detail from JIRA
Votes 0
Component/s Compiler
Labels Improvement, Driver
Assignee None
Priority Medium

md5: 5f352ec7ad8e8ae14f428f601664bb7d

relates to:

  • SR-327 Add --outdir argument to swiftc

Issue Description:

Several FIXME in the Swift repository mention that compilation with -incremental should not require the -output-file-map option to be specified:

Instead, the notes indicate that another way to specify a build record and where to put intermediates should be used. What should this other way be? What are the downsides of using an output file map?

@swift-ci swift-ci transferred this issue from apple/swift-issues Apr 25, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
compiler The Swift compiler in itself improvement legacy driver Area → compiler: the integrated C++ legacy driver. Succeeded by the swift-driver project
Projects
None yet
Development

No branches or pull requests

0 participants