please consider tagging versions & doing releases #12
Assignees
Milestone
Comments
|
I'll update the documentation to reflect this but we prefer people to embed the library to prevent breakage due to API changes (i.e. compile and link statically). See abseil documentation here. I don't plan to provide explicit versions or release for now. |
|
cough https://www.youtube.com/watch?v=NSemlYagjIU cough ;-) |
|
cough cough |
|
Fair enough. I understand there is a need for a versioning scheme. |
|
👍 |
gchatelet
added a commit
that referenced
this issue
Jan 17, 2019
# This is the 1st commit message: Update macros to detect mips64 and differentiate between x86 32/64. # This is the commit message #2: Fix Mips32 and add an alias for Mips32/64. # This is the commit message #3: Allow specifying cmake generator. # This is the commit message #4: Remove unavailable MSVC version and test Ninja on travis # This is the commit message #5: Add ninja build. # This is the commit message #6: Use Ninja by default # This is the commit message #7: Show tests output # This is the commit message #8: Defaulting env to Ninja in the build matrix # This is the commit message #9: Defaulting env to Ninja in the build matrix # This is the commit message #10: Do not use ninja on OSX # This is the commit message #11: Fix test output. # This is the commit message #12: Fix running tests # This is the commit message #13: Fix running tests
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I assume this library is alpha-stage currently, but please tag versions/releases so people know exactly which revision of
cpu_featuresthey are currently using.The text was updated successfully, but these errors were encountered: