Update compilation instructions #645
Merged
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
|
No comments yet, so I'm merging this. Make a new issue/PR in case corrections are needed. |
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.
There are some things I'm unsure about (see below for list) but the general aim for this is to simplify the compilation instructions enough that we don't need separate wiki pages for it anymore.
Things I'm unsure of (please comment/correct if necessary):
5. Build and RunandCompiling...is nearly unchanged, but I don't know how relevant that still ismake; ./game/ultrastarreally not work on MacOS?Most of the installation-related things (like
make install) are deliberately deleted, since it's generally a bad idea to install things like that. The AUR version already creates a regular package, I don't know that works for other distro's. Ideally commands to create proper shareable/installable packages (like the one for MacOS in the above list?) should eventually be part of some more general section with notes on how to do a release, once I've figured out what the Windows commands for it are.