-
-
Notifications
You must be signed in to change notification settings - Fork 5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add snappy #193
Add snappy #193
Conversation
🎉 Thanks @groutr. This is awesome. Will take a closer look when I'm at my computer. |
home: https://github.com/google/snappy | ||
license: Other | ||
license_file: COPYING | ||
license_family: Other |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Needs maintainer.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Done.
I have a pre-generated configure script. Do we want to include that in the recipe rather than rely on autogen.sh? |
Phew, that feels like a lot in that last commit! What's wrong with autogen? We also have |
There's nothing wrong with autogen. It just seemed that the circleci builds were failing because of it. |
Hi! This is the friendly conda-forge-admin automated user. I wanted to let you know that I linted all conda-recipes in your PR ( Here's what I've got... For recipes/snappy:
|
Do all the CI machines have autotools? If so, I'll revert the commit of all the files that autotools generates. |
Meaning |
This reverts commit 0a08730.
Hi! This is the friendly conda-forge-admin automated user. I wanted to let you know that I linted all conda-recipes in your PR ( Here's what I've got... For recipes/snappy:
|
We also have |
autogen.sh fails becase:
snappy doesn't use cmake. |
We have |
Also, |
Oh, I expected those the come with the CI, not be dependencies. I can change the recipes. |
Hi! This is the friendly conda-forge-admin automated user. I wanted to let you know that I linted all conda-recipes in your PR ( Here's what I've got... For recipes/snappy:
|
Yeah, we are getting pretty low level here. Linux is a bare docker container with a compiler and a few X11 dependencies so that Qt can survive. Mac has brew, but we are planning on removing just about everything from it. |
REM Build step | ||
devenv "%SLN_FILE%" /Build "%SLN_CFG%|%SLN_PLAT%" | ||
if errorlevel 1 exit 1 | ||
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Drop extra newline.
Think you need |
build: | ||
- msinttypes # [win] | ||
- libtool # [unix] | ||
- automake # [unix] |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Add pkg-config
for Unix.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Also, selectors.
- 2 spaces after package name (minimum)
- line up indentation of these selectors.
Think we're close. Couple more things noted above. |
Hi! This is the friendly conda-forge-admin automated user. I wanted to let you know that I linted all conda-recipes in your PR ( Here's what I've got... For recipes/snappy:
|
Hi! This is the friendly conda-forge-admin automated user. I wanted to let you know that I linted all conda-recipes in your PR ( Here's what I've got... For recipes/snappy:
|
Hi! This is the friendly conda-forge-admin automated user. I wanted to let you know that I linted all conda-recipes in your PR ( Here's what I've got... For recipes/snappy:
|
Hi! This is the friendly conda-forge-admin automated user. I wanted to let you know that I linted all conda-recipes in your PR ( Here's what I've got... For recipes/snappy:
|
As for tests, could you please just verify the relevant libraries are installed? If there happen to be executables that ship with it, checking version or help should be sufficient. This will also make the linter happy. |
version: {{ version }} | ||
|
||
source: | ||
git_url: https://github.com/google/snappy.git |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Could we just download the tarball instead? Should be faster and may avoid a few extra configuration steps.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Are tarballs preferred over repositories?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
IMHO, yes, for many reasons:
- download size is (probably) smaller
- tarballs + sha/md5 is a stricter definition of version than a git tag (tags can change to other revisions)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Also, they may have run autoconf
and other things so it is simpler to build. With many google libraries the standard has been downloading gtest and gmock, though they may have tarballs where this is already done.
@jakirkham I dug up some old PRs and saw how they do tests. I'll get that in the next couple of commits. |
about: | ||
home: https://github.com/google/snappy | ||
summary: A fast compressor/decompressor | ||
license: Other |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks like BSD 3-Clause. Could we put that here? I know the data is licensed differently, but don't think we want to distribute that anyways.
Note, some of the test data is licensed under different licenses, but since they are not in the resulting binary package, the license stays BSD.
Hi! This is the friendly conda-forge-admin automated user. I just wanted to let you know that I linted all conda-recipes in your PR ( |
- test -e $PREFIX/include/snappy-stubs-public.h # [unix] | ||
- test -e $PREFIX/lib/libsnappy.dylib # [osx] | ||
- test -e $PREFIX/lib/libsnappy.a # [unix] | ||
- test -e $PREFIX/lib/libsnappy.so # [linux] |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looking good. Could you please indent the selectors in the test section so they are lined up? Also, we may want to test dll
and lib
for Windows.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Can skip the Windows tests for now, but the other minor comments here should be addressed.
Thanks for adding tests. Looks like the Windows builds don't like the version of the solution file in some cases. The 64-bit Python 2.7 test failure is a bit strange. Not sure what is going on there. |
|
||
extra: | ||
recipe-maintainers: | ||
- groutr |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Please add me too. 😄
Yeah, the one Windows case covered by that solution is passing though. It just doesn't look like we can use it elsewhere. Looks like they might add CMake support upstream. See this PR ( google/snappy#16 ). Given that this is building everywhere else and Windows is such a hard target at present. Let's just skip Windows and handle the other quite minor comments here. Once that's done, I would like to get this merged. Sound good everyone? |
Taking this over in this PR ( #459 ) so we can clear this one. |
Add Google's snappy library
https://github.com/google/snappy