Re^2: XS, raspberry pi, and a hundred bucks

Replies are listed 'Best First'.
Re^3: XS, raspberry pi, and a hundred bucks by stevieb (Canon) on Nov 01, 2021 at 17:37 UTC
I usually use Inline::C for initial prototypes and quick one-off tests before I write an actual XS module. I never want a user to have to require `Inline`.	[reply] [d/l]
Re^4: XS, raspberry pi, and a hundred bucks by NERDVANA (Priest) on Nov 02, 2021 at 06:10 UTC
Check out Inline::Module. It lets you develop using Inline and then package it in a way that all the Inline compilation happens during Makefile.PL and then the resulting installed module doesn't require Inline. It's a bit of effort to learn, but I got it working in OpenGL::Sandbox, even packaged up with Dist::Zilla!	[reply]
Re^4: XS, raspberry pi, and a hundred bucks by perlfan (Parson) on Nov 02, 2021 at 01:58 UTC
That seems fair - mind explaining why? I am only asking for my own edification. I've written exactly one XS module on CPAN, and I had a lot of help; but I can say for sure that any use of Inline::C has not been for anything I plan to distribute broadly. That said, the one difference I can see between the 2 is that XS modules are compiled once on install; Inline::C run the risk of being recompiled if the cache goes away - usually at an inopportune time.	[reply]
Re^5: XS, raspberry pi, and a hundred bucks by Anonymous Monk on Nov 02, 2021 at 08:31 UTC
Indeed Inline::C generates an xs distribution, you only have to use it once to bootstrap an xs module	[reply]
Re^6: XS, raspberry pi, and a hundred bucks by bliako (Abbot) on Nov 02, 2021 at 09:18 UTC
Re^7: XS, raspberry pi, and a hundred bucks by Anonymous Monk on Nov 02, 2021 at 10:06 UTC
Some notes below your chosen depth have not been shown here
Re^3: XS, raspberry pi, and a hundred bucks by ikegami (Patriarch) on Nov 02, 2021 at 15:12 UTC
For accessing a library, I'd go with FFI::Platypus	[reply]