Cleanup project files and structure, fix all build warnings #391
Conversation
This file contains 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
itswisdomagain
force-pushed
the
generic-build
branch
from
2e7e5fb
to
b47fa8a
Compare
itswisdomagain
force-pushed
the
generic-build
branch
from
8f54434
to
3e297e4
Compare
itswisdomagain
force-pushed
the
generic-build
branch
from
3e297e4
to
37f8152
Compare
macsleven
approved these changes
May 19, 2019
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.
I created a new Xcode project, carefully moved over project files from the current codebase, deleted duplicate files and other files that were unused, restored testnet/mainnet build schemes, then copied over the new project files to the current project directory. The result is a clean project codebase without bloated files and without build warnings.
Resolves #361.