Open
Conversation
|
@romainmenke Maybe another/better solution is to create a header file dynamicly on the built process to read the version and maybe add the commit hash from another file, like other/popular tools do it, sothat its not required to edit the guetzli.cc on every version change |
Author
|
@gtuk c++ is not my strong suit, thought I would get the ball rolling by adding the flag to the cli already. Do you have a reference for the method you describe? |
|
@romainmenke i had something like this http://stackoverflow.com/a/1843783 or this http://m.linuxjournal.com/content/add-auto-incrementing-build-number-your-build-process in mind. Maybe its a good first reference. Let me know if i can help you |
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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.
Added a version flag to the cli.
Currently prints :
Guetzli 1.0.1#130