At Wed, 12 Jul 2017 17:25:58 -0400, Leif Andersen wrote: > It looks like this is what the docs have to say wrt making tests pass: > ``` > Distribute Native Libraries > > Another option is to build a 64-bit Linux version of the library, > distribute it as a package, and make the package a platform-specific > dependency of your package for the "x86_64-linux-natipkg" platform. > > This option is in many ways the best one for users and for > testing—especially if Windows and Mac OS native-library packages are > also provided—but it’s more work. > ``` > > This isn't enough though, we need to know what distro to target. Even > in situations where I would love to bundle native packages, these can > have a large amount of dependencies that are specific to individual > distros.
For the "natipkg" strategy, you would need build and supply all of those dependencies, too --- or depend on other "natipkg" packages that supply them. Granted, you'll need to depend on some C library, but picking a sufficiently old one works in practice. The existing "natipkg" binaries are built on Debian Lenny for that reason. To the degree that this strategy doesn't work, then I think we should just say that the "natipkg" idea doesn't work instead of trying to pick a distribution. -- You received this message because you are subscribed to the Google Groups "Racket Developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/racket-dev/5966ac99.ca00620a.4eed9.97b7SMTPIN_ADDED_MISSING%40gmr-mx.google.com. For more options, visit https://groups.google.com/d/optout.
