You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Thanks again for providing VADR. In packaging VADR for a production system, I have noticed that it transitively depends on Inline::C. Compiling C/C++ code at runtime requires a build toolchain to be present at runtime, and introduces potential reproducibility and maintainability issues. While I haven't used Inline::C myself, I understand from reading the documentation that it's possible to compile the Inline::C modules once and distribute them as XS modules. It would be nice if this could be done in the course of packaging VADR, so that only dynamic libraries and Perl modules are required, instead of a full compiler toolchain.
The text was updated successfully, but these errors were encountered:
Thanks again for providing VADR. In packaging VADR for a production system, I have noticed that it transitively depends on Inline::C. Compiling C/C++ code at runtime requires a build toolchain to be present at runtime, and introduces potential reproducibility and maintainability issues. While I haven't used Inline::C myself, I understand from reading the documentation that it's possible to compile the Inline::C modules once and distribute them as XS modules. It would be nice if this could be done in the course of packaging VADR, so that only dynamic libraries and Perl modules are required, instead of a full compiler toolchain.
The text was updated successfully, but these errors were encountered: