-
Notifications
You must be signed in to change notification settings - Fork 1.1k
Publish libraries to apt repo #490
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
Comments
Would you care to share the code for generating the deb files? I'd be happy to incorporate it into our build. We've been planning on this for a while, but haven't gotten around to it. Also, it's not THAT useful, since we can't guarantee ABI compatibility between releases. I suppose we could only provide the static libs? |
@JonathanHenson the repo I linked has all the code. It's just a sub-100 line makefile (plus some configuration for Travis publishing to Bintray). Debian has a bunch of fancy packaging tools, but mine is pretty bare bones. I build two packages for each library: the binary package with the static binary, and the source package (
Sure, but that's for the consumers to figure out. E.g. I can consume 1.0.90 to 1.0.96. Debian actually has some tools to help downstream packages determine when symbols in shared libraries change. (https://www.debian.org/doc/debian-policy/ch-sharedlibs.html) But those don't really apply to C++ libs, which export pretty much everything. There are some CMake tools (https://cmake.org/cmake/help/v3.0/module/CPackDeb.html) that you might prefer using, but I am no CMake expert. |
Closing this issue as we currently don't have any plans to publish binaries and recommend consuming this sdk from source |
This issue is now closed. Comments on closed issues are hard for our team to see. |
It would be nice to published the compiled libraries, just like the Ruby, Python, PHP, JavaScript, and Java AWS SDKs are published as installable packages.
I've published debs to an apt repo here: https://github.com/lucidsoftware/aws-sdk-cpp-deb
The text was updated successfully, but these errors were encountered: