Add dependency on swiftc for %.o.%.swift rules #178
Merged
+4
−2
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Detect that swiftc has changed since the Swift file has been compiled and force it to be recompiled. The explicit rm of the target before regenerating it is needed because if the new compiler generates exactly the same bits as the old one the .o file isn't updated and the target gets stuck as being out-of-date. An explicit rm avoids that problem.
das
pushed a commit
that referenced
this pull request
Feb 21, 2017
Add dependency on swiftc for %.o.%.swift rules Signed-off-by: Daniel A. Steffen <dsteffen@apple.com>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Detect that swiftc has changed since the Swift file has
been compiled and force it to be recompiled. The explicit
rm of the target before regenerating it is needed because if
the new compiler generates exactly the same bits as the old
one the .o file isn't updated and the target gets stuck as
being out-of-date. An explicit rm avoids that problem.