Closed Blacksmoke16 closed 3 years ago
Bump.
Would be great if this made it in time for https://github.com/crystal-lang/crystal/pull/9317 in order to enable MT builds with 0.35.0
.
\cc @bcardiff @RX14 @waj
@RX14 @bcardiff @straight-shoota This should be good for another review.
I suppose the build tools should be removed from the docker image after building libgc?
Hey just FYI, I was looking for an "official" alpine crystal image and stumbled onto this PR.
I was trying to build a static binary for Crystalline to solve this issue. It seems like yaml-dev
on Alpine doesn't give the right static libs, so I had to add yaml-static
as well.
Not sure if it is useful, but since this is not merged yet, I thought I'd share 😄
Bump :)
This needs conflict resolution.
I'm also a bit confused now about the Ubuntu dockerfile changes. Description only talks about alpine. And a patched library should be shipped with the debian package, so rebuilding seems unnecessary here.
@Blacksmoke16, I made a PR to your repo that I believe resolves the comment above by @straight-shoota
Blacksmoke16/distribution-scripts/pull/1
@caspiano Thanks! Merged and fixed up two things I noticed. Should be good for another review now.
Disclaimer: I didn't test it locally yet.
This would be awesome to have with 1.1.0
😉 What's currently in the way of a merge?
I cannot wait to run my crystal services with MT 🤤
I cannot wait to run my crystal services with MT 🤤
Well, you can already do that with older releases, just need to provide the patched library.
I normally run alpine images, I'd either have to build an image with the patch (like this) or switch to the ubuntu images. This is a great change, thanks @Blacksmoke16!
~One question I have left is what to do about
LIBRARY_PATH
? Given I think both paths need to be used?~~Added built libgc path to
LIBRARY_PATH
in build image.~LIBRARY_PATH
is no longer required apparently due to #69.