At Tue, 18 Sep 2018 14:42:56 +0200, Paulo Matos wrote:
> Just out of curiosity, why are natipkg
> binaries built and distributed? Is there any use case you are
> specifically targetting?
The pkg-build service:
http://pkg-build.racket-lang.org/about.html#foreign
--
You received this message
On 18/09/2018 14:23, Matthew Flatt wrote:
>
> The right solution is probably to use the "natipkg" build of Racket for
> Linux, which minimizes the libraries that are required from the OS. For
> example, the natipkg variant uses its own build of libcrypto. You can
> find natipkg builds from a
At Tue, 18 Sep 2018 13:09:22 +0200, "'Paulo Matos' via Racket Users" wrote:
> That looks ok to me, so why didn't raco distribute copy the library into
> the distribution?
`raco distribute` only incorporates libraries that are from Racket's
own "lib" directory. On Windows and Mac OS, that includes
I have been playing with a CI pipeline of my software that does:
test -> build -> containerize
The idea is that build creates an OS independent distribution using raco
distribute and then containerize creates a docker image of the
distribution using a well-known linux distro. In my case, I chose
4 matches
Mail list logo
