-
Notifications
You must be signed in to change notification settings - Fork 4
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Please consider switching away from Inline::C #32
Comments
@cpansprout I tried to do that once using As for compiling in a different folder have you tried setting |
huh.. I'm pretty happy with Inline::C. It works. :D I'm on macOS X and here
are some XS modules which doesn't compiles. Never happens such problems
with Inline::C - anything using Inline::C - just works. So, by me - stick
with it. :)
…On Thu, Jun 22, 2017 at 12:16 AM, Mamod Mehyar ***@***.***> wrote:
@cpansprout <https://github.com/cpansprout> I tried to do that once using
Inline::Module and InlineX::XS with no success, I'll see if I can do this
in next version so I'll keep this open for now, thank you
As for compiling in a different folder have you tried setting
PERL_INLINE_DIRECTORY environment to the location where you want the
compiled sources to be located?
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#32 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AAr7Yq76Vo_fNkKpyiAppQnFsLksC4G3ks5sGZYugaJpZM4NvLuY>
.
|
It turns out that Inline is supposed to support compiling the code at install time. You just need to do
Inline is far too restrictive when it comes to version numbers. I have reported the bug at ingydotnet/inline-pm#62. |
A major downside of Inline::C is that it requires a C compiler to be installed on the machine, even if it's a production server. If one uses system packages for installing precompiled dependencies, this is a very undesirable exception. |
The problem with using Inline::C, rather than compiling the C code at installation time, is that multiple users all end up with their own copies of the compiled C code in their home folders. (And Inline does not have the courtesy to use a hidden file name beginning with a dot!) Also, if I happen to upgrade Inline::C, then JavaScript::Duktape recompiles its C code all over again, which can be quite annoying if I am actually trying to get some work done. :-)
The text was updated successfully, but these errors were encountered: