--
You received this message because you are subscribed to the Google Groups "Crystal" group.
To unsubscribe from this group and stop receiving emails from it, send an email to crystal-lang...@googlegroups.com.
To post to this group, send email to crysta...@googlegroups.com.
Visit this group at https://groups.google.com/group/crystal-lang.
To view this discussion on the web visit https://groups.google.com/d/msgid/crystal-lang/CAGuHJrNDDkJXh_afjENxVcM70HNNcOunn5eL81jsv2o5%2BTnftg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.
Ryan (ライアン)
Yoko Shimomura, ryo (supercell/EGOIST), Hiroyuki Sawano >> everyone else
https://refi64.com/
To view this discussion on the web visit https://groups.google.com/d/msgid/crystal-lang/CAO41-mP_S7acirgKC0ybNxG3SXdKNroNoFzTeKPUx6tfYM1MUA%40mail.gmail.com.
I definitely don't want to use containers. I was hoping I could do something like this https://github.com/hone/mruby-cli this project lets you build CLI apps in mruby and generates binaries that run on multiple platforms. I wanted to use Crystal though because I prefer a static typing for the project I have in mind.Maybe I'll just use go or mruby instead.
--
You received this message because you are subscribed to the Google Groups "Crystal" group.
To unsubscribe from this group and stop receiving emails from it, send an email to crystal-lang...@googlegroups.com.
To post to this group, send email to crysta...@googlegroups.com.
Visit this group at https://groups.google.com/group/crystal-lang.
To view this discussion on the web visit https://groups.google.com/d/msgid/crystal-lang/74a76a78-49b1-481f-bf58-ee094638277a%40googlegroups.com.
A few statements in this thread sound awefully weird or at least incomplete or over complicated.
# System CompatibilityFirst of all, a binary compiled on one system should run on any other system using the same target triple.As long as they're run on the same architecture, you can use the same binary for any linux distribution like Ubuntu, CentOS, Arch etc. An example for this is the compiler itself. In the the release process it is compiled once (on Alpine) and then used for packages in the different distributions.
--
You received this message because you are subscribed to the Google Groups "Crystal" group.
To unsubscribe from this group and stop receiving emails from it, send an email to crystal-lang...@googlegroups.com.
To post to this group, send email to crysta...@googlegroups.com.
Visit this group at https://groups.google.com/group/crystal-lang.
To view this discussion on the web visit https://groups.google.com/d/msgid/crystal-lang/9a527985-c43b-49d1-9ad5-ff82090601fb%40googlegroups.com.
A few statements in this thread sound awefully weird or at least incomplete or over complicated.
This isn't true unless you statically link, because different machines have differently compiled dynamic libraries which can easily be incompatible. The only way to ensure this is to statically link, which isn't yet easy.
On 07/09/18 11:15, Johannes Müller wrote:
This isn't true unless you statically link, because different machines have differently compiled dynamic libraries which can easily be incompatible. The only way to ensure this is to statically link, which isn't yet easy.A few statements in this thread sound awefully weird or at least incomplete or over complicated.
# System CompatibilityFirst of all, a binary compiled on one system should run on any other system using the same target triple.As long as they're run on the same architecture, you can use the same binary for any linux distribution like Ubuntu, CentOS, Arch etc. An example for this is the compiler itself. In the the release process it is compiled once (on Alpine) and then used for packages in the different distributions.
--
You received this message because you are subscribed to the Google Groups "Crystal" group.
To unsubscribe from this group and stop receiving emails from it, send an email to crystal-lang...@googlegroups.com.
To post to this group, send email to crysta...@googlegroups.com.
Visit this group at https://groups.google.com/group/crystal-lang.
To view this discussion on the web visit https://groups.google.com/d/msgid/crystal-lang/a74b2c98-fe75-48ed-9489-4beea698d7cc%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
--
I don't have to build on a Mac, I could build the binary in a docker container (like the mruby-cli project does) and ship the binary generated to the destination machines. My question was "what packages do I need to install on the target machine in order for that binary to run"
I realize that if I use YAML or Pg libs or whatever I need to bootstrap with additional libs but do I need to install some packages if I only use the standard crystal libs? If so does anybody have a canonical list of the libs used by the crystal base classes.
--
You received this message because you are subscribed to the Google Groups "Crystal" group.
To unsubscribe from this group and stop receiving emails from it, send an email to crystal-lang...@googlegroups.com.
To post to this group, send email to crysta...@googlegroups.com.
Visit this group at https://groups.google.com/group/crystal-lang.
To view this discussion on the web visit https://groups.google.com/d/msgid/crystal-lang/d7be2de9-6667-4fb4-88f3-107141379d58%40googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/crystal-lang/CAGuHJrPtY0xqotiuU-SEqwPbOx9YjMxQqrYPdT98LsEz%3D43B2w%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.
On 07/09/18 11:15, Johannes Müller wrote:
This isn't true unless you statically link, because different machines have differently compiled dynamic libraries which can easily be incompatible. The only way to ensure this is to statically link, which isn't yet easy.A few statements in this thread sound awefully weird or at least incomplete or over complicated.
# System CompatibilityFirst of all, a binary compiled on one system should run on any other system using the same target triple.As long as they're run on the same architecture, you can use the same binary for any linux distribution like Ubuntu, CentOS, Arch etc. An example for this is the compiler itself. In the the release process it is compiled once (on Alpine) and then used for packages in the different distributions.