Make install #27
Open
Make install #27
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
|
Thanks for this! Does it make sense to use /usr/local for the binaries but just /usr for the data? (One reason I didn't bother with adding an install: before is that I don't like having to think about this.) |
|
No, it doesn't make much sense, but since paths are hardcoded on the source I thought I could just automate it out just as-is. I can rework it to make it more consistent and use DESTDIR everywhere (even for source code paths). That shouldn't mean so much work. That would even be useful as a first step towards packaging :) I'll get back to you with a new proposal. |
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.
Implement a basic install target to automate initial pommed-light installation.