Re: [ANNOUNCEMENT] wasm-0.5.0 (stable) Released.
| From: | Ivan Enderlin | Date: | Fri, 23 Aug 2019 11:56:00 +0000 |
| Subject: | Re: [ANNOUNCEMENT] wasm-0.5.0 (stable) Released. | ||
| References: | 1 2 3 4 | Groups: | php.pecl.dev |
| Request: | Send a blank email to pecl-dev+get-16176@lists.php.net to get a copy of this message | ||
Thanks for the replies.
I perfectly understand the issue with shared libraries. Is it a strict rule for PECL to avoid them? The Wasm runtime is written in Rust, and PECL doesn't support the Rust toolchain. The solution proposed by Thomas Hruska to rewrite the runtime in C or C++ is absolutely out of the question :-). To facilitate the user lifes, I've decided to embed the shared libraries; I can build one per architecture if necessary, or throw an error telling Rust is required when a specific architecture isn't supported.
My problem so far is that PECL failed to compile against the shared library. Am I doing something wrong in the
config.m4 file?
Thanks.
On 23.08.19 10:39, Remi Collet wrote:
Le 23/08/2019 à 10:09, Ivan Enderlin a écrit :Also, why publishing aBecause perhaps it will work for some users which use the same distro than the one used to generate it, but won't work for others. Especially for various arch (arm, i386, ppc, ...) IMHO: A pecl archive is a "sources" archives, so should only contains sources. Remi.soand a.dylibfiles aren't acceptable?